John Dowson

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).

Hi Eric, What do you mean by this? Is FSUIPC installed and running ok? Could you post your log and ini files please, and maybe also your install log if FSUIPC4 is not installed correctly. Thanks, John

Could you try the following dll which should ignore the spaces - haven't had time to test this, sorry, so please report back: FSUIPC5.dll

Yes, sorry - missed the JoyScan.csv file in the initial post. As Thomas says, try editing the registry to remove the space from the start of the device name. I'll check with Pete to see if I should update FSUIPC5 to handle this automatically. Cheers, John

Your Yoko is also missing: Y=VirtualFly - YOKO+ << MISSING JOYSTICK >> Is this attached? Could you also please attach your FSUIPC5.JoyScan.csv file. There may be a problem in FSUIPC5 if the device name starts with a space, which is very strange. I'll take a look at the code over the weekend. Cheers, John

Mouse macros do not work well with PMDG aircraft, you are better off using custom controls. Please see this post:

There is no 'best response curve' - it is totally up to personal preference, and may also vary from aircraft to aircraft (via using the 'profiles' mechanism). FSUIPC is hardware independent - there are no recommended settings for particular hardware. Just try different slopes and stick with what feels good for your hardware/aircraft. John

Hi, generally it is not recommended to use the SAITEK drivers when using FSUIPC. Try uninstalling them and see if your device is recognised by FSUIPC without them. John

Hi, usually such issues are caused by the editor adding a .txt extension to the file name - check the file extension is correct, and if not then rename. If thats not the issue, can you attach your FSUIPC4.ini file and your 1F111.mcro file. Any macro files found in your directory should be in your ini in a [MacroFiles] section. John

Hi Ray, looks like it was due to the size allocated to the drop-down entry (composing macro file name + lvar name) being too small. Please try the attached version. Cheers, John FSUIPC5.dll

You are also using an old (unsupported) version of FSUIPC5 - please update to the latest version, 5.152. John

Hi Ray. I just checked this and it worked for me, although I invented an LVAR name that didn't exist. This is what I got in my ini: 11=PT,0,CM1:1,44 -{Macro longMacro: L:MyExtremelyLongLvarNameToCrashP3DWhenUsed set}- The lvar name is truncated in the UI, but can still be selected and used. I'll need to investigate further. John

Hi Ray, Ok, thanks - sorry I didn't have time to check this last night. I'll take a look and get back to you with a new version later today (hopefully!). John

Hi, presumably, from your ini, your taxi lights are assigned to a button that stays in when pressed (i.e. no release), and then releases when pressed again? i.e. 112=P4,9,C69749,1 -{Custom control: <69749>}- 113=U4,9,C69749,0 -{Custom control: <69749>}- You have the same on your 777 but on a different button, which, as you say, works for you, which is strange. Also, if the same happens when you activate in the sim overhead, then it does sound like a PMDG issue. There are no events in your log - did you activate this as advised by Thomas? If not, can you activate logging for 'Button and key operations' and also 'Events (non-axis controls)' (from FSUIPC's Logging tab), and produce another log file that shows the taxi lights being activated. John

Hi Mark, for install error 1332, you can manually edit the Modules folder permissions yourself to allow full access, by right clicking on the folder properties: select Security-->Edit-> Add, enter Everyone as the object name, then 'Check Names' and 'OK'. Then give 'Full Control' to the Everyone group just added. John

Hi Ray, please try the following dll (5.152c) - I've increased the max space for LVAR names from 32 to 64 characters. I haven't tested this yet, so please let me know if there are any issues. Cheers, John FSUIPC5.dll

Hi, sorry for the late reply... What version of MakeRunways are you using? Did you check the MakeRunways documentation? For P3Dv4, MakeRunways uses a special version of the Lorby-Si add-on manager (included with MakeRunways) to generate a scenery.cfg file that it can use that contains the scenery from various add-on xml methods. Therefore, please check that you are using the latest version of MakeRunways and check the documentation. John

Hi Stu, please try the attached version (5.152b). John FSUIPC5.DLL

Hi Stu, Thomas, I'll take a look at the changes and build a new version for you to try. I'm a bit busy at the moment so it may take me a couple of days. John

Hi Daniel, do you have anything in the windows event log for the crash? If so, could you please post it. Thanks, John

Hi Rodger, your FSUIPC license for FSX-SE is for FSUIPC4. This license is also valid for P3D version 2.5, 3-3.4 (all 32-bit). If you are using P3Dv4 (64-bit), you will need to purchase a license for FSUIPC5, available from SimMarket. Regards, John