04-08-2005, 05:50 PM
Hello,
I'm glad that the list of "full of bug" end only with three item on wich two doesn't come from FsP...
there are some of course I'll not discuss this point I'm aware on most of them and working
on an upgrade. but considering the amount of work and code line (50'400) they are rare believe me.
Emergency:
if you get a failure in flight wich is not detected by FsP it must come from the aircraft himself,
be sure to know the aircraft you fly and to disable any failure.
If the author have set some gauge that give failure There is no way in the world to detect that.
The crash in flight:
FsP doesn't set any crash value during flight, it only FORCE the "crash detect" value of Fs2004
IF you have disabled it ONLY. (you can disable that in more_option.cfg file)
so two case:
You just started a FsP flight, your aircraft was wrongly positionned or there was a scenery glitch
and your Fs2004 crash detection disabled, As soon as FsP force the crash detection Fs2004 have
detected a crash because of scenery of whatewer.
not a bug usually you must have Fs2004 crash detection enabled to avoid that.
(there is no consistency to run an addon as FSP with Fs2004 crash detection disabled howewer)
If It happened in a midle of taxiing: I see no way for FsP to suddenly set the crash flag, in this case might
be an AFCAD problem (scenary problem) invisible house or invisible difference in height.
the inconsistency beetween crash report and death is due because it's a "bug crash" and not a normal crash...
induced bug in brief.
The x16 howewer is a true FsP bug, I'm working on this... to be informed about how the upgrade goes
please have a look at this post in "support forum":
http://www.fspassengers.com/forum/showth...p?tid=4874
Hope it explain ?
Dan
Post Edited ( 08-04-05 19:06 )
I'm glad that the list of "full of bug" end only with three item on wich two doesn't come from FsP...

there are some of course I'll not discuss this point I'm aware on most of them and working
on an upgrade. but considering the amount of work and code line (50'400) they are rare believe me.
Emergency:
if you get a failure in flight wich is not detected by FsP it must come from the aircraft himself,
be sure to know the aircraft you fly and to disable any failure.
If the author have set some gauge that give failure There is no way in the world to detect that.
The crash in flight:
FsP doesn't set any crash value during flight, it only FORCE the "crash detect" value of Fs2004
IF you have disabled it ONLY. (you can disable that in more_option.cfg file)
so two case:
You just started a FsP flight, your aircraft was wrongly positionned or there was a scenery glitch
and your Fs2004 crash detection disabled, As soon as FsP force the crash detection Fs2004 have
detected a crash because of scenery of whatewer.
not a bug usually you must have Fs2004 crash detection enabled to avoid that.
(there is no consistency to run an addon as FSP with Fs2004 crash detection disabled howewer)
If It happened in a midle of taxiing: I see no way for FsP to suddenly set the crash flag, in this case might
be an AFCAD problem (scenary problem) invisible house or invisible difference in height.
the inconsistency beetween crash report and death is due because it's a "bug crash" and not a normal crash...
induced bug in brief.
The x16 howewer is a true FsP bug, I'm working on this... to be informed about how the upgrade goes
please have a look at this post in "support forum":
http://www.fspassengers.com/forum/showth...p?tid=4874
Hope it explain ?
Dan
Post Edited ( 08-04-05 19:06 )