pilotgod
Trainee
Chicks dig us, and guys think we're cool.
Posts: 47
|
Post by pilotgod on Sept 22, 2009 17:07:15 GMT -5
Title sums it up. I got another "Hero" flight for something not going wrong. When I consulted the fault listings I see "documented as FSX but does not fail". OK, that makes sense, but my install is only on FS9. Is this supposed to do anything in FS9 or even appear on an FS9 install?
|
|
|
|
Post by Dutch Owen on Sept 22, 2009 19:45:01 GMT -5
It's nice to be a hero isn't it?  Looking at the code, something triggered a "Partial Panel Avionics" failure signal coming from FS9 that resulted in the 203. That's the only possibility. My note in faultcodes.txt refers to the documentation for FSUIPC4, which says that the partial panel avionics failure can be triggered by FSCaptain in FSX ... but it doesn't actually seem to fail when FSCaptain tries to trigger it. Our problem here is the other direction -- a failure sensed by FSCaptain in the airplane. That could come from either version. Since I did most of my testing in FSX and never saw a 203 it must be a glitch in FS9. Since it was a false signal (your avionics were working fine) I'm going to disable sensing for 203 in FS9. I'm really beginning to suspect some of the FS9 failure signals are lit up for reasons not related to actual failure. Dutch |
|
pilotgod
Trainee
Chicks dig us, and guys think we're cool.
Posts: 47
|
Post by pilotgod on Sept 23, 2009 5:56:51 GMT -5
It is starting to sound like FS9's failure signals do like to false report a lot. I would run this on FSX, but as I haven't yet upgraded my memory and vid card FSX runs just above minimal acceptance and I didn't want to deal with something causing problems and that spilling over to FSCaptain, so I'm running it on FS9 since that program is extremely stable on my system.
|
|
