John Dowson

First, you posted in the Download Links sub-forum where it explicitly states Not for support requests. I have moved your post to the main support forum, where it belongs. As for your issue, I cannot say as I don't have that controller, but I don't see why it wouldn't work. I can provide you with a tine-limited trial license if you would like to try. John

ipc.control takes the control number (n) as a parameter, as an integer. You are passing a string, Even though the sting holds the name of a local variable which holds a number, it is the string that is passed to the function, not the variable value. This should work: ipc.control(L_CDU_5 , Click_L)

I don't have the PMDG 737-800 so it is difficult to advise... Try activating logging for events, open the logging console window, click the button in the UI and see what, if anything, is logged. It is probably using the Rotor Brake control with a specific parameter indicating the action. The 737-700 uses the following, which is available as a preset: PMDG_B737-7_MCP_ALT_INTV_BUTTON : 88501 (>K:ROTOR_BRAKE) i.e. the Rotor Brake control with a parameter of 88501. Use logging, as advised, to check the same parameter is used, or use the one logged.

You could use lua. If the values you want to change are held in simvars that are writeable, then check if the simvar is already held in an offset and if so you can just write/update the offset value using the lua library. If the simvar isn't writeable, then there is most probablt an event you can use instead, which you can also send using lua ipc.control, e.g. for changing the time you probably need to use the Zulu Hours/Minutes/Day/Year Set control. See the Offset status document to see what simvars are held in what offset, and whether writeable or not. You can also check the MSFS/Asobo documentation on available simvars and events, and there is a file called Controls List for MSFS Build 999.txt which also lists available events/controls. For lua, check the FSUIPC Lua Library.pdf document, and maybe the FSUIPC Lua Plug-Ins.pdf and the provided examples (in Example LUA plugins.zip). John

Not possible at the moment, but I can add a new ini option for this. I will let you know when done. John

Well, if it works with other aircraft it sounds like its an issue for that specific aircraft, but as you don't say which aircraft this is I cannot help... Some controls work when assigned in MSFS but not wen sent from external applications, and this can be aircraft dependent., There are usually solutions around this issue, but I need to know what aircraft you are using. John

This is the first I have heard of this... Can you show me your FSUIPC4.log and FSUIPC4.in files please. John

Your log shows there are issues with duplicate ids in your registry, as well as a missing device: But your yoke and VPC joystick are detected, and the latter acquired for use, but with the same id as your Razer Tartarus Chroma: That is very strange,,, Could you also show me your FSUIPC6.ini file please - we can try using that to change/reset the ids. With the same devices? And all is ok there? If that is the case, maybe also show me your FSUIPC7.ini and an FSUIPC7.log file for comparison. John

Your ini shows multiple assignments, which is why they are grayed-out in the assignments tab: So when you press button 6, assignments 19 and 76 are triggered, so toggles twice resulting in the same state. and when you release, assignments 20 and 77 are triggered, again two toggles resulting in no change to the parking brake state. But I don't see how this could have worked with FSUIPC5, as the assignments are still the same. You can always set logging for Buttons & Keys as well as Events, open the logging console and you can see what is being sent when you press or release the button in real-time. This should tell you what is going on. Note that as you have overloaded/multiple assignments, you will have to adjust/remove these by editing the ini file directly rather than using the button assignments panel. John

Just installing FSUIPC6 should not do anything unless configured, and it certainly doesn't affect anything visually, so something else must be going on. What happens if you rename the FSUIPC6.dll (e.g. to FSUIPC6.dll.unused) so that FSUIPC6 is not loaded?

First, you posted in the sub-forum for FSUIPC7 / MSFS2020. As you are using FSUIPC4 and FSX-SE, I have moved your post to the main support forum. Which throttle axis are you using? Did you try other throttle axes? If not, please do. And are you calibrating with a reverse zone or not? I am not familiar with the Eaglesoft C750 2.0, but maybe check the configuration for that aircraft, as some Eaglesoft aircraft require to be configured, e.g. see this for the Eaglesoft Citation: https://www.avsim.com/forums/topic/377514-eaglesoft-citation-x-problem-with-idle-and-throttle/ Otherwise, please show me your FSUIPC4.ini and FSUIPC4.log files, the latter with axes logging enabled and move the throttle through its full range and exit. John

Please see APPENDIX 3: Handling VRInsight serial devices in FSUIPC on page 60 of the FSUIPC7 Advanced User guide, as well as the additional document Lua Plugins for VRInsight Devices.pdf. John

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