Search the Community

Upon starting FSX today, I encountered the error message shown below. It happened early last month, at which point I updated to the most current version of this software, but today the problem came back. Even after running this program in compatibility mode (which only worked for a few hours) this error message keeps popping up. My FSX Autosave and FSGlobal Real Weather engine depend on this software in order to function and I want to know how I can fix this error once and for all. Any suggestions would be appreciated. I would also like to underline that I have the most recent version of FSUIPC installed. I also have a copy of the FSUIPC4 Log file if you need that (see below) FSUIPC4 Install.log

*** Moved from FAQ to main Support Forum *** Hello how are you doing ? I hope you are well, well, my last option is to ask, since I get tired of looking everywhere and I have not found a solution for my problem and that has already discouraged me from continuing since I started doing scenarios for fsx but it happens to me the following I have the stage soon in ADE and when I want to test if it is working, I give it Connect now with the simulator open and what happens in photo 1 happens and then I have the simulator closed and what happens in photo 2 happens. Is there any solution that will help me? and forgive the inconvenience that I'm new to this hug (1)FSUIPC Error #2: FSUIPC_ERR_NOFS. Cannot find FSUIPC or WideFs running on this machine (2)FSUIPC Error #2:FSUIPC_ERR_VERSION.Incorrect version of FSUIPC

Hi, I'm new to this forum but have been building a set of switches and buttons with arduino by using the com ports and joystick functionality of FSUIPC. At first I used FSX and the aerosoft A320 bundle and everything was great (Also using FSUIPC v4), buy then i changed to P3D, Aerosoft's professional A320 and FSUIPC v5 and problems started. In the beginning I thought it was random. My plane would turn off at any point of the flight, sometimes twice if I was in the ground on the first shutdown. But then I've managed to find out that I can replicate the error when I plug a new device to the computer. The FSUIPC log will say "HID USB device reconnected: re-initialising FSUIPC connections" and in that point it wont read the actual state of my joystick switches. (For example, if the engine switches on the joystick are ON, FSUIPC will read all switches as off after the "sudden" reconnection, until I move any of the switches, and now it would read all the actual states of the switches, but at this point the plane is already off with several switches moved to zero positions) The thing is, to summarize, sometimes my PC (and i've tried on different PCs, reinstall windows and p3d and everything) reconnects all USB devices randomly on FSUIPC (not on actual windows since I dont listen to the connection sound) Maybe the device that reconnects are the bluetooth ones, but it doesn't matter, what I need to get working is to stop this "reconnection" of FSUIPC every time a new device is recognized by my computer.

Hi I've created a custom schedule and from testing it I am getting a lot of "=> ***** close cross incoming range" errors in regards to arrival aircraft. I did some initial research and found this topic but there is no set solution. I know this issue is to do with arrivals only. And that it is related to crossing runways - I personally am unsure how the sim calculates how an arrival is granted permission to spawn. I have uploaded the log file and uploaded a spreadsheet to help better understand what could be the issue here. Situation: Airport: KLAS Runway Setup: - 26L active (all arrivals) - 26R departures (commercial mainly - 1z Janet and 1z GA departure) - 19L departures (GA only) - 19R arrivals for GA that are transferred from 26L NOTE: I cannot make 19L an active as I require commercial aircraft only on 26L, which we cannot implement currently in schedules. If we activate 19L as well, then commercial aircraft will spawn on this runway which is something I want to avoid completely. All arrival aircraft spawn on time, up until SWA6885. This arrival is NOT the first one with the error messages "=> ***** close cross incoming range" but it is the first one that is considerably late. Onwards from here, 72% of arrivals from this point are delayed considerably. DAL2832 is the first aircraft to get the error message, followed by (in the order shown): DAL2832 - scheduled at 12:27 to land around 12:34 (spreadsheet contains this data) - between DAL2832 and SWA6885, there are x4 arrivals that spawn with no such error message SWA6885 SWA6448 WWI93 (GA) ASA1410 SWA3552 SWA541 AAL2456 N18ZD (GA) DAL1097 SWA378 UAL462 RSP137 (GA) What is happening (time stamp wise): @ 12:27, DAL2832 [arr] spawns on app to 26L > Lands @ 12:34:58 (on time) --- Between 12:28 and 12:37 all arrivals spawn on time & all departures spawn on time (i.e. pushback) @ 12:33:01, N93124 (GA) lines up on 19L & immediately starts her takeoff roll @ 12:34:07 JSX108 (GA) lines up on 19L & immediately starts her takeoff roll @ 12:34:55 JSX108 (GA) has taken off successfully @ 12:35:25 PWA454 (GA) spawns on app to 26L > Lands @ 12:46:55 (on time) @ 12:35:59 PWA454 (GA) begins her turn onto final approach for 19R @ 12:37:00 SWA5742 (arrival prior to SWA6885) spawns on time on to 26L > Lands @ 12:43:58 (on time) @ 12:38:00 SWA6885 attempts to spawn for the first time (denied with error "***** close cross incoming range") --- There are x4 attempts between now and 12:38:36 with the same error for SWA6885 @ 12:38:36 SWA6885 attempts again to spawn onto 26L - Even though there is more than 5nm seperation now to SWA5742 - There is also no GA landing on 19R or departing 19L - However PWA454 is on app to 19R - not sure how far out (I will assume 46 mins - 38 mins = 8 mins - So probably about to turn onto finals [basing upon the 7 min approach]) --- @ 12:41:19, I believe PWA454 turns onto finals for 19R as log state changes from "FINALRUNWAY" to "STATE_INCOMING" @ 12:38:51 LXJ528 (GA) lines up on 19R & immediately starts her takeoff roll --- SWA6885 is continuing to try to spawn @ 12:39:55 LXJ528 (GA) has taken off successfully @ 12:40:00 Now SWA6448 tries to spawn on time without success and the same error message -- PWA454 on 19R app. is now (00:46:55 - 00:40:00 = 7 mins odd) therefore about 13-15nm out from 19R -- SWA5742 on 26L app. is now (12:43:58 - 00:40:00 = 4 mins odd) therefore about 6/7nm out from 26L And so forth ... Why aren't these arrivals spawning when there is plenty of separation? It cannot be due to crossing runways because 26L and 19R or 19L do NOT cross according to the ADIRS radar. FORUM.xlsx 1st_attempt_log.txt

Was playing KBOS when I got a GetThreadContext Failed error. Attached are the files from the error folder created by steam. crash.dmp error.log output_log.txt

I found an error when attempting to pushback a cargo plane at JFK(the gates on QD) it just sits there and cannot find a route.(no route line ever gets drawn) Screenshot and log attached. Dev output_log.txt

Hi guys, I want to ask you about my problem. I have problem that i can't install FSUIPC for my p3d v3. the problem is the FSUIPC installer cannot checking the correct version of "p3d v3.exe". it's said that "Couldn't obtain Version Info! Asking user to find Prepar3D v3.EXE ..." and this is my FSUIPC installer log Installer for FSUIPC4.DLL version 4.949h Looking in registry for FSX install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"AppPath" ... NOT found! ... Looking in registry for FSX-SE install path: HKEY_LOCAL_MACHINE\SOFTWARE\DovetailGames\FSX Parameter"Install_Path" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\DovetailGames\FSX Parameter"AppPath" Not there, so looking in: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0 Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0 Parameter"AppPath" ... NOT found! ... Looking in registry for Prepar3D v1 install path: HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D Parameter"AppPath" ... NOT found! ... Looking in registry for Prepar3D v2 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2 Parameter"SetupPath" ... >>> OK! FOUND Prepar3D v2! <<< ... SetupPath=E:\Games\Lockheed Martin\Prepar3D v3 Looking in registry for Prepar3D v3 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v3 Parameter"SetupPath" ... >>> OK! FOUND Prepar3D v3! <<< ... SetupPath=E:\Games\Lockheed Martin\Prepar3D v3 ************ BUT this is the same path as for Prepar3D v2! Will only install for Prepar3D v3 ************ =========================================================== INSTALLATION FOR Prepar3D v3: SetupPath="E:\Games\Lockheed Martin\Prepar3D v3\" Checking version of the Prepar3D v3 EXE: Couldn't obtain Version Info! Asking user to find Prepar3D v3.EXE ... User identified path: "E:\Games\Lockheed Martin\Prepar3D v3" Checking version of the Prepar3D v3 EXE: Couldn't obtain Version Info! Asking user to find Prepar3D v3.EXE ... User identified path: "E:\Games\Lockheed Martin\Prepar3D v3" Checking version of the Prepar3D v3 EXE: Couldn't obtain Version Info! Asking user to find Prepar3D v3.EXE ... User identified path: "E:\Games\Lockheed Martin\Prepar3D v3" Checking version of the Prepar3D v3 EXE: Couldn't obtain Version Info! Asking user to find Prepar3D v3.EXE ... User identified path: "E:\Games\Lockheed Martin\Prepar3D v3" Checking version of the Prepar3D v3 EXE: Couldn't obtain Version Info! Asking user to find Prepar3D v3.EXE ... User identified path: "E:\Games\Lockheed Martin\Prepar3D v3" Checking version of the Prepar3D v3 EXE: Couldn't obtain Version Info! Asking user to find Prepar3D v3.EXE ... User aborted attempt to find Prepar3D v3. Installation failed. =========================================================== *************** End of Install Log *************** Last, i really need your help for resolve my problem. so desperate. Thanks, Azhari

I am having an issue installing FSUIPC into my steam version of Flight sim. I recently reinstalled windows 7, and have a fully updated os. I have already tried reinstalling flight sim, bot to no avail. Windows 7 FSX-SE Installation log: Installer for FSUIPC4.DLL version 4.938b Looking in registry for FSX install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"AppPath" ... NOT found! ... Looking in registry for FSX-SE install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0 Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0 Parameter"AppPath" ... NOT found! ... Looking in registry for Prepar3D install path: HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D Parameter"AppPath" ... NOT found! ... Looking in registry for Prepar3D v2 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2 Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v2 Parameter"AppPath" ... NOT found! ... ... NOT found! Asking user to find the .EXE instead ... User identified path: "C:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.exe" =========================================================== INSTALLATION FOR FSX: Checking version of the FSX EXE: ... Version 10.0.62607.0 (Need at least 10.0.60905.0) Checking compatibility with installed SimConnect: ... Failed to find a valid SimConnect needed to use FSUIPC4! A popup that says Your FSX installation is incorrect! The version of simconnect installed will not run FSUIPC4. You may need to repair the installation to rectify this first. No changes have been made by this program