John Dowson

I don't think this will make a difference. You can try it, but make sure MSFS is set to run as administrator. I didn't try this though, but should work...

Sure, I can also add that. Ok, but rather strange. I can do that before the offset is populated. Ok, I can look into that as well, but may take a few days. I'll do it for the 3 slot index offsets (altitude, heading and speed), but not the APU switch offset. John

Further info: both your second yoke and your wingman have been assigned the same joystick id (2), which is why you have issues. Also, as both your yokes have the same product and vendor ids, they can get confused if you disconnect and re-connect. But, once set-up it should be ok if you leave them connected. Your assignments are slightly confused due to this and will need modifying. You have assignments to a device with id 3 that doesn't exist - do you know which device you made these assignments to: Once I've seen your updated files with the joyletters assigned. I can change these to the correct device if you let me know which that is! From you Joyscan.csv file, it should be the wingman. If thats the case, you could also try changing this line in your ini: 2.GUID={4D285480-3B07-11EA-800D-444553540000} to 3.GUID={4D285480-3B07-11EA-800D-444553540000} at the same time as you make the AutoAssignLetters update, then restart FSX, try your yoke and post the update files if still not recognised. If you do that, you may need to revise your current assignments to device 2: If they are to the Wingman, they will also need to be changed to 3. Otherwise they will be assigned to your 2nd yoke, which should be recognised (with the above changes) as device 2. If in doubt, remove them and re-assign. John

Looks like the yoke is being assigned the same joystick id as your Wingman for some reason. Can you do the following please: change AutoAssignLetters=No to AutoAssignLetters=Yes in your FSUIPC4.ini, start FSX, close it, then attach you new FSUIPC4.log and FSUIPC4.ini files. John

This should be the one that works, with both flightsimulator.exe set and FSUIPC7.exe set to run as admin. I don't know why you get a CTD with this config. Maybe try that again? If it crashes again, check for a crash event in the windows event viewer. You can post that here but I'm not sure I can do much with it... John

Sounds strange. Did you try sending the control on the release only? Then this seems correct - only one control being sent. If that is incrementing by 5 rather than 1, I think you need to ask PMDG why... What is logged when you increment by 1 with the mouse? Have you trued using a mouse macro for this instead? And lookin art the PMDG website, someone also posted the issue there: https://forum.pmdg.com/forum/main-forum/pmdg-737-ngxu-for-prepar3d-v4/57103-mcp-heading-selector-event-evt_mcp_heading_selector-event-70022-jumping-in-steps-of-value-of-5 The proposed solution is to assign keys for this in the PMDG setup, and then assign to those keys in FSUIPC. Maybe try that? John

As with all CTDs, they should be reported to Asobo with the relevant crash logs, not here. John

But why do you think that? Its the same issue for both systems. No point in investigating both, if you solve it in one then you will have solved it in the other....

He means the date on the www.fsuipc.com web page - which still says July 20th 2020. I will update that shortly. Not sure where he's getting the 5.0.5.1 version number from though! John

Just had a look at this in more detail. TrackIR is not set to run in administrator mode, but it requests this when ran, so it does run in administrator mode. You therefore need to set FSUIPC7 to run in administrator mode if starting trackIR from FSUIPC7. Then, as MSFS stars FSUIPC7 from the EXE.xml, you need to run MSFS in administrator mode for it to be able to launch FSUIPC7, which will then be able to launch trackIR. I did this by setting this option on my FlightSimulator.exe file. After doing that, all start ok. Alternatively, you can remove the start-up of FSUIPC7 from the EXE.xml, and re-enable the start of FSUIPC7 from the MSFS.bat file.To do this, change to and replace INSTDIR with the full path to the FSUIPC7.exe John

I wonder how this happened. Currently, uninstalling removes the entry, and installing ALWAYS adds the entry, but does not check for existing entries. When I get time, I'll update the installer to check for an existing FSUIPC7 entry first, before adding the new entry. This should prevent mutile entries occuring. Yes, that's fine. But note that you can also use either the FSUIPC ini file ([Programs] section) or the MSFS EXE.xml file to also start other programs.

Is trackIR set to run with admin privileges then? If so, try turning that off and running everything as non-admin. John

Can you try the attached version, v7.0.4b, where I have added the following offsets: 0x0290 4Bytes AUTOPILOT ALTITUDE SLOT INDEX 0x0294 4Bytes AUTOPILOT HEADING SLOT INDEX 0x0298 1 Byte APU SWITCH Thanks, John FSUIPC7.exe

Hi Stephane, someone else has also reported something similar here: I have found a sim variable APU SWITCH (read-only), that may be useful to you. Its available in the version posted in that topic. John

Can you try the attached version, v7.0.4b, where I have added the following offsets: 0x0290 4Bytes AUTOPILOT ALTITUDE SLOT INDEX 0x0294 4Bytes AUTOPILOT HEADING SLOT INDEX 0x0298 1 Byte APU SWITCH Thanks, John FSUIPC7.exe P.S. The offsets are read-only. I could make the slot index ones writeable by using the associated controls when written to if needed.

The SDK also lists the following sim variable: APU SWITCH Boolean, whether or not the APU is switched on. UNITS_BOOL However, this is not documented as being exposed vi SimConnect. I will try adding it anyway, to see if it is recognised, and will let you know. If not, I can raise a zendesk issue to get this exposed via SimConnect. John

If you keep the console open, you will see the entries logged (or not!) when you use the mouse. Doo you see anything doing this? Ok, but why not just disable controllers in P3D then? This will prevent them from being automatically re-assigned by P3D, which can happen. It can go in the [General] section or in a a [Profile.xxxx] section. You want it in the latter, i.e. add this to your [Profile.B738U] section (and maybe your other PMDG profile sections): DontLogThese=66587 Yes, as this is used internally by your PMDG aircraft. Also, please don't start a new log file - I need to see the complete log file. You have also assigned to send the control on both press and release: 242=P257,17,C70022,-2147483648 -{Custom control: <70022>}- 243=U257,17,C70022,-2147483648 -{Custom control: <70022>}- So this will send to controls (one on press, one on release), so maybe remove one of those - this will half the change rate. Your last log is also quite strange, as it shows several button presses per second: If you press this button once, do you see multiple press entries in your log? What is your 257 device (some type of VRI device?)? Is that sending repeated button press/releases when 'on'? John P.S. Please keep your console open when testing, so you can see what is logged on each individual button press/release. Other than that, your assignments look fine according to the header file.

Just rename your linda.lua script, or, better, remove the call to that script from your ipcReady.lua script. There is no FSUIPC7 log file included, only you installation log which is not relevant. Please disable Linda, activate the logging requested (event and button & keys) then produce a short log where you press one of you assigned buttons (i.e. not keys - we'll check your issue for buttons first) Could you update to FSUIPC6 v6.0.12 first though please - this was released yesterday. Your ini file also shows that you are not using the JoyLetters facility. This means that you joystick IDs could have changed, which would invalidate your assignments. You should activate the JoyLetters facility by setting the AutoAssignLetters ini parameter (in the [JoyNames] section) to Yes. You also have one assignment to a non-existent device (with id=0) that you can delete: 0=0X,256,D,36,0,0,0 -{ DIRECT: SteeringTiller }- Maybe also check your FSUIPC6.ini to see if you can determine if your assignments (buttons and axes) are assigned to the correct devices (with 1=T.16000M, 2=TWCS Throttle, 3=Yoke).

Its obviously a permissions issue but I've no idea what is causing this, you need to play around. I have TrackIR as well, but I never run anything in admin mode.... I always start TrackIR manually (as I only use it occasionally and for tests), but I'll try starting in via both FSUIPC and the MSFS EXE.xml to see if there are any permission issues for me (but I doubt it!). You could also try running TrackIR from the EXE.xml, rather than from FSUIPC?

Sounds like a question for MobiFlight. Someone asked the same question on the Asobo forums, but I haven't seen a response, so far.

No idea, sorry.

As I said, I am not sure where this is held. However, just looked at the SDK documentation, and there are the following sim variables (although they are not documented as being available via SimConnect: AUTOPILOT ALTITUDE SLOT INDEX Index of the managed references Number TYPE_UINT32 N - AUTOPILOT HEADING SLOT INDEX Index of the managed references Number TYPE_UINT32 N I can try requesting these to see if available and add them to a spare offset. I'll check if these are available in the next day or so and let you know. John

Only do that of you want to run MSFS as administrator. Previously FSUIPC7 was either started manually, or with MSFS using the batch file and desktop link provided. Since the latest release, v7.0.4, FSUIPC7 is started by MSFS via the EXE.xml file, and the launching of FSUIPC7 via the batch file has been removed - this file (and desktop link) now start MSFS only, as well as displaying the splash screen. If you get the error that another copy of FSUIPC7 is already running, then two copies are being started. Check your EXE.xml to see if it has two entries for FSUIPC7 and, if so, remove one. Also, check that you are not using the old batch file/desktop link to start MSFS. John

Can you check to see if there is a crash event in the windows event viewer, and if so post me the details. Can you also right-click the installer, select properties, and take a screenshot of the details and attach that. What version of windows are you running?

Check your FSUIPC documents folder. There should be a text file there called Controls List for P3Dv4 Build xxxxx.txt.The FSUIPC added ones are documented in the Advanced User guide. John