FsPassengers Forums
unfair crashes - Printable Version

+- FsPassengers Forums (http://www.fspassengers.com/forum)
+-- Forum: FsPassengers (http://www.fspassengers.com/forum/forumdisplay.php?fid=3)
+--- Forum: FsPassengers Support (http://www.fspassengers.com/forum/forumdisplay.php?fid=5)
+--- Thread: unfair crashes (/showthread.php?tid=6130)



unfair crashes - 09El_Boissevain - 30-03-2006

Hello to all,

When I was really far in my company, I made the biggest BS crash ever!! What happened was, I was taxiing to the runway, a/c full of passengers, then
suddenly my plane sank through the ground (on taxiway!!!!) and crashed!!!! That is TOTAL BS!!!!! Now is there a program I can get to get rid of this
unfair crash and unfair drop in reputation??!! Thank you.

Captain El wow


Re: unfair crashes - Dutch64 - 30-03-2006

Hi, just read this FAQ http://www.fspassengers.com/?action=faq&question=40 and after that disable fs and fsp crash detection. I hope it is what you
meant, maybe you want to remove the last crash from your database? For that there is a program called covoxerSmile You will find him on the forum here Wink




Re: unfair crashes - SaVas - 30-03-2006

Unfortunately there are a number of circumstances that cause this and there is no root fix to eliminate them all.

Chances are there is an issue with eithe the contact points of the aircraft, something wrong with the runway placement and ground
texture levels, or scenery refresh rates causing initial blurries (easily avoidable in most cases by staying in one view - either 2D panel or
VC) that then render the textures causing fluctuations in elevations by a few feet. It could be because add-on scenery is conflicting with
ground elevation, etc.

My best advice, is to NOT have all flights recorded because of these anomalies that are not the fault of FSP




Re: unfair crashes - poden - 30-03-2006

For your current company, the only way to get it fixed is to try and get John (Coxover) or Dan to take your database and remove the flight. You might
also see if John can set the "autorecord" to off. I don't know if he has done this before.


Re: unfair crashes - 09El_Boissevain - 30-03-2006

How do I do that? Is that a program or do I send it to the creators of FsPassengers and let them do it?


Re: unfair crashes - runibl - 30-03-2006

Send a message to Covoxer, and ask if he can help you.

He helped me set the autorecord to off once.




Re: unfair crashes - poden - 30-03-2006

I think the FAQ could use a good strong warning about the problems associated with using autorecord; I don't see anything in there about it.


Re: unfair crashes - ste9889 - 30-03-2006

talking of unfair crashes, i was making a perfect app into EDDF after a short hopp from EGLL in a bA 757 i had a random engine
flameout, and i literally crashed and burned lol


Re: unfair crashes - olseric - 31-03-2006

Savas is 100% right.

What I usually find as the culprit is when I use an aircraft that does not use the default "three footprint" gear configuration. Project
Opensky planes are notorious for having "real-feel" gear. It's great stuff, but it doesn't follow the terrain like the default tricycles do.

Out of curiosity, what aircraft were you using and by whom?




Re: unfair crashes - 09El_Boissevain - 31-03-2006

I used the Mooney Bravo (default) with a pilot named John Peterson at Deventer Airport; Teuge (EHTE). I seperated that airport from NL2000 and tried
to make that airport an individual on my FS, but on the RW I sank and crashed.

BTW, what is Covoxer's e-mail or whatever to cobtact him?

Thanx



Post Edited ( 04-03-06 17:34 )


Re: unfair crashes - Drew - 31-03-2006

http://www.fspassengers.com/forum/profile.php?f=2&id=1888




Re: unfair crashes - 09El_Boissevain - 03-04-2006

Ok, I sent a message to Covoxer. What do I need to do in order for him to get my company fixed?


Re: unfair crashes - 09El_Boissevain - 05-04-2006

Runibl, how long did you have to wait for Covoxer to reply? It's been 2 days and no reply yet... Huh
I really need this done quick because I cannot use the pilot unless it is fixed first