Help "Horrible Flight"..... error

[rchwallace]

Hi there,

I finished a flight this afternoon which was KSEA to KPHX. I have recently bought the KPHX Simflyers scenery so wanted to check it out.
My question is really going to go to how the program has given me this error. I would assume that it is basing its calculations on the
default scenery location and not the one that I am using............ but there could be more. Here is what happened:

I landed on runway 26 in the TDZ at roughly 1700ft. The program has logged the landing as "kiss". After exiting I overshot the taxyway
that FS2004 ATC wanted me to take so when I was turning the AC to get onto the right taxiway I put the nose whell slightly into the dirt.
After landing I noticed a much louder sound comming from the gear.... etc etc (for this reason I think the program has logged the landing
at fault and not my taxying .....) I got a "HORRIBLE" for the flight..... I also changed my FSREALTIME time half way through the flight which
obviously messed with my arrival time (-200) I can live with that but...............

I quote "At arrival airport you rolled at 140kt beyond the edge of the runway without any emergency. The landing gear sustained some
damage and our company has received a fine of $1,540 (-700)" This I believe is an error created by the default scenery and my using
simflyers KPHX.... but I am not sure. I have not had any trouble with any other of my non-default sceneries and I generally fly around to all
non default sceneries. (The above is a direct quote and is a little bit confusing..... 140ft I am assuming.....) I definitely did not leave the
runway accept to a taxiway.

Any theories...... I will have to live with it on my record I recon as I am using the auto record feature.

[mwhpilot99]

i have had the same problem with all my simflyers scenery. i have phx,iah,dfw and atl. this is the only scenery i have had this problem
with. I wonder if we can get someone to look into this problem and post a fix.

[DanSteph]

it seem for me that the author of this scenary forgot the "surface" declaration, IE:
internally you're rolling on grass when visually you see asphalt or such.

This can be resolved by AFCAD editing...

Dan

[JayKae]

I have all the simflyers sceneries and I never have any dramas, maybe it is as Dan says and guys have a look at simflyers.net under AI
traffic and get the new AFCADS

[rchwallace]

Thanks guys I will try to update the AFCAD files. Is there any chance I can remove the report from my file in the game ........... not that it is a
big deal but I have had 13 perfect flights and this one...........

Anyhoo, thanks again.

Ron

[nem]

rchwallace wrote:
Is there any chance I can remove the report from my file in the game

See http://www.fspassengers.com/forum/showth...p?tid=4798

I think with auto record on you're bound to have a not perfect flight recorded sooner or later anyway.

[jboweruk]

Tell me about it, I had a whole evening of it yesterday, as a distinct lack of pilot shows.

[rchwallace]

Just for reference.... I have downloaded the latest AFCAD for the Simflyers which I am using.... I bought quite a few. I flew Dubai to Rome
yesterday and had the same thing happen in Rome LIRF with the landing. I am going to have to use AFCAD2 and see if there is any way
in which I can edit the file to work properly.

If anyone knows how to do this that would be great but I am sure in time I will figure it out.

Regards

[FPEMiller]

Ok, has anyone been able to fix this? I just spent the whole evening changing various files (AFCAD, Scenery .CFG, etc) changing elevations, Exclude, and Flatten commands in an attempt to get FSP to recognize KPHX's runways... with not luck. Yes I know that I can disable "off runway" penalty as Dan suggested, but I'm trying to fix the problem with Simflyer's KPHX. I don't know what else to try. Ironically, their KLAS scenery appears to be working fine with FSP.

The only thing is that I might have been doing the flatten command wrong. Which order should the coordinates be listed; clockwise, or counter-clockwise? I thought I remember reading somewhere that the coordinate points had to be entered in a specific order.

Regards
MK



Post Edited ( 09-07-05 06:47 )

[SWAFO]

Also, in the more_option.cfg file there is an option to disable the "roll outside landing strip" penalty. I've heard that that usually fixes the
issue.

[DanSteph]

FPEMiller wrote:
The only thing is that I might have been doing the flatten command wrong. Which order should the coordinates be listed; clockwise, or
counter-clockwise? I thought I remember reading somewhere that the coordinate points had to be entered in a specific order.
Regards
MK

Sorry I can't help you on this I'm not a scenary specialist perhaps someone can't help you on this ?
You may try to ask the question on AVSIM forum there is a lot of scenary specialist there
http://www.avsim.com

What I can tell anyways is the FsP Part: FsP don't recognize itself the surface, he ask Fs9
with a FS9 function what's surface is detected by Fs9.

Now what I can do but only for the next release is to add a "debug" display that will show you
on top of screen wich surface is detected by FS9 under your aircraft, this will not solve your problem
but it might help. This debug display would be enabled by a parameter in "more_option.cfg"

What I can do right now is to send you by mail a "debug" version of FsPassengers DLL
that will tell you that info, so you'll be able to report to scenary author that their surface
is wrong at nn location. If you want that send me a mail and please recall what is your mail about.

Hope it help ?

Dan

[FPEMiller]

Thanks for the offer Dan... Let me do some more digging and take a closer look at their xml code and see how they have the runway designed/specified.
I was thinking that it was an elevation issue, not thinking about how they had the runway surface defined.

Regards
MK

[DanSteph]

let me know if you succeed in this, if you can't sort it out my "special DLL" can help you find
what surface is declared in their scenery so you can see exactly where is the problem.

Just write me a mail if you need it, the DLL is ready I'v
made the change already for the next update...

Dan