John Dowson

The issue seems to be that the name of the device (T.A320 Pilot) is now missing. Not sure why this is...do yo have any specific drivers installed or any additional software for this controller? If so, you could try uninstalling and using the windows default drivers to see if that makes a difference. This controls automatic assignment of joyletters, not ids. If you can't get FSUIPC to read the name of the device from the registry correctly, then you could try without using the joyletters facility. To do this, try the attached ini where I have reverted your assignments to use the joy ids rather than the letters., John FSUIPC7.ini

What has this got to do with FSUIPC7? I do not support REX 2020 Weather Force - try their support forum: http://rexsimulations.com/support.html John

Yes - there is an FSUIPC-added control that you can use for this - from the Advanced User guide, P29: 1152 Pause (ms) – this adds a delay in ms. It can be used to insert a delay between key press/releases and mouse operations (where needed) Yes, this is correct. John

There is an issue with 7.3.8 in that the presets won't load unless you add the following to your FSUIPC7.ini: [WAPI] EnableWAPI=Yes Alternatively, try with the latest beta available here: I don't know, I don't have the 737-800. Maybe they do, otherwise I would expect to see new presets for this aircraft on the MF hub-hop site. Try them and see... John

The FSUIPC7.log file will certainly be in the FSUIPC7 installation folder. You probably have windows explorer set to hide extensions of known file types. Change that - see the appendix in the Installation and registration guide for details. If FSUIPC7 crashed, was MSFS still running? MSFS crashing on long flights is a long standing issue (check the Asobo forums for details), and when MSFS crashes that can cause FSUIPC7 to close down. Are there any MSFS crash events before the FSUIPC7 one? Your FSUIPC7.log file would confirm if it was FSUIPC7 that crashed or MSFS. Note that there is also a beta that you could try that has a fix for a CTD relating to lvar/hvar reloading, but I don't think this is your issue. The latest beta is available from here: John

You need to show me your FSUIPC7.ini and FSUIPC7.log files, the latter with Axis logging enabled - start MSFS and FSUIPC7, load an aircraft and move an assigned axis or two, then exit FSUIPC7 and show me the .log and .ini. But this will change/alter an axis assignment...what happens if you click cancel? I haven't seen that option...I will take a look, but that certainly wouldn't affect assignments. The WASM is only used for lvars, hvars and calculator code. I can't see how that can happen...can you show me a screenshot of before and after you click the reload button please. John P.S. Sorry for the delay - I was on holiday for the week.

This indicates that the button is either overloaded, or there is a compound or offset condition in the button press. Activate logging for Buttons & Keys, open the logging console and see what is logged when the button is pressed - that should give you some idea. Also, check that aircraft name is in your profile - use substring matching in profiles or when you use an aircraft with a different livery it may not match your profile. But I am now on holiday until Monday 19th. If you are still having issues, post your FSUIPC6.ini as well as your FSUIPC6.log file with logging for Buttons & Keys added as well as Events and I'll take a look when I return. There really should be no such issues switching from FSUIPC5 to FSUIPC6...

I have looked into this further, and what ever assignments I try I always get the same problem: when I deactivate the reversers, the motion of the plane suddenly changes from reverse to forward motion, even though the thrust is at idle. This seems to be an issue for PMDG (or maybe MSFS) - I will investigate further when I return from my holidays and report/raise a bug if necessary. This is the simple config I ended up with: [Buttons.PMDG737] ButtonRepeat=4,2 1=PB,8,C65966,1 -{THROTTLE1_DECR}- 2=UB,8,C1070,112 -{: F1}- 3=PB,9,C65971,1 -{THROTTLE2_DECR}- 4=UB,9,C1070,112 -{: F1}- 5=CR(+B,8)B,24,C65966,1 -{THROTTLE1_DECR}- 6=CR(+B,8)B,25,C65971,1 -{THROTTLE2_DECR}- This only sends the F1 key (throttle idle) when reversers de-activated, but has the affect of changing reverse motion to forward motion in an instant, although the thrust is at idle. I decided to remove the action on the release of the throttle detent, and I have slowed the button repeat rate to 4 per second. This allows me to slowly increase reverse thrust and move back to the detent to maintain that level of reverse thrust. I did try various other assignments, but they all had this issue. The throttle 1/2 reverse thrust hold didn't work, although others have reported that Throttle Reverse Thrust Hold is working (i.e. all engine version), but I haven't tried that. John

Yes, this is very strange, I do not know what could cause this, as the auto-start does work on subsequent runs of MSFS You will just have to manually start GSUIPC7 on the first run of MSFS I'm afraid. Note the desktop MSFS icon created by the installer is just a shortcut to the MSFS.bat file, which shows a splash screen while MSFS is starting. It does not start FSUIPC7 - that is performed by MSFS itself using the EXE.xml file,

Only the latest version of each FSUIPC version is supported (apart from betas) - please update to 7.3.8 or 7.3.9c. If you update to v7.3.8, also manually add the following to your FSUIPC7.ini: [WAPI] EnableWAPI=Yes You should also update your profiles to use substring matching, e.g. change this [Profile.PMDG 737-700] 1=PMDG 737-700 Southwest Airlines (N268WN | 2021 | Heart) 2=PMDG 737-700 United Airlines (N27734 | 2019 | EvoBlu) to this: [Profile.PMDG 737-700] 1=PMDG 737-700 John

Sorry, didn't have much time today to look into this... The throttle detent should work on release in FSUIPC...I don't think this works in the FS as I believe the always-on type buttons just continually send presses until turned off, and no release. This is the config I have which is basically how you describe: [Buttons.PMDG737] 1=PB,8,C65966,1 -{THROTTLE1_DECR}- 2=UB,8,CPPMDG_B737_Eng_1_Reverse_Thrust_Kill,0 -{Preset Control}- 4=PB,9,C65971,1 -{THROTTLE2_DECR}- 5=UB,9,CPPMDG_B737_Eng_2_Reverse_Thrust_Kill,0 -{Preset Control}- 6=CR(+B,9)B,25,C65971,0 -{THROTTLE2_DECR}- 7=CU(+B,8)B,24,C65820,-1 -{THROTTLE1_SET}- 8=CR(+B,8)B,24,C65966,0 -{THROTTLE1_DECR}- 9=CU(+B,9)B,25,C65821,-1 -{THROTTLE2_SET}- However, the Throttle1/2 Set with a parameter of -1 doesn't seem to set idle reverse, and killing reverse starts forward thrust instead of idle forward. I'll see if I can take another look tomorrow.... I will check the parameter of -1 to see if I can change this to get idle, and also check what the controls Hold Throttle Reverse Thrust do... You can always use FSUIPC's logging facility to see what is happening on button presses and releases - best to do this with the logging console window open so that you can see the button presses/releases and events sent in real time. Note that I will be on holiday from tomorrow evening. back a week Monday.

Some issues with that version, try this one, 7.3.9c: FSUIPC7.exe

Here it is: FSUIPC7.exe

No idea...this is support for FSUIPC and WideFS, not Xplane or XPWide.

Then FSUIPC7 is not auto-starting... How are you starting MSFS? This is normal... So you are saying that FSUIPC7 auto-starts the 2nd and subsequent times you run MSFS, but not the first (after a reboot)...I don't understand this - there is no count on the number of times you start MSFS. This I don't understand either... Running the FSUIPC7.exe ONLY runs FSUIPC7, not MSFS. If you see the 'Preparing the cabin' splash screen, you are using the MSFS desktop icon (created by the FSUIPC7 installer) or the MSFS.bat file, and not the FSUIPC7.exe. Please try and start using the FSUIPC7.exe, i.e. go to your FSUIPC7 installation folder and double click the FSUIPC7.exe file, NOT the MSFS desktop icon created by FSUIPC7 installer as that starts MSFS and not FSUIPC7, as the name suggests... But if FSUIPC7 is just not starting the first time you run MSFS after a reboot, but works on subsequent attempts, then I have no idea what could cause thus. It is an MSFS issue, not an FSUIPC7 one, and I do not know why or how it could be doing this. It is not obeying the MSFS EXE.xml, so you should report this to Asobo. When this occurs, just manually start FSUIPC7 by double clicking the FSUIPC7.exe, and NOT the FSUIPC7 MSFS icon or MSFS.bat file. John

First, you posted in the Download Links sub-forum where it explicitly states NOT for support requests. I have moved your post to the correct forum for this question, which has also been asked many, many times before... Check the error 2 down from the one you highlighted. This will be an MSFS CTD. When this happens, you also get an fault (not a CTD) in FSUIPC7 as the FS has quit unexpectedly. If you check your FSUIPC7.log file, you will see that FSUIPC7 exited as MSFS was no longer available - and you may also see some SimConnect errors before this. If MSFS CTDs, report to Asobo. I cannot help with this. John

👍

See what the following lvars hold and how they change when you set TOGA: XML_Airbus_Throttle1_TOGA XML_Airbus_Throttle2_TOGA There are also the following, but probably less useful: TOGAPush TOGARelease If the XML_* variables hold the correct TOGA state, you could use those...

Ah, sorry - I think I misunderstood.... You have the TOGA button working, but the offset is not updated and so the motorized throttle doesn't see it... If that is the case, you need to determine if there is a different simvar or possibly an lvar that is updated instead. Once this has been found, you can either add that to a spare FSUIPC offset and use that, or you can add to an offset and spoof offset 0x080C to the value of the new offset. Try listing the lvars to see if any look appropriate. I will also take a look at some point to see if I can see anything... John

Many standard controls and offsets don't work with the PMDG 737 - you need to use either custom controls (using the Rotor Brake control) or presets. Presets may be easier, and looking at https://hubhop.mobiflight.com/presets/ I can see the following which you can try: PMDG_B737-7_AUTOTHRUST_TOGA_L_BTN PMDG_B737-7_AUTOTHRUST_TOGA_R_BTN Or assign to the Rotor Brake control, with a parameter of 68401 for the left button, and 68701 for the right button. To use the Rotor Brake control with the PMDG 737, see this FAQ entry: John

Could you try the attached version, v7.3.9c. This fixes a CTD caused in the WAPI (WASM API( that can occur when several config data updates are received in quick succession, usually caused by lvar creation in the WAPI/WASM. I don't think this is the cause of your CTD but worth trying. I have not been able to get a CTD with this version so far... Could you also enable debug logging in the WAPI, by adding the following to the [WAPI] section of your FSUPC7.ini file: LogLevel=Debug and show me your FSUIPC7.log file again if/when you get a CTD. John Later: beta version removed, some issues...I will repost at some point...

Stick with the current script - when updated on an event, the offset reverts back to 0 (when parking brake set) after a few seconds, and so needs to be continually updated. I did however experience a FSUIPC7 crash, and after restarting had difficulties accessing lvars. I will investigate. John

I am pretty sure they were for me...show me your FSUIPC7.ini and I will take a look (tomorrow now).

FSUIPC numbers buttons from 0, whereas windows starts from 1... FSUIPC certainly registers a release...but what button(s) are you talking about? What are you trying to do? What problem? I have a few other settings/configurations that I would like to try - didn't have time today, but will take another look tomorrow... I can also show you how I used this to prevent reversers activating from the throttle detent when reverser not activated. John

Ok, that shows the lua was sleeping when the crash occurred, so I doubt that is an issue. So it doesn't crash every time? How come the lua plugin log wasn't still active in that log? Yes - I wrote that script a while ago as an example. I will update to use an event when I get a chance and repost.