John Dowson

Hi Detlef, the P3D window blackens when you open FSUIPC. When you press the escape key, that will close FSUIPC. Sounds like your screen resolution change has moved the FSUIPC window out of visibility. Try removing the ini parameter OptionsDialogOffset (from your FSUIPC5.ini file, located in your Modules folder), with P3D closed, and then restart P3D. Alternatively, go back to your previous screen resolution! Btw, you are using an older (and unsupported) version of FSUIPC. Please update to 5.152. John

You need to download an install the lua socket module. There is a FAQ entry on this.

Hi Ray. It won't be the firewall - this doesn't come into play when you are running programs on the same machine (with a local ip address). I don't know GIT - what is it using to talk to FSUIPC? Pete may know more, but you should probably try GIT forums or support.

You could try the log lvars.lua plugin (see the FSUIPC Lua Plug-Ins manual) which will list any lvars available for your aircraft. If any are listed, you can access these in lua and macro scripts. John

Please check the FSUIPC User Guide: p14: Throttle sync to sync Thr/Prop/Mix: When selected, this makes the Throttle Sync Hot Key (see the Hot Keys section) and the added Throttle Sync controls synchronise the Prop pitch and Mixture settings to the Engine 1 values, as well as the throttles. p17: Throttle Sync: This operates a facility to make all throttle inputs, for any engine, affect the throttle inputs to all engines. It’s a toggle function—if it is on then using it again turns it off. For best use of this facility you will want to also calibrate the separate throttles in FSUIPC’s Joysticks pages. If you are only using a single throttle then this won’t make a lot of difference except that every time you use it FSUIPC will make the throttle selection (i.e. the keypress E+1 ... etc) apply to all engines. However, it works a lot better even then if you’ve calibrated the throttle axis in FSUIPC’s Joysticks pages. If you also select the option to synchronise propeller pitch and mixture settings (see the Miscellaneous page), then the same Hot Key operates all three together. There again, if you are using joystick axes for propeller pitch and/or mixture you should calibrate them in FSUIPC’s Joysticks pages. If an assigned reverser axis is used whilst throttle sync is engaged, the sync action will be automatically cancelled. Note that this same facility can now be assigned to keypress or buttons/switches via the additional Throttle Sync controls in the drop-down assignments lists. As well as Toggle actions you can program On and Off actions separately. P43: CALIBRATING MULTIPLE THROTTLE, PROP & MIXTURE AXES TO "LINE UP" .....

Do you mean that you cannot see them in the assignments tab? Is this for all your devices or just the X-55? Could you post your ini, log and joyscan.csv files please (all in your modules folder). You can also try uninstalling the Saitek drivers to see if this solves your issue. Yes, you should disable power saving mode on your USB device hubs as this will prevent Windows from putting your devices to sleep. If you have a mixture of USB 2 and USB 3 ports, you can also try changing the USB port - some USB2 devices don't seem to work well with USB3 connections.

FSUIPC's Logging tab.

The size limit for the macro filename is 16 characters, including the extension. The limit for the macro names is also currently 16 characters. When using LVARS, the length for the lvar name is currently 32 characters, but has been increased to 64 for future releases and this update is also available in this post:

Your log file doesn't show much, except that that you keep losing your connection, which is strange. Did you not activate the suggested logging? You need to do this so that I can see what is being sent when you activate yout button. Maybe also post your ini file with your next log as well

You are still not providing enough information. When does it freeze? What are you doing? Does this happen in all the time? Only with PMDG aircraft or with all aircraft (have you tried with a stock aircraft)? Your FSUIPC4.log file would help. However, if the crash was not "immediate" then maybe you have a corrupt weather file -- a .WX file in your Flight simulator Documents folder, or possibly the wxstationlist.bin file in the same folder as your FS-SE settings (the AppData folder). deleting both would help in that case.

I see FS2Crew also recommend having repeat as fast as possible if using mute on a button, so you may need to play around with the 'ButtonRepeatRate' parameter to increase the rate. You can try with the following (one at a time, to see which works best): ButtonRepeat=50,10 ButtonRepeat=100,10 Or even unlimited: ButtonRepeat=0,10 Also, as you are sending this control on repeat, it makes no sense to also send it again on release, so remove entry no. 50.

Ah, ok. Not familiar with UGCX, but I can see that they repurpose this control as a soft mute on a 'push-to-hold' basis, so I guess that makes sense. Did you try logging to confirm that all your assignments are being used? Btw, John not Pete!

The propeller sync is a toggle - why would you want to repeat a toggle? Maybe this is ProSim related, which I do not have.

All entries will be recognised... Your first two (highlighted) entries are on key repeat ('R'), and the third entry is on button release ('U') - do you really want these on repeat? Try changing the 'R' to a 'P'. The 2nd and 3rd entries are also sendng the same control... Try logging 'Events (non-axis controls)' and 'Button and key operations' (from the FSUIPC Logging tab) to verify what is being sent when you press the button.

The initial value will not reflect the controller position - values are only received from the controller when it changes/moves. What do you mean by this? Do you mean that you cannot see the controller in FSUIPC, or you can see and assign/calibrate the controller in FSUIPC but it has no effect in FSX? Have you installed the Saitek drivers for the X-55? If so, try removing them. And controllers disabled in FSX?

When you re-assign, the entry will be updated. But I don't understand - why do you want to use this if it never worked?

Brief instructions (although you are better off reading the manuals!): Set up one control on your button. Open your FSUIPC ini in a text editor and locate that button entry and save it. Then re-assing your button to the second control (or keypress). Open your ini file again, and post the entry you saved at the end of the [Buttons] section (or your [Buttons.<profileName>] section if you are using profiles) , making sure to change the initial number of the line you posted to 1 greater than the last entry in that section.

If you want multiple assignments on a button, then you can only achieve this by manually editing the FSUIPC ini file. Please see the section entitled Button Programming in the FSUIPC Advanced User Guide, starting on p16. Alternatively, you could assign to a compound (or multi-action) macro - see Multiple actions in one macro control, p35. John

You do not need to remove FSUIPC to reinstall.

Ok. I have just ran some tests with multiple macro files being called from a single lua and cannot see any issues. You could also try logging Debug/Trace Lua plugins and maybe Events (non-axis controls) (from FSUIPC' Logging tab) to trace what is happening. You can also attach this log with your lua/mcro files.

You can monitor the axis values being sent by activating the 'Axis controls' logging from the logging tab. You can also monitor the throttle values by monitor the appropriate offset in the right hand side of the logging tab. For example, Throttle1 lever value is at 088C (2 bytes). However, as Thomas says, you may be better off sending to FS as a normal axis rather than using FSUIPC' calibration facilities. John

So you just want to remove FSUIPC and not solve your problem? Removing the Modules folder will (obviously) stop FSUIPC from running - you could also just rename the dll file so that it cannot be found. To remove FSUIPC completely, as well as removing the Modules folder, you can also remove the section in the dll.xml file (in your <user>/AppData/Roaming/Microsoft/FSX folder) which starts the FSUIPC4.dll. John

your FSUIPC4.log and FSUIPC4.ini files from your Modules folder, with the log file generated from a session when you had your issues What version were you previously using? There have only been very minor changes to FSUIPC4 in the recent releases... Did you upgrade anything else besides FSUIPC? John

John, not Pete! Could you post your ini file, your lua file and your two macro files and I'll take a look.

You can Reload all assignments from the Axis Assignment tab, or Reload all buttons from the Buttons + Switches tab. Yes, you should be able to refer to any loaded macro file. I'll look into this later, but could you check that the .mcro file & macro that you are referencing are correct (i.e. the .mcro file is loaded/referenced in your ini, and the macro name exists in that file).