Thomas Richter

Hi, as you can read already in different topics there is a problem with FSUIPC5.123c but you will have to wait for Pete, he will be back on 20th. Thomas

Hi, follow this (from FSUIPC History.pdf) Thomas

Hi, best is when having a question to open a new topic instaed of writing into an completely different one and doesn't have anything to do with your question. It just confuses the original topic. The key you bought from SimMarket will only work with the FSUIPC version you bought it for. Each version has its own key, - FSUIPC3 for FS9 and earlier - FSUIPC4 for FSX / FSX-SE / P3Dv1 to P3Dv3 - FSUIPC5 for P3Dv4 (64Bit) only WideFS is slitely different - WideFS for FSUIPC3 (FS9 and earlier) - WideFS7 for FSUIPC4 and FSUIPC5 If you bought WideFS for FSUIPC4 or FSUIPC5 then it will work for both, either way. Thomas

Hi, Pete told me FSUIPC5.123c will work wit P3Dv4.2 as he tested everything with the Beta but it looks like there there must be a last change with the release version. Here are links to: FSUIPC5.122 FSUIPC5.123b Thomas

Hi, but in case that was never reported before FSUIPC5.123c, at least not that I remember, it cannot really have to do with FSUIPC5.123c when you have the same effect with 5.121c and 5.122 (I guess). Which Windows is used, maybe another nice MS update? Btw - No problem here, but I don't have any Add-ons installed at all. Thomas

Hi, as there is already a problem please the complete FSUIPC5.log file after FS was fully closed the log file complete written. In case the rest of the log file is missing it doesn't tell much. Does FS fully close? Thomas

Hi, did you disable Controls in FS? Thomas

Hi, there must be something mixed up in Windows registry as FSUIPC gets its information from Windows registry. Thomas

Hi, please attach the FSUIPC4.log file as it give maybe some more information. Thomas

What else software is installed, like for the others that have the problem with EZdock and ProSim? Also you didn't show the requested files? Please also check that the dll.xml file contains the FSUIPC entries on last position. Thomas

Normally you get a CD with a driver software delivered. This might 'map' buttons they physically don't exist as controller buttons and uses maybe a virtual controller for additional axes. FSUIPC cannot see those mapped buttons or virtual axes, as long it is not a real virtual controller. Just check there is no Saitek software installed/ running. Please also send this files, attached or zipped: FSUIPC5 Install.log FSUIPC5.ini FSUIPC5.log FSUIPC5.JoyScan.csv Thomas

Do you have any Saitek software installed for that setup? Thomas

Hi, someone else reported it happens with ProSim running Very strange as FSUIPC uses a standard Windows facility as its window. I cannot check here as I don't have either of those add-ons. It might have to wait until Pete returns and he uses Prosim as well. Thomas

Hi, please update to latest supported Install_FSUIPC4972.zip Run the installer and then FS. After that place and overwrite with FSUIPC4972a.zip but please first run the installer (above). It works fine here, FSX under Windows 10. Thomas

Yes, as I said max 32 buttons are supported per controller if the controller itself supports 32 buttons. Also max 8 axes per controller. Thomas

Hi, max 32 Buttons per controller, if the controller supports 32 buttons. Controller with more than 32 buttons are only supported up to the 32nd button. Thomas

You should see all axes and buttons windows recognise, while moving you can of course identify. Thomas

Hi, did you correct install Lorbi-DI Addon Organizer? If not then MakeRwys will not find it, it looks the registry up for its installation path. Here it works correct. Thomas

Hi, you need to check in Windows Gamecontroller Settings that all axes are shown and functioning there. Thomas

Hi, In FSUIPC5.ini file, the section is already there in your file with = No So just change that to Yes This is from Your FSUIPC.ini file [JoyNames]AutoAssignLetters=No The dll.xml or exe.xml are never in \Modules\ folder, if you didn't placed them there. FSUIPC doesn't move those files but adds entries to start FSUIPC to the dll.xml file. Those files are located in ...\AppData\Roaming\Lockheed Martin\Prepar3D v4\ folder. There is no Uninstall for FSUIPC other than deleting files. So if you want to keep previous settings just don't delete the FSUIPC5.ini file. Yes please, they might give some information. Do a FSUIPC5 installation and run FS, do this opening of FSUIPC the three times (with couple seconds in-between) and close (if possible) FS and wait all files are written. Thomas

Hi, First question at all; are all axis of the Throttle-2 (PS/2) seen in windows controller setup? FSUIPC can only see Controllers/ Joysticks Buttons and Axes that Windows itself does see. Thomas

Hi, best is to show the FSUIPC4.ini file with the saved values and the FSUIPC4.log file. Thomas

To eliminate those AC's as the source, did you try the same flight with a default AC? Thomas

It shouldn't but maybe PMDG causes a SimConnect stall when in time acceleration.? Do you use as well latest FSUIPC5.123c ? Thomas

Hi, it is not FSUIPC that quits but SimConnect stalls and in case ALL applications that uses SimConnect will stop working, and of course any application that uses FSUIPC as well. Does the SimStall uses SimConnect to communicate with FS? Later: Their web page says you need FSUIPC for FSX/P3D. But doesn't say it is compatible with P3Dv4? Thomas