flight classified as cheated when client froze

[e.rossiter]

Hello, my flight has been classified as cheated due to time. However the flight was not cheated it was done at 8x like what it said I could do it at, at 38, 000 feet at 260 knots with autopilot controlling the navigation with a flight planned route. However apart 1/4 of the way into the flight the client froze I thought it would be ok so I continued, and it came back when I was landing.

What I request is that this flight be fixed to say I didn't cheat and I get my full 100% that the flight would have got, and my pay back.

Thanks.

[Konny]

Your flight got marked because the flight report showed that you actually only flew 1.9h (FS time, so the simulation rate doesn't matter). Nobody can do 4000nm in that time. Can you please send me the debug.out in your client directory? (konny@fsairlines.net)

[e.rossiter]

the what

[Konny]

The debug.out file, which is located in the directory you chose when installing the Client ( usually C:\Program files\FSAirlines ). If the Client froze it might be possible that it didn't record the flight time from then on, so if it froze at 1.9h (which could be about 1/4 of the way) that might be the reason. But I'll first have to check the debug.out file.

[e.rossiter]

It won't let me attach the file due to the extension.out isn't aloud so what is your email address and I will send it to you that way? Also I can send you the flight plan that I followed due to it was on GPS hold also.

[joefremont]

Can you send it in a zip file?

The system flags flights that look like they arrived at there destination too fast. Sometimes this is because of a slewing or other techiques to change the position of the aircraft, sometimes its just an bug with the system clock. The we usually just clear these situations and have the system recalcuate the hours.

[e.rossiter]

There it is. (REFER TO ATTACHED)

[Konny]

Ok, I deleted the cheat-flag and reset the flight hours to 9.1.
The Client didn't record the 7.2h which were flown while it was frozen and so the flight got marked. I'll try to detect this kind of freeze in the next release, meanwhile you could try to awake the Client (if it's frozen) during flight by descending 1000 or 2000ft. I'ld really like to know if that helps.

[e.rossiter]

ok thank you.