[old thread ]FFX 737-200 Tail Strike Bug - HELP NEEDED!

[AltairZQ]

SWAFO wrote:
I believe you can disable the crash penalty altogether via the more_option.cfg file... this should fix the tail strike problem.

I've seen you recommend disabling penalties a dozen times (and a couple of times to me too). Please understand that we bought FsP to
be penalized, this is the reason for FsP to exist, so disabling penalties is the least desired solution for most of us.

[DanSteph]

AltairZQ wrote:
you recommend disabling penalties a dozen times (and a couple of times to me too). Please understand that we bought FsP to
be penalized, this is the reason for FsP to exist, so disabling penalties is the least desired solution for most of us.

A "disable crash" as said brad would not resolve anything in this case and even in the
737-200 case the disable will not be needed with next version.

90% aircraft tail strike at less than 11° as FSP is set, anyway it's not possible to maintain a database
of all the aircraft in the world and to detect wich one exactly you use...
so the only way for special aircraft in this case is to disable penalty...

disabling penalty are only and mostly made for special aircraft that are uncommon
or for people that want to fly uncomon.

So I agree it's not a common solution but it might be the only one for special aircraft
and special case...

Dan

[MarkMcCoy]

Thanks Dan, I really appreciate your attention to the FsP community. This program, while young, has certainly added the increased commercial flight
realism so many of us were looking for. Thank you. I'd like to end this thread (before it brachnes too far off-topic) by asking you when you think
this update will take place? Myself and many of my friends and contacts are extremely curious.

Thanks again, Dan and I look forward to your reply! :D

[DanSteph]

the new update is already functionnal but not on a "stable state" (mean some feature are half
done or on the way) so I cannot assure to anyone that would test it that there would not be any other
problem or missing stuff. (on this version for example you may miss the "win/fail" splash screen
while I'm not fully done with the modif of path)

People that would still want to test it would have to be very carrefull and backup their database
and get ready to get some bug... a beta tester work in brief.

Once the "path" job will be done this beta will be more stable but still would be only
released by people fully aware about what is a beta test.

About delay... it depend on what's planned and the work still to do... I'm now in touch with PMDG
so I cannot promise anything but I hope 2 weeks. anyway this would not be the definitive update
as I'll not stop working on FsP during the next month.

Dan

[Swag]

Perhaps it's worth checking out the flight dynamics file made by Charles Fox, which you can find together with
a very nice panel at http://www.tinmouse.org.

[SWAFO]

AltairZQ wrote:

SWAFO wrote:
I believe you can disable the crash penalty altogether via the more_option.cfg file... this should fix the tail strike problem.

I've seen you recommend disabling penalties a dozen times (and a couple of times to me too). Please understand that we bought FsP to
be penalized, this is the reason for FsP to exist, so disabling penalties is the least desired solution for most of us.

I always recommend disabling the crash penalties, since I find FS has a few too many issues to fly around with the crash penalties on.
What other penalties have I recommended disabling? Perhaps the light penalty because my company uses the LL's below FL180, not
FL100. Anytime I recommend disabling, it's for realism, not to sacrifice it.

[AltairZQ]

SWAFO wrote:

AltairZQ wrote:

SWAFO wrote:
I believe you can disable the crash penalty altogether via the more_option.cfg file... this should fix the tail strike problem.

I've seen you recommend disabling penalties a dozen times (and a couple of times to me too). Please understand that we bought FsP to
be penalized, this is the reason for FsP to exist, so disabling penalties is the least desired solution for most of us.

I always recommend disabling the crash penalties, since I find FS has a few too many issues to fly around with the crash penalties on.
What other penalties have I recommended disabling? Perhaps the light penalty because my company uses the LL's below FL180, not
FL100. Anytime I recommend disabling, it's for realism, not to sacrifice it.

Yeah right.

[Ryanamur]

AltairZQ wrote:

SWAFO wrote:

AltairZQ wrote:

SWAFO wrote:
I believe you can disable the crash penalty altogether via the more_option.cfg file... this should fix the tail strike problem.

I've seen you recommend disabling penalties a dozen times (and a couple of times to me too). Please understand that we bought FsP to
be penalized, this is the reason for FsP to exist, so disabling penalties is the least desired solution for most of us.

I always recommend disabling the crash penalties, since I find FS has a few too many issues to fly around with the crash penalties on.
What other penalties have I recommended disabling? Perhaps the light penalty because my company uses the LL's below FL180, not
FL100. Anytime I recommend disabling, it's for realism, not to sacrifice it.

Yeah right.

As you probably noticed, Brad (SWAFO) was banned from the forum because he was claiming to be a SWA pilot when he was not.
Just dismiss any claims he made about real wolrd operations.

Cheers.

Phil



Post Edited ( 01-06-06 14:21 )

[pagir]

...and this "zombie thread" is four months old!!!

Pagir

[CODY614]

Dunno.....Only thing I would venture to say is.......
Check weight and balance....
Check trim....
Flaps....
If you cant' find something your doing wrong...Then look to the airplane.
Could be something in the "points"..ie..where the plane pivots in the sim....you said you tried different config files?
Are they still his?....Maybe drop him a line and explain the situation...
Jeff



Post Edited ( 01-06-06 17:32 )

[AltairZQ]

I know, sorry, just wanted my little revenge.

[flameout]

I would change the flight dynamic[ 737-200.air ] file. Replace it with one you know is not buggy.

Regards

[pagir]

Please... this is an old post, and the issue has been fixed with the september 2005 update...

Pagir