StewCal

I have the Pap 3 and both efis units. Works great with the pmdg 737 800 but not with the recently released 900. Anybody figure that out yet? Have the latest simapp pro and firmware. Steve

Went back to ver. 5.4.2 and it works. Then tried 5.5.3 again and no joy. This is for 2020.

I have one but I just can not get used to it. Keep going back to TrackIR. Part of my problem may be that both devices do not play well together on the same machine.

Which version of TrackIR software do you use?

Well, it seems that the latest version of the TrackIR software that is required for MSFS2024, doesn't ( at least for me) work with 2020. I have reverted back to TrackIR version 5.4.2 and it is now working in MSFS 2020. This is so frustrating. Steve G.

No. I've tried all of that.

Not sure how this is possible but it seems that once I got TrackIR working in MSFS 2024, it stopped working in MSFS 2020. Has anybody else had this issue? Very frustrating. I've tried everything. Just have the left had light on on the unit. Help!! Steve G

Solved my issue by removing Saitek driver for my pedals. Just using generic drivers. Steve G.

All seems well! I think I may have gotten past my USB crashes. Thanks for all the help. Fingers crossed. Steve

Interestingly enough, they work in the sim although they don't show up in Devices and Printers. I'll have to fool around a bit. Thanks! STeve

I've managed to delete the Saitek drivers for my Combat pedals. However when I plugged them in again they show up under devices and printers but don't respond when I select game controller settings. Any thoughts? Steve

Thanks Rich! I might pick one up.... Steve

My particular issue is specific to Prepar3d 3.0 and 3.1. In fact, I stopped using Prepar3d all together (I could rarely complete a flight) and went back to FSX (I had already uninstalled Prepar3d 2.5 and was too lazy to reinstall it). I've flown about 100 hours in FSX without having the USB crash. Something changed between 2.5 and 3.0. LM even said in the release notes for 3.0 that they changed the way the sim interfaces with controllers. I have an active thread on the LM forum about the crash. The LM moderator suggested I unplug my pedals to see if I could complete a flight and guess what? I could. I'll have to try uninstalling the Saitek software and drivers again and see if I can get the pedals to work without the drivers. From what has been said here it is possible to do so...Thanks! Steve G. By the way, I'm still using Windows 7 along with PFC yoke and Throttle Quad, as well as TrackIR (Saitek Combat Pedals)

What is Spad?

I've been having trouble with Prepar3d since version 3.0. It seems that something is causing a USB crash. There has been some discussion about Saitek products as a possible cause so I've updated my Saitek drivers to the latest available but am still having the USB crash. I have been able to complete flights with the pedals unplugged which deepens my suspicion that my pedals are the culprit. My question is whether or not it is possible to use the Saitek Combat rudder pedals without installing any Saitek drivers or software. I tried uninstalling everything Saitek and install the generic USB and HID drivers but the pedals did not seem to recognized. Any Ideas? Flying without rudder pedals is a challenge to say the least. Steve Giblin

Does your mouse start to beep if you move it around?. If so the computer's usb system has crashed. I have had this issue since version 3.0. I believe it is an issue that was introduced when LM "rewrote the way contollers are handled within the sim." Wondering if you have any Saitek contollers? (I have the combat pedals). There is a long thread on the LM forum discussing issues with the Saitek trim wheel. I suspect the problem goes deeper. I can not complete a flight anymore without the USB crash. Have not found a solution and don't know if LM has even acknowledged a problem. I'm thinking of going back to version 2.5. Quite a few people are having this problem but it does not seem to be the majority so I'm wondering if it has anything to do with Saitek. I've tried all of the new beta driver etc. to no avial. Sooo frustrating!

Problem is back. I'm back to thinking that Prepar3d is the culprit. Started with version 3.0.

This does sound logical since the usb board in my Precision Flight Controls yoke just failed totally. I suspect that it may have been causing the issue prior to its total failure. Time will tell. Just installed the replacement.

I too have had this issue since version 3.0 even following Kyle's suggestion above. Mouse stutter, beeps, freeze (or at least no control inputs work and hard restart required). There's a huge thread on the Prepar3d forum as how this relates to the Saitek trim wheel. I do not have the trim wheel but do have Saitek pedals. I have updated to the latest Saitek beta drivers but have not been around to do much flying since. We'll see.

Thank you Jim, I appreciate you taking the time to help. I downloaded the CTD guide and will be doing some exploring when I have the time. Thanks again! Merry Christmas Steve

I've had a CTD Fatal Error just before the approach phase on 2 consecutive flights. Wondering if it has something to do with add-on airports loading. Using Prepar3d 3.1 but it has also happened with 3.0.

I tried the plug in after start method and that seemed to work at least for the short flight I completed. I'm hoping this all goes away with Prepar3d 3.1. Fingers crossed. I feel your pain. I can't count the times over the years that I found myself banging my head against the wall due to one issue or another involving flight simulator. The encouraging part though is that there are a lot of very helpful people in the forums and most of the problems I experienced were eventually overcome. That being said, are you using Windows 10? I had to go back to 7 due to USB issues. There is one method that you can still try. It works with windows 8 and 10 and involves a relatively simple registry edit that truly shuts off USB power management. Give it a try. Check out the link below... https://support.microsoft.com/en-us/kb/2830154

I'll try the boot then plug in method to see if I can complete a flight. I did find a new beta driver for my combat pedals but still had the problem. I did read somewhere though that if you disconnect and reconnect it can reinstall the old driver. I reverted back to Windows 7....I suspect there is something going on with Prepar3d 3.0.

Had this problem again last night on a flight from IAH to DEN. Happened when puling into the gate without GSX. Very annoying. Never happened before Prepar3d 3.0..

Did that. Did not work for me. Did not try the registry edit method though...