John Dowson

There is something strange going on with your devices - there seems to be a mix-up/registry problems between your TQ6+ and a vjoy device. First you have this: You have the same joystick id (4) assigned yo your RUDDO+ and one of your x-box controllers (do you have 2?) Then the mix-up between the TQ6+ and a vjoy device - from your log So the TQ6+ has been acquired but with the GUID of a vjoy device. And your axes assignments are to device 'C', which is: So it seems your registry is in a bit of a mess and there seems to be a problem with a vjoy device. There are a few things to try: - revise your vjoy set-up - disconnect your TQ6+ and Ruddo+, remove any drivers and reboot, then re-connect to see if the issue get resolved - if that doesn't work, you will need to clean your registry. If you can show me your FSUIPC7.Joyscan.csv file I can help you with this. John

FSUIPC7 already supports the 8.33KHz frequency range via the 32bit int offsets (e.g. 05C4,05C8, 05CC, 05D0). However, it seems that the MSFS SDK does not yet support this. This has already been raised with Asobo.

I was just trying to say that FSUIPC7 does not affect MSFS at all (it doesn't change anything) - its standalone, so you can still start MSFS how you used to without FSUIPC or the link it creates. FSUIPC7 will have no affect until it is ran, and can't interfere with the start-up process (apart, of course, from the using the -FastLoad option in the bat file).

FSUIPC7 is a separate application and does not affect MSFS. However, if you are talking about the optional desktop link that starts MSFS and FSUIPC7, then this starts MSFS with the -FastLaunch option (for MS Store installs only). Does that bypass the update check? I didn't know it did that (I have a steam install). You can remove this by editing the file MSFSwithFSUIPC7.bat - just fine that option (end of line 7) and remove it. John

There is only a discount available for FSUIPC7 for FSUIPC5 and FSUIPC6 license holders, sorry. John

I see the empty line in the log, which is strange. However, my controls still work fine. I do continually get the following message: 795062 #### ERROR: No SimConnect data seen for more than set stall time! which is not good! As I said, I'll investigate and get back to you.

Leave it with me, I'll get back to you.

Ok! I thought your issue was that it wasn't being sent! Could you try assigning the Tab-T on its own, to see if it works like that. However, it may be a timing issue when you are overloading the keypresses on a single button. It may be better to use the controls directly, or maybe a lua script. Leave it with me and I''ll get back to you, but it may take a day or two. John

I'm also wondering maybe if its the use of the tab key. Iy is being treated as a modifier key when it isn't really. I'll do some tests over the next few days and get back to you.

So the switch has two buttons, with the press being sent on each when iy goes to up/down, and a release sent when you put ity back to the centre. This is what I expected. So this is sending the ctrl+L, as expected: 18125 SendKeyToFS(0002004C=[ctl+L], KEYDOWN) ctr=0 18234 SendKeyToFS(0002004C=[ctl+L], KEYUP) ctr=0 This is your release, and is sending the Ctrl+L followed by the Tab+T:: 28359 SendKeyToFS(0002004C=[ctl+L], KEYDOWN) ctr=0 28359 SendKeyToFS(0002004C=[ctl+L], KEYUP) ctr=2 28359 SendKeyToFS(00080054=[tab+T], KEYDOWN) ctr=4 28468 SendKeyToFS(00080054=[tab+T], KEYUP) ctr=0 So it looks to me that its sending exactly what you have assigned. So what exactly is the issue? Maybe its the timing... with the tab+T down being sent at the same time as the keyup for the Ctr+L?

Is MSFS running?

By the way, does this occur all the time or only occasionally? I've had FSUIPC7 running for several hours and have closed/re-opened MSFS several times. I have noticed an issue with data from simconnect seeming to be stalled (although aircraft operates ok), so I'll look into this, but other than that it seems to be ok. I am wondering if this could be due to the Rotaries.lua that you are auto-starting. Maybe you could test without this running. Looks like FSUIPC7 isn't killing the luas when the FS disconnects which it should I guess. I'll look into this. John

Yes, of course. But as I said, the batch files (and shortcut) are only there as a convenience, you don't have to use them, and you can adjust them to your needs (i.e. remove message or splash screen). For all other flight sims, FSUIPC was an embedded dll and so always closed with the FS.

Please repeat but with the assignment UI panel closed. I am interested in the 'Button changed' log messages..... That log shows the switch has two "buttons", but its not logging the releases with the ui panel open.

I think you should remove any assignments to that switch, activate button logging and then move the switch between the three settings to see what is actually being sent on each change. If its a 3-position switch, it must be using more than one button number, otherwise I don't know how it can function properly. I don't have any 3 position switches so cannot advise. Try operating it with logging on (and the console open), and see what button presses/releases you see when you change its position: off -> up up -> off off -> down down->off ?

Sorry, I don't understand what this means. They are both distinct applications. Nothing is stopping you from doing that. Just don't use the provided batch file (and don't install the link on your desktop), and start FSUIPC7 as before, by running the FSUIPC7.exe. If you don't want FSUIPC7 to exit when you exit MSFS, then disable that option from the Options menu. The batch file (and desktop link) are provided for convenience only. You don't have to use them. John

Just tried it and it works ok here.... Did you edit the ini file with FSUIPC7 still running and not 'reload' it? Try exiting FSUIPC7 and check your ini to make sure the assignments are still there. Here's my log with those assignments (different device and button number) - it is sending two Ctrl+L and one tab+T: I am wondering if you have programmed this to a "sticky" button, i.e. one that on first press sends a button down, and on second press sends a button up. Even so, it should still be sending the two keys on the button up. You can zip it if its too big. John

I mean that you should not start a new log by selecting 'New Log' from the log menu. I'll investigate and get back to you.

Can you also attach your FSUIPC7.ini file. And when you attach a log, please always attach the full log, not a continuation. There is also information at the beginning of the file that I need to see. John

No idea, but maybe your device was in a weird state.... So its recognized and you are good to go, no?

Looks ok. Try activating logging for buttons & keys and see what you can see.

The key for those details validates ok, so I don't understand your issue. I have sent you a PM. John

The installation folder, yes. Thats one way. Or if you want it to auto-start, you can add it to the [Auto] section of your FSUIPC7.ini (or the same in a profile), like so: I've already seen that. As I said, better to run FSUIPC7 and show me your .log, .ini and Jotscan.csv files. However, if HidScanner thinks its a mouse, I presume so will FSUIPC7 and so you will not see it.

No success with uninstalling? Why - what does this mean? Did you get an error? What did it fail to uninstall? Do you have an uninstall log? Have you managed to register or not? I really can't help you if you do not provide the required information.

As I said, I'll take a look at this when time permits. But it is low priority. There is really little point in having FSUIPC running without the FS. You should start/stop FSUIPC7 with the FS. The latest installer creates a shortcut item to start them together, and you can now exit MSFS and FSUIPC from within FSUIPC. John