Search the Community

HI All, Apologies if Im beginning what was an aged topic - I had a quick look around to see if anyone had posted a similar issue before but couldnt see anything. I have recently gained a Saitek Proflight Yoke with throttle quad. I plug the quad into the main body of the yoke. I had used the yoke on a win7 note book with great reliable results and now I have a new desktop PC the saitek is unreliable. I can set up and be flying then the yoke control drops out....I have no control over the plane. So I either have to unplug and plug in again to bring back the control or completely shut down FS9. Often when I have had to do this I lose some if not all of my assignments. I thought it was a power issue so was looking for a 5V adaptor (found one but not the right pin). It is starting to become a pain in the a :ph34r:s now so can anyone offer me advice? Many thanks N :blink:

So my Flight Sim X has started crashing to desktop again. With that and my joystick losing calibration flying is no longer enjoyable. I am on windows 8 and have had frequent CTDs before. I completely eliminated the problem by installing the vista version of UIAutomationCore.dll inside C:/FSX. Well now it is still crashing. I looked in the Windows event viewer and found these application logs and I would appreciate some expertise to understand them: Yesterday: Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: MSVCR80.dll, version: 8.0.50727.6910, time stamp: 0x4fee68f0 Exception code: 0xc000000d Fault offset: 0x00008aa0 Faulting process id: 0x1dd8 Faulting application start time: 0x01ceaf0c64436c72 Faulting application path: C:\FSX\fsx.exe Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6910_none_d089c358442de345\MSVCR80.dll Report Id: 3195ceed-1b09-11e3-bee4-50e549ce63df Faulting package full name: Faulting package-relative application ID: Today 1: Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: USER32.dll, version: 6.2.9200.16420, time stamp: 0x505a971d Exception code: 0xc0000005 Fault offset: 0x00019217 Faulting process id: 0x1a14 Faulting application start time: 0x01ceaf371982e48a Faulting application path: C:\FSX\fsx.exe Faulting module path: C:\Windows\SYSTEM32\USER32.dll Report Id: 1dbe9481-1bf5-11e3-bee4-50e549ce63df Faulting package full name: Faulting package-relative application ID: Today 2: Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x7770bda1 Faulting process id: 0x2478 Faulting application start time: 0x01ceb0325b901d08 Faulting application path: C:\FSX\fsx.exe Faulting module path: unknown Report Id: 69dbb72d-1c2a-11e3-bee4-50e549ce63df Faulting package full name: Faulting package-relative application ID: Today 3: Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x7770bda1 Faulting process id: 0x1604 Faulting application start time: 0x01ceb0375cb550b3 Faulting application path: C:\FSX\fsx.exe Faulting module path: unknown Report Id: df71cdb8-1c2d-11e3-bee4-50e549ce63df Faulting package full name: Faulting package-relative application ID: Thank you to anyone who has a look at these four logs and can assist me in diagnosing and then eliminating the problem. I really would like to end all my flights on the runway rather than a crash during the descent.

hello guys I am new to the forum and the ngx and I was just needed some clarification please. During tutorial 2 I was testing the cargo fire system, on the tutorial it states that after I push the master fire warn system to cancel the bell, The FWD, AFT, DETECTOR FAULT, EXTINGUISHER, and DISCH lights all stay illuminated. however I get the AFT, FWD, DISCH and green EXTINGUISHER lights but not the DETECTOR FAULT LIGHT in the right corner above the DISCH. I was just wondering if I have missed something or if that is normal. sorry if this has already been asked or is a stupid question, thank you.

Hi, I suspect I might have found an error in the Fire protection FAULT light logic. According to the FCOM, with the fire detection loop switches in "normal", failure of both detection loops for an engine causes the FAULT light to illuminate. (No master caution) This means, suppose loops A and B for engine 1 fail -> FAULT light illuminates. In the NGX though, I need to fail all 4 loops (e.g. Loop A and B for engines 1 AND 2) in the FMC/failures menu, for the fault light to illuminate. Please correct me if I missed something. Greetz, Bob

Hi I'd appreciate any ideas on what might be the fault with my GTX285 and if there is anything I can do. Please "don't get your card wet is not going to be helpful LOL!). It's a long story! But my gaming PC ended up getting pelted by rain when the wind blew a window wide open. Drops of water dripped onto the circuit board of my GTX 285 inside the PC. The PC was on when is git wet, when I discovered it it had shut down. The PC appears to be working OK with another graphics card. The part of the circuit board that got wet is right above the two 6-pin power receptacles (at the end of the card). Consider the orientation of the graphics card when installed with the back circuit board of the card facing upward; there are two 6-pin power - lets call #2 the one closest to the end and #1 beside it. I'm left with the following behaviour wihen I install my GTX 285 (and when I use a different PSU): 1) With no 6-pin power connectors attached when switched on nothing happens. 2) With 6-pin #1 only connected when the PC is switched on it sounds as if it's beginning the boot sequence but the monitor receives a blank signal (on either DVI output), graphics card fan is spinning. 3) With 6-pin #2 only connected when the PC is switched on nothing happens. 4) With both 6-pins attached nothing happens. :(((.