John Dowson

But maybe @Chuck100 can help - I presume the message was for him as you could not contact him by other means.

Ok, thanks. Strange error though - looks like your Path isn't being set correctly (but it is for Admins). cmd.exe should be in c:\Windows\System32, which should be in your path....

It shouldn't do. But if that was what you saw in the editor, maybe it saved and overwrote the full log when it closed? I don't see why FSUIPC would stop logging - unless it has crashed. Let me know if it happens again. Btw, to view the log in real-time you can use Log -> Open Console.

Ok, thanks for the report. I'll update in the next few days (it will be included in the next release of FSUIPC6/7, and I'll update the downloadable SDK zip file). Cheers, John

@Matthew Twomey Please try the following: FSUIPC7.exe

Just checked this - it works in FSUIPC6 but not in FSUIPC7. I'll investigate and get back to you. John

Yes, and in that order. Yes, and you can mix and match controls & keypresses.

Then do the same but switch from using the key presses to using the provided controls for taxi and landing lights: Landing lights toggle: C65751 Taxi lights toggle: C66240 Both with a parameter 0. Remove these from your 'Tab-O' control, and overload where needed (with a mixture of the controls and keypresses).

@Blindside Just took a look at the TBM 930....why don't you just use the controls rather than the keypresses: Toggle Taxi Lights Landing Light Toggle Assign your button 12 to one of those controls for both press and release, and the other control to button 13 for press and release. Then your switch in one direction should activate the landing lights, the other the taxi lights, and when in centre (off) both will be off.

@aurel42 The empty log line was a log of an empty AIR file being received...I have now changed this to an appropriate message when this occurs, and then not using this to update offset 3C00. Can you try the attached version please (7.0.1a): FSUIPC7.exe

I am confused as to what is actually happening! To be honest, I have no idea what "bug" you are referring to. Are you saying that you not longer get to the MSFS main menu when you start MSFS? Can you no longer use the sim? What 'page' does MSFS show you once started and loaded? Later: sorry, as you said 'it runs till the opening screen (Mount Fuji) but no step further as it used to. ' So it just hangs there? Check the Asobo/MSFS forums and see if any one else has reported this, and if not raise a zendesk ticket.

In MSFS, you cannot disable controllers. However, you can create an empty profile for your controllers. If you create a new profile it will automatically be empty. It also seems that MSFS doesn't suffer from the same problem (i.e. automatically re-assigning to a controller) as P3D/FSX, so you can mix and match, and assign to some controls in MSFS and others in FSUIPC7. This is useful as there are quite a few controls (e.g. for view control and slewing) that work in MSFS but not via SimConnet (i.e. in FSUIPC7). The alternative to assigning such controls in MSFS is to assign in FSUIPC7 but to an MSFS keyboard assignment (this is how I currently control my views and eyepoint). John P.S. Try yo give your posts an appropriate title! This helps other users who have a similar query. I will update it.

Just remove the -FastLaunch - you nee the App bit, so should be cmd.exe /C start shell:AppsFolder\Microsoft.FlightSimulator_ 8.............bwe!App However, I'm not sure why you would want to do this... I don't know what this means. As I said, FSUIPC7 in no way affects MSFS - you can always start it however you used to, before you installed FSUIPC7. Its not a registration key and is fine to be public. John

Yes. A few. These ae the current 'undocumented' controls that have been added: AILERON_TRIM_SET RUDDER_TRIM_SET TOGGLE_AIRCRAFT_EXIT_FAST HEADING_SLOT_INDEX_SET SPEED_SLOT_INDEX_SET ALTITUDE_SLOT_INDEX_SET VS_SLOT_INDEX_SET THROTTLE_REVERSE_THRUST_TOGGLE AVIONICS_MASTER_1_SET AVIONICS_MASTER_2_SET It has also been noted that the TOGGLE_MASTER_BATTERY control accepts a parameter to toggle individual batteries - see John

You license has expired. The time-limited license for FSUIPC7-beta expired yesterday. If you want to use the assignment facilities, you will need to purchase a license from SimMarket. John

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?