Thomas Richter

But did you check the manual? Thomas

Hi, you cannot modify the settings direct in FS via FSUIPC for Ground Vehicles, but for Airline/ General/ Ships & Ferries in FSUIPC there is a Hack that controls those via Offset (check Offset Status List), Offsets 0x0250 / 0x0251 / 0x0252. But you can for FSUIPC4 and FSUIPC5 use the new Facilities under [Traffic Limiter] in the INI file, but also controllable via Offsets, 0x86E0 to 0x86E7. Thomas

Because something on your system decides so. Did you re-download the installer ? The installer does check P3D and its version but only to make sure the P3D is not older than the minimum required version. The installer does not check if the P3D version is in a higher version with FSUIPC. But in any case it does not force FSUIPC_Installer to crash at all. The installer in your case crashes before it is doing anything, even a messed up Registry would be noted but not forcing a crash. In case you are here the only one with that problem there is something on your system that forces that crash. That what it looks like with P3D HF1 and 102 / 103 That's on Win10 with MS build Antivirus (defender) only. Thomas

Hi, the hotfix has nothing to do with it. The installer looks the registry up to find the correct location of the xml.dll file to place the entry for FSUIPC there and also to know where the P3D is installed on the system. If the entries in the registry are not correct or missing you will get an error message in the log file but the installer does not crash at all because of that. You have definitely a problem on your system and I still think it is related to a Virus checker. I would go and re-download the installer and unpack it into a low level folder on a fixed installed drive, when P3D was installed with admin rights then the same for FSUIPC installer by mouse-right-click ... Thomas

Hi, is the 102 installer folder as well located on the desktop like it is for the 103 installer? I always have an folder on C:\xxx to ensure it is not in one of those Windows secured places. Thomas

Hi, checking for Exception code 0XC0000005 I found most likely I would expect the problem is a Antivirus program on your system, in case no one else seems to have a problem. Or the permission you use to run the Installer doesn't match the permission you used to install P3D. Thomas

Hi, that looks like you don't unzip the whole to a separate folder first? Not a good idea at all. Just unzip the files first into a folder and from their start the installer. Thomas

Hi, when on P3D start you get noticed that FSUIPC is already running then it means that actually P3D in its last session never proper closed, has to be closed manually in TaskManager. Make sure you use latest Install_FSUIPC5103.zip because any earlier version might not work proper when P3D's hotfix 1 is already installed. Also please send the FSUIPC5 Install.log to see where it stops. If P3D process is still running in the background the installer will crash because of no access to the already installed FSUIPC5.dll. Thomas

Hi, I don't know on which Windows you work. Here I connected the Avionics stack to a Windows 10 Pro PC (Windows 10 Pro 64 Bit reported as Build 15063, Release ID: 1703 (OS 10.0)) doesn't work Then connecting it to good old Windows 7 Pro PC I get, and fully working Also It was before connected to Windows 10 Pro but the first released version and the Avionics stack worked also perfect. So if you run on Windows 10 latest version it seems the problem is in Microsoft's hands. Also by looking into the hardware properties of the recognized PFC device on Windows 10 PC I see that device could not be started with error code 10. The device itself displays fast flashing dashes on the displays but steady dashes on Windows 7 PC (device could be started). You say it works OK with xPlane, is that on the same PC and same Windows? Thomas

Hi, did you try with latest version PFChid.zip (1.49) and of course latest FSUIPC4.969 version Install_FSUIPC4969.zip ? Thomas

Hi, as your FSUIPC log file shows you use PMDG add-on aircraft and it is here and also in the FSUIPC manual very clear described to DON'T use AutoSave facility in FSUIPC because PMDG forces FS/P3D to freeze for the time of saving and because PMDG saves a big bunch of data that forces SimConnect to stall. The SimConnect stall will result in a disconnection of all SimConnect related programs. 108890 E:\P3D v4\SimObjects\Airplanes\PMDG 777-200LR\B777-200LR.air There is NO workaround that other than don't use AutoSave. What you could do instead is assigning a key in FSUIPC or FS/P3D to save the flight, then any time you want. Thomas

Hi, that doesn't tell anything about a problem you might have? Best would be if your problem is not related to this topic to just start a new topic and describe precise what your problem is. Also having some information about the used versions does then help in addition, FSUIPC5.log file. Thomas

Hi, please install latest Install_FSUIPC4969.zip . If you still have any problems then please send the following files with your message. FSUIPC4.ini FSUIPC4.log FSUIPC4.JoyScan.csv Thomas

Hi, if you are trying to register with a FSUIPC4 key that will not work, FSUIPC5 needs a new registration key you would need to buy from SimMarket. If you bought already a FSUIPC5 registration key and you have problems please copy and paste the content of the FSUIPC Install log file to your message. Thomas

Hi, good that is sorted. What do you mean by 'Now on to the next issues.' Are those related to FSUIPC5 ? Thomas

Hi, there is no FSUIPC.exe file because FSUIPC ist not a standalone running program you can just start. Older FSUIPC.dll files are not available because they are not supported. Best is to describe your 'many problems' to help instead ! Thomas

Hi, FSUIPC5 is a new independent product, the FSUIPC4 key does not work. You will have to buy a new registration for FSUIPC5 at SimMarket. Note the WideFS registration from that you might have used for FSUIPC4 will still work, just in case you used that before already. Thomas

Hi, in that case you have three options. 1/ you change the trim effectiveness in its aircraft.cfg (located in the folder of the used aircraft), most effective, where you change the line elevator_trim_effectiveness = 1.0 to a lower value i.e. elevator_trim_effectiveness = 0.75 or less 2/ you can use slope in FSUIPC calibration that will reduce the amount send in low range but still the full range at each end 3/ you can manually increase the full range in FSUIPC4.ini file, normally the value would be i.e. 16383 and -16383 and you change those values to i.e. 22000 and -22000 Thomas

Hi, I guess you use a standard AC and not a add-on like A2A / PMDG / ... ? If not it might not work because mostly add-on AC use their own internal logic and gauges to control stuff like that. Thomas

Hi, FSUIPC is an interface to FS that uses SimConnect and provides an easy way for add-on programs to use that, internal there are lots of facilities to use (when registered) like Joystick, buttons, keys ... As the link I added says in their forum it works correct (30th of June 2017) it must be something on your side. Btw- I guess you use latest FSUIPC5.103 and 5.103b over it. Thomas

Hi, in case FSUIPC5 has nothing to do with that program it doesn't need to be compatible with something that uses FSUIPC. Make sure the version 'vafs' is compatible with FSUIPC5 or P3Dv4 instead. Often programs use a FSUIPC version check and that version number has of course changed for FSUIPC5. Maybe it uses also or only SimConnect and that is fo course not compatible with any older versions. So you are better of to ask that in 'vafs' forum than here. Also as their page says ... actually P3Dv1-3 and special P3Dv4 is not listed at all? Later: here is a link that it does work with P3Dv4, so best is to stay in contact with them anyway. http://forums.myvafinancials.com/viewtopic.php?f=6&p=23745#p23745 Thomas

Hi, for some reason those devices have the same GUID and ID, where they are unique in Windows (should be). 156 Device acquired for use: 156 Joystick ID = 3 (Registry okay) 156 3=Saitek Pro Flight Quadrant 156 3.GUID={4667AD50-4C6F-11E7-8001-444553540000} 156 Device acquired for use: 156 Joystick ID = 3 (Registry okay) 156 3=Joystick - HOTAS Warthog 156 3.GUID={4667AD50-4C6F-11E7-8001-444553540000} Can you please download and run the HidScanner (from Useful additional programs) and send as well its log file. Thomas

Hi, please copy and paste the following files after a short session and a fully closed FS (P3D), FSUIPC5.ini / FSUIPC5.log / FSUIPC5.JoyScan.csv Thomas

Hi Urs, First, there is never a space (Leerzeichen) used, means it would be ServerName instead. But when ServerName= is used then you need to use a name and not the IP-Address ! So by using the IP-Address your entry in the INI file is then: ServerIPAddr=198.168.1.153 Picture: Make sure you use for all connected PC's the same Subnetzmaske (in your case 255.255.255.0)and the same first three numbers of the IP-Adresse (192.168.1.xxx). Also take care all PC's are in the same Netzwrkgruppe (name). Thomas

Hi, you need to use the registration info from the time of registration, exactly and independent of the current email address. Best is to copy and paste the info, Name/ email/ key, instead of typing to prevent error. Thomas