StewCal

Interestingly, last night, I changed the eyeadaptation from 1 to 0 and it fixed it for me. Did it both non-VR and VR sections. It still does it a tiny bit but not even close to before. Maybe they fixed the switch....

Sometimes with TrackIr I can't even see the runway when landing....Just a big white band....

Thank you so much for the reply! Just purchased the program this morning and haven't had the time to do a deep dive. I'll give your suggestion a try. Looking forward to exploring more as time permits... Steve

New to Axis and Ohs. Trying to assign an axis to the PMDG 737 for MSFS2020. My joystick axis works fine in AandO but in the PMDG737 theres a conflict with the reversers. Is there a way to assign a throttle axis with no reverser zone like in FSUIPC? If not is there another workaround? I also have the MFD crosswing rudder pedals. They show up fine in A and O but not translating to MSFS2020. Any suggestions? Haven't had too much time to fool around with it yet. Thanks 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.