gdavej

I just bought FCR v5.0.2304.1, and I'm using it with MSFS. When I select the tool from the MSFS toolbar, and hit Record, it does seem to record the flight, and indeed the Stop button appears to stop the recording, but I don't seem to be able to load the flight using the Load button. When I check the contents of the folder where flights are saved, I see a flt file and spb file with the correct file prefix, but no fcr file. I believe I need a fcr file as well in order to load the flight. Why am i not getting a fcr file? I'll attach an image of my options below.

Not sure how I can calibrate the joystick with FSUIPC, if I can't load FSUIPC in P3D when the joystick is plugged in. I tried starting P3D, after killing the Saitek software, but joystick still connected, and P3D died again when it tried to load FSUIPC. I also tried starting P3D without the joystick, and this started normally, but died the instant I connected the joystick. The update to v4.3 was made using only client and content. I can't see why this would cause the problem I'm seeing. However, before the update, P3D was starting okay with both FSUIPC and the joystick. After the update, P3D would start with either FSUIPC or joystick but not both. The only other change I made would be with ActiveSky, I installed the beta version for P3Dv4.3, and this of course installs simconnect in P3D, don't know if this has any impact?

Guess I spoke too soon 😞 I just updated P3D to v4.3, and immediately started having the same issue again, whereby P3D crashed as it tried to load fsuipc5.dll. I tried installing the latest v5.132c, still no change. I tried completely uninstalling the Saitek drivers and software, and reinstalling first the Saitek drivers and software, but later the new Logitech drivers, and software; and still P3D crashes. I did switch back to the Saitek installs, since the new Logitech seemed to lack a few things (like calibrating the joystick) I'll attach the fsuipc log, although it looks identical to the last one (except for the first 3 segments of the GUID). The event viewer gives pretty much the same as well (except the hex values) Faulting application name: Prepar3D.exe, version: 4.3.29.25520, time stamp: 0x5b2c3263 Faulting module name: ucrtbase.dll, version: 10.0.17134.137, time stamp: 0xeafbf647 Exception code: 0xc0000409 Fault offset: 0x000000000006d198 Faulting process id: 0x4b58 Faulting application start time: 0x01d4156c2baa6dfa Faulting application path: D:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe Faulting module path: C:\WINDOWS\System32\ucrtbase.dll Report Id: 8db0b29b-95aa-4afb-8282-90be86c8213a Faulting package full name: Faulting package-relative application ID: I have tried several times to uninstall and reinstall, but with no joy. David FSUIPC5.log

Thanks Pete, That did the trick. Sorry I was so slow responding, but I wanted to test a few times, make sure that the issue had well and truly gone.

Here's the hidscanner and fsuipc5 logs. Also the event viewer gave: FSUIPC5.log HidScanner.log

Three days ago, I updated my Windows 10 Pro OS with the 1803 Feature update... bad move on my part. Since then, I've had problems with P3Dv4.2 starting. It would suddenly die, before getting to the start screen. I have a lot of entries in exe.xml and dll.xml, and I tried commenting out entries, until I discovered that the culprit seemed to be FSUIPC v 5.131. Before the 1803 update, I never had a problem with either P3D or FSUIPC. I believe the problem is related to the Saitek X52 Pro joystick, since the FSUIPC log seems to stop abruptly whilst scanning the joystick. I'll attach both the FSUIPC5.log and FSUIPC5.JoyScan.csv. I have a registered copy of FSUIPC. FSUIPC5.JoyScan.csv FSUIPC5.log

Hi Thomas Looks like uninstalling and reinstalling the Saitek joystick drivers and software did the trick. I can now start P3Dv4 with both the registered FSUIPC and the Saitek joystick. Thanks for all you help. David

Hi Thomas I don't have another joystick. Wrt uninstalling the driver, I found a YouTuve video showing how to do this, but I stumbled at the first step, finding X52 in the HID section of DeviceManager. Problem was that I was trying to uninstall whilst the joystick was not connected. I'll have another go at this, and will report back tomorrow. David

I can wait for Pete to return. I can, of course, run FSUIPC in unregistered mode with the joystick, and I currently use the Saitek software to program the joystick, so not crucial at the moment. Thanks for your help. Should I resubmit this issue later? or will Pete see this is still an open issue?

Yes, there's a Saitek driver installed (Saitek_X52Pro_Flight_Controller_7_0_53_6_x64_Drivers). Can't find any way to uninstall these drivers, so I just reinstalled the driver. Still get the same crash.

Hi Thomas Test #1: As soon as I connected the joystick, bang, P3D crashed. Test #2: Connected the joystick through USB hub (using a laptop with only 2 USB 3 ports). Same story, P3D crashed as soon as it tried to load FSUIPC Test #3: Attaching the log from HidScanner. FSUIPC5.log FSUIPC5.JoyScan.csv FSUIPC5.ini HidScanner.log

Sorry, didn't realise there was a later version than the one on http://www.schiratti.com/dowson.html. Anyway, tracked down the latest version, and here are the 3 files... FSUIPC5.log FSUIPC5.ini FSUIPC5.JoyScan.csv

Hi Thomas I'm already using v103e, so files are as earlier. David

I have FSUIPC5 version 5.103 installed in P3Dv4. I also have a Saitek X52 Pro joystick. Everything worked well until... This afternoon, I tried using both the Saitek joystick and a gamepad (wanted to configure ChasePlane). I've since gone back to using just the joystick, but since then, when P3Dv4 starts, I get a message that Prepar3D.exe has stopped working. If I don't plug in the joystick, P3Dv4 starts okay, if I comment out FSUIPC5 in the dll.xml, again P3Dv4 starts okay. I've tried deleting the modules directory, and reinstalling FSUIPC, still the same problem, can't now run FSUIPC and the Saitek joystick together. I'm attaching the log, ini and joyscan csv files. FSUIPC5.log FSUIPC5.ini FSUIPC5.JoyScan.csv