John Dowson

Do you mean you cannot open FSUIPC7? Is it starting - do you see an FSUIPC7 splash screen? Have you looked in your system tray to see if its there? If it is, you can open it from there or use the (default) hot-key Alt+F to open the FSUIPC main window. If your issue is that FSUIPC7 is not auto-starting with MSFS, there are already many threads on this issue - check them for a solution. Have you assigned and calibrated it? Does FSUIPC7 see this yoke? You really need to provide more details if you want further help. I do not even know if you have FSUIPC7 tunning at the moment... John

This is basically correct - the *_EX1 controls don't go through FSUIPC's calibration. However, you can do more than just reverse - you can perform scaling on the axis values (see P41 of the Advanced User guide, section Additional parameters to scale input axis values). FSUIPC's tiller axis blends rudder and tiller controls and the blending can be controlled by various ini parameters - see the box on page 30 of the User guide for details on how this works. If you don't want to use rudder/tiller blending, then assign directly to the FS tiller control rather than the FSUIPC added one, and scale or reverse as needed. John

This is a problem with MSFS. The FSUIPC WASM module just scans for lvars whenever a new aircraft is loaded, and reports what it finds back to FSUIPC7. It sems the MSFS returns many lvars used in both previously used aircraft and for aircraft sitting in your Community folder that have not been used. This can create issues as currently only a maximum of 2044 lvars are returned from the WASM to FSUIPC7, and so if you have an aircraft such as the FBW A320 installed in your folder, many of the lvars will be for this aircraft, reducing the number available (or returned) for the current aircraft. Note that when the WASM scans for lvars, there is no way for it to know if the lvars are for the previously loaded aircraft or an aircraft just installed in your Community folder - as far as the WASM and FSUIPC7 are concerned, they are the lvars that are currently available. Due to this, it is recommended to clear your Community folder of all aircraft before starting MSFS and just leave the one that you want ti use for that session, and most people use the MSFS add-on linker for this. There is not much I can do about these extraneous lvars - this needs to be addressed by MSFS / Adobo. I could increase the number of lvars passed back from the WASM to FSUIPC7, but the current limit (2044) should really be enough. I may consider increasing this (to 3066) in a future update, but it will take me a while before I have time for this. This has been reported before: John

You need to add a compound button condition, which allows for different controls to be sent when a button is pressed depending on the state of another button. See page 21 of the Advanced User manual. It is not that difficult - please read the document and try it before posting for assistance. John

Please do not post support questions in the FAQ section - use the main forum for FSUIPC6 support. And you need to give details if the problem you are having, what you have trued, etc. There are a large number of posts on how to configure for PMDG aircraft already - I suggest you check the forum before posting again. John

If you had checked your install log, you can see the reason and what you need to do: I think this failed as The Type attribute on the SimBase.Document node is "SimConnect" when it should be "Launch". This must have been written incorrectly by one of the other addons that have updated your EXE.xml file (noolaero-module-vdgs or FS2Crew Command Center). I have corrected this and added the auto-start for you in the attached exe.xml - download this and use it to replace your current one. John exe.xml

Alt + F (left or right) is the default hot-key for opening the FSUIPC main window. If you want to use that for something, you can change it - see the User Manual. No, but I have received several support requests about this. I am trying to get some information from PMDG about this, yo see if they are providing the additional offset data as they do for P3D/FSX versions...

I do not have the PMDG 737 so cannot advice how to set this up. Most probably the AP_ALT_VAR_INC and AP_ALT_VAR_DEC controls do not work for that aircraft. Read that topic I referenced on how to use PMDG custom controls, then take a look at the PMDG header file for the aircraft you are using and see if there are any custom controls that you can use instead and assign to them (following that tutorial).

Sorry but I have no idea what you mean... and DONT attach screenshots - explain what you are trying to do, what your issue is, an attach your FSUIPC log and ini files. If using the PMDG 737, be aware that many of the standard controls do not work. You need to use the custom controls provided by the PMDG SDK. See John

Ok - what did you change? Did you try: RunIf2=READY,KILL,"C:\Users\FLIGHTSIMPC1\AppData\Local\vPilot\vPilot.exe" -host -voice as advised?

Your FSUIPC6 is also out-of-date and needs updating - you are using 6.0.8 and the current version is 6.1.8. However, there is a problem with that version when setting payloads through ProSim. This is fixed in 6.1.9a which is available in the forums somewhere, and which I will release very shortly - probably tomorrow (if I get time...) John

No, that is not what I have said. The previous error with ProSim is that it was previously set to tun as admin and FSUIPC7 not. I also said nothing about changing vPilot to run with admin. Please re-read my previous comment and follow those instructions. If this still doesn't work, show me both your ini and log files. John

What does this mean? I don't understand this either... What version of FSUIPC were you previously using? If not 7.3.3, download and install that first (to also update the WASM), and then download the 7.3.4d version above again and use that to replace the 7.3.3 FSUIPC7.exe. If you weren't previously using 7.3.3, then your currently installed WASM is probably out-of-date. John

Error 2 is file not found - are you sure this exists: C:\Users\FLIGHTSIMPC1\AppData\Local\vPilot\vPilot.exe ? If so, change the run line to: RunIf2=READY,KILL,"C:\Users\FLIGHTSIMPC1\AppData\Local\vPilot\vPilot.exe" -host -voice or maybe just: RunIf2=READY,KILL,C:\Users\FLIGHTSIMPC1\AppData\Local\vPilot\vPilot.exe -host -voice Error 740 indicates that you need elevated privileges to run the program. So you run ProSim with admin privileges? If so, try setting FSUIPC to also run with admin privileges. Otherwise, change ProSim to run without admin privileges. Note that setting FSUIPC7 to run with admin privileges may prevent MSFS auto-starting FSUIPC7 - this has been reported in another topic. If this is the case, then first try running FSUIPC7 manually to check the run commands work. If you decide you need to run with admin privileges and FSUIPC7 is not auto-starting with MSFS, then you can go back to the old method of starting FSUIPC7 (via the MSFS.bat file). Check the forums on how to do this. John

I really can't advise on a specific card - especially when you don't give a version/model number, or say what type of device it is (HID or COM?). FSUIPC (all versions) only recognise HID joystick type devices for direct assignments. Other HID type devices can usually be used via the lua com interface. There have been other support requests regarding pokeys cards - maybe try searching the forum (FSUIPC / FS version not relevant). Here's one such request: Also, there is a User Contribution for pokeys55T / pokeys56U / pokeys55E cards: You can also just try it to see if recognised - there is a trial license available in a post at the top of this forum if you do not have a license. John

Your FSUIPC7 version is out of date - you are using 7.2.6, and the latest (and only supported) version is 7.3.3 - please update. Always check that you are using the latest version before requesting support as only the latest version is supported. Try changing Programs section: to If that doesn't work, I need to see your FSUIPC7.log file as well as your FSUIPC7.ini (and only after you have updated to the latest version). John

Discussions on this topic have been continued in the following similar thread/topic: Please use/refer to that thread instead. I will close/lock this topic. John

Hi @mtjoeng, please try the attached version, v7.3.4d. Download and replace your current FSUIPC7.exe with this one. Note that any previous key assignments using the shift, ctrl or alt modifiers will now use the left keys. You could previously assign to right shift and ctrl (but not alt) but these assignments were not correct - if you have any such assignment then the modifier key will be removed, so maybe best to just remove these (from your FSUIPC7.ini) file beforehand, if you have any. Maybe also take a backup of your FSUIPC7.ini first, just in case. John FSUIPC7.exe

Can you please attach your FSUIPC7.ini and FSUIPC7.log files so I can see how you are starting ProSim and if any errors are logged. John

Btw, this also looks suspicious (but not related to your issue): 30031 *** LUA Error: ...x86)\FSUIPC7\l... You haven't installed FSUIPC7 under your Program Files(x86) folder have you? You should not install FSUIPC7 under windows protected folders (Documents, Program Files, Program Files (x86), etc). If you have, you should re-install into a non-windows protected folder. John

I wouldn't delete that if you are using Linda for other aircraft.... I think you need to provide more details - your complete FSUIPC7.log as well as your FSUIPC7.ini would help. Are you using Linda at all? Something is obviously calling a Linda script, so I presume you have it installed for something. If you weren't using your MSFS PMDG 737, what aircraft were you using? If you are using various 737s (e.g. PMFG, Asobo, FBW) you should make sure that you have different profiles for each. John

Do you mean Throttle 1 Dec? Try Throttle Dec instead (although this is for both throttles/engines). Ok, so the MSFS PMDG uses the rotor brake control with the parameter indicating the actual custom control being used. Good to know, thanks. John

Note that we discussed this before (nearly 1.5 years ago now) and I provided you with a script that gets numeric input via lua using the wnd library - see John

Looking at this I have realised that I have made a mistake in the position of the parameter - as the total length of offset 0x7C50 is 72 bytes, I should have but the preset parameter at offset 0x7C94, allowing for 68 bytes for the offset name. Or, probably better, allowing 8 bytes for the parameter so putting the parameter at offset 0x7C90 and allowing 64 bytes for the name. I will leave this for now, but may have to update if preset names get larger than 48 bytes. John

FSUIPC should certainly not make MSFS stutter... I am slightly confused by your issue - when you say 'When i have FSUIPC open', do you mean the FSUIPC window open/visible, or just when FSUIPC7 is running? You can try running FSUIPC7 with the logging console open (Log -> Open Console). When you experience the stutters, see what (if anything) is logged in the console when the stutter occurs. Take note of the starting/ending times of the stutter in the log messages. When you have finished, exit MSFS (or just FSUIPC7) and attach your FSUIPC7.log and FSUIPC7.ini files and I will take a look, and also tell me the timestamps (from the log) where the stutter(s) occurred. John