Jump to content


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

47 Neutral

About rcpistonhead

  • Rank
  • Birthday May 21

Profile Information

  • Gender
  • Location
  • Interests
    Enduro, flying, camping, boating, rc cars

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines
  1. Here is the “long version” of the fix should the “short fix” not work for somebody: f this does not work: this is the long version which was the first way I found to get itworking again:- Plugin the X52- Go to device manager and delete the X52 and USB devices with an ! sign (warning/notinstalled correctly)- Restart your PC- Unplug your X52- Run the installer (with the latest beta drivers for W10)- When the screen pops up with the instruction to plugin your X52 -> plug it in...- Just let the installer run (with the NEXT button greyed out) and go to device manager- Right click on the X52 device and select update driver- Choose "search on my PC" and then "let me pick" (2nd option) -> you get a list of 2compatible devices- Now select the 1st option "USB device" or something similar NB: NOT the 2nd one withUSB X52 in the name!!!- Directly after this W10 detects your X52 and you can select NEXT in the installer- Install will continue and finish correctlyThe right selection of the USB device (AND NOT X52..) is important. If you select the X52line you get a critical error and it stops..Also I would recommend disabling FAST START. It seems that Windows starts too fast forUSB devices to report themselves and to be enabled. You can find this option here:Energy management -> behaviour of on/off buttons -> Fast start is greyed out, but if youselect "choose options which are not available right now" you can disable it.
  2. Update: FIXED! I found a similar thread about the X52 doing the same thing. This is the process that fixed it for me (substitute x52 for pro flight throttle quadrant) Try this short version first:- Connect X52- Open device manager -> look for an USB input device with an !- Right click: update driver- Choose "search on my PC" and then "let me pick" (2nd option) -> you get a list of 2compatible devices- Now select the 1st option "USB input device" or something similar NB: NOT the onewith USB X52 in the name!!!- Device should work now...
  3. Also, the quadrant isn’t listed under human interface devices. It is listed under other devices. When I go to it’s properties it says no drivers are installed for this device. I have tried re installing the saitek driver for it but when I get to the screen that says to plug in the quadrant it won’t recognize it to proceed.
  4. No change unfortunately. It still shows as unspecified. I also tried plugging it into different USB ports, no change.
  5. I just plugged it into my laptop and it set up and is working properly. Listed as a working device in control panel. I’m totally confused why it isn’t working on my pc?
  6. Needing some help with saitek throttle quadrant. I have a Cessna yoke with quadrant and a second quadrant (usb). I have been using both for years without a problem. Suddenly now my second quadrant (usb) will not work. Fsx won’t recognize it. In windows control panel it shows up under “unspecified” and says the drivers need to be reinstalled. I tried reinstalling the saitek driver for it but no change. Did the quadrant die or something else going on? All of my other saitek equipment works fine (6x fip’s, switch panel, radio panel, warning light panel, pedals, yoke with quadrant, auto pilot panel - all working fine).
  7. I've been out of the sim for over a year and just getting back in. In the Ops Center it tells me that my NGX, 747V3 and 777 need updated. When I click on "Install Update" for the products, a black window with some text code pops up for a couple seconds and then that's it. So then I run the sim (fsx) thinking they were updated but nothing was changed. So I exit fsx and run the Ops Center again and it gives me the same notifications that my products need updated. What gives? I thought this op center thing was supposed to be convenient? How do I update? Thanks
  8. I would love to see some dedication to GA aircraft by PMDG.
  9. This fixed the problem for me. I was running in compatibility mode for windows 8 (i am running windows 10). Works like it should now. THANK YOU!!!
  10. I installed the CJ2 correctly without issue (antivirus off during installation, no errors). When I load the CJ2 in FSX the frame rate drops below 1 and basically freezes the sim. I have to exit the sim completely and re start a new flight. All other aircraft work great, only the CJ2 causing problems. Specs are Windows 10 Pro, i7 6700 4Ghz, NVIDIA GTX 1070, 16gb ram. Any help would be great. Thanks.
  11. Hello, I just installed the mod and everything loads and looks correct but now the frame rate is about 1 fpm. Any ideas? I had this problem when I first installed the CJ2 and the solution was deleting the carenavigraph.dll from the main fsx folder. Thanks,
  12. Thanks for your quick reply, Jim. I tried as you suggested and it did not help, it actually made the fatal error occur much faster. This time it occurred immediately after loading the A2A C172. I am pretty sure at this point it is something to do with that aircraft only since no others seem to be effected. Particularly one livery even seems to be more problematic than others. I am going to try uninstalling and reinstalling the A2A Cessna and go from there. Otherwise, any suggestions? Thanks!
  13. Hello, I've been battling a fatal error in FSX caused by a panels.dll module failure. I have googled and tried many things before resorting to posting a new topic but I'm stumped and could really use some help. The CTD seems to only happen with the A2A C172 but here are the details from my event view. Any help would be great, Thanks! Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: panels.dll, version: 10.0.61637.0, time stamp: 0x46fadb59 Exception code: 0xc0000005 Fault offset: 0x000320c0 Faulting process id: 0x232c Faulting application start time: 0x01d25c8a4525c083 Faulting application path: E:\FSX\fsx.exe Faulting module path: E:\FSX\panels.dll Report Id: 1f0001dd-c886-11e6-9668-e56af7577eda Faulting package full name: Faulting package-relative application ID:
  14. Anyway to accomplish this without using windowed mode??
  • Create New...