Crash on Spawn - ALOT

[stonelance 136]

Hmmm, this stinks.  Normally that can happen because some of the aircraft were not set up very well and they drop a small distance to the ground when they are spawned.  I've had it happen a couple times in the warbirds, but not as much as you are describing.  If you spawn in the air and try to land in those spots does the aircraft seem to float or do other weird things in those areas?

[EzRyder 35]

Hmmm, this stinks. Normally that can happen because some of the aircraft were not set up very well and they drop a small distance to the ground when they are spawned.

 

If you spawn in the air and try to land in those spots does the aircraft seem to float or do other weird things in those areas?

Exactly what it does - I've seen it in FSX but only on 3rd party Aircraft (reducing the 'Static_Hieght' in the cfg sometimes fixed it)

 

No it flies fine if I spawn in flight - 'in those spots' is every location I've tried (at least a dozen or more in Alaska and maybe 6-7 in Hawaii)

 

'Hmmm, this stinks.' Not to bad I'm back to Airport Hopping and since I reload without 'moving' the aircraft it loads fine

 

Hopefully I'll get it sorted out Monday when I reinstall

[EzRyder 35]

After a Complete ReInstall the culprit seems to be the Alaskan Wilderness Pack.

 

No crashes until this was installed

 

After install I'm back to square one crashing anytime I move the Aircraft from the menu (Even in Hawaii)

 

Uninstall Alaska - no crashes

 

So it Looks like I'm stuck with it - I don't expect to get any tech support from Microsoft

 

Thank you all for the effort & suggestions

[Air1 136]

Very sorry to hear this. Still sounds like the computer itself or the video card? I just don't know anyone that has had this kind of problems. All and all it's normally a pretty trouble free installation.

[EzRyder 35]

TY Air1

 

I agree its likely a hardware/software issue at my end.

Also my PC has a 1.8GH processor not the 2GH required (everything else meets req)

So I can't expect ms to support it

 

I can play it so its not too bad, just takes an extra load to do aerocache hunts and jobs

And I can use freeflight without any problem at all 

[Moe 6]

Sounds like you have justified a new computer to me.

 

That's how I would spin it off my wife.

 

Just saying

 

Moe

[basys 4]

Hi Folks

 

AirWayMan -

My apologies for not responding earlier.

 

I've been away/offline since end of June,

so not seen these posts till today.

 

 

 

Once the sim considers that your aircraft has crashed,

you will lose ALL joystick & keyboard input control.

 

Also,

as per previous FS versions,

if your user's slider settings are set too high,

versus your PC's capabilities,

then FLIGHT will struggle with your joystick inputs

against attempting resolving scenery display.

e.g.

An unresolved mesh

may cause your aircraft to spawn at an elevation above

the finally resolved mesh elevation.

 

This will appear to be be more prevalent when operating in Alaska

as your system will be attempting to load/process a greater amount of data.

 

Lastly,

if some app or device is flooding your PC's USB inputs,

e.g. modem, audio, external drive, etc.

then that may be conflicting with / suppressing your joystick inputs.

 

 

 

However -

As you've stated the joystick was working ok previously,

then maybe an unrelated software, install or update, since that time,

is taking up previously unutilised PC resources,

i.e. it's tipped your PC beyond its capabilities.

 

 

 

From looking at your screenies above,

and your statement that these airplane crashes occur more prevalently with Alaska installed,

 

Do you have the Hawaiian Adventure Pack installed ?

 

 

 

Could you clarify please,

were these genuine Missions, (accessed via Map - Missions),

or as suspected, Jobs accessed from an airport's Job Board, (accessed via Map - Clicking on an Airport),

 

 

 

Your screenies appear to indicate the latter,

i.e.

you'd been attempting to fly a Job from an airport's Job Board.

 

Your fourth screenie

appears to show you've turned off the HUD,

which'd give additional indicator evidence.

 

Your second & fourth screenies

also appear to show that your aircraft

has been keeled over on its stbd wingtip

i.e.

It's being subjected to strong crosswinds

and blown/scraped across the terrain.

 

 

 

All Missions are initiated using

MS pre-selected weather conditions.

 

All Jobs are initiated using

the user's currently selected Free Flight weather conditions.

 

Just a guess

that if you look at Map - Free Flight - Flight Conditions

you'll possibly find that your user-selected weather settings

incorporate a strong wind component.

 

 

 

If so,

then selecting Clear Skies or Fair Weather

should allow you to launch these Jobs successfully.

 

Landing and completing is a different matter,

dependent on your capabilities. :lol:

 

 

 

As a final resort -

try clicking FLIGHT's main menu - Options

then clicking the Defaults button

on each of the 5 LH menu buttons.

Then clicking Accept.

 

 

 

 

HTH

ATB

Paul

[EzRyder 35]

Hello basys    And Thank You for your help 

 

"Do you have the Hawaiian Adventure Pack installed ?"

 

 

Yes the Hawaiian Pack is Installed

 

"were these genuine Missions"

 

 

No, you are correct they are Jobs but missions do it also if they start on the ground

 

"Just a guess
 that if you look at Map - Free Flight - Flight Conditions
 you'll possibly find that your user-selected weather settings
 incorporate a strong wind component."

 

 

Weather is/was set to Fair Weather - It 'Falls Over' like that as I capture the Screenie

 

"As you've stated the joystick was working ok previously,
then maybe an unrelated software, install or update, since that time,
is taking up previously unutilised PC resources,
i.e. it's tipped your PC beyond its capabilities."

 

 

No New Software other than TeamSpeak 3 (not used just installed) and no other programs running

 

"if your user's slider settings are set too high,
 versus your PC's capabilities

 

 An unresolved mesh
 may cause your aircraft to spawn at an elevation above
 the finally resolved mesh elevation."

 

"As a final resort -
try clicking FLIGHT's main menu - Options
then clicking the Defaults button
on each of the 5 LH menu buttons.
Then clicking Accept."

 

 

This IS the case - using 'Low' across the board the game works flawlessly - Yeaaa

I must have increased an extra setting before this started

So obvious and simple I overlooked the settings

Now to see how far I can increase the settings without crashes

 

THANK YOU again        I appreciate the help

 

[stonelance 136]

Wow, that is unfortunate.  I've never known about anything like this but the input code in FSX\Flight is very ancient...

[EzRyder 35]

_{I've never experienced this (crashes) in FSX myself so its new to me (It always just took forever to load and became unplayable - jittery and too slow to react to input)}

 

_{Thinking back I 'ramped up' the settings before getting the Alaska Pack and then finished 'collecting' the Hawaiian Airports so I didn't notice right away, making me think it work ok}

 

_{The good news is I can run the settings up to Medium + Max on Scenery Density so I'm not 'missing' anything (Trees, buildings, etc.) and still have excellent graphics and performance  :lol:}

 

Much higher and I "tip the scale" as basys suggested (I can run up some of the 'less important' settings but backed them back down to med for performance)

 

_{I Apologize for the trouble and concern over such a simple oversight on my part      Thank you all for the help}

[188AHC 2,138]

No worries about posting anything like this.  It's good to share all our problems no matter how minor they may end up being. Someone down the line might have the same problem and the answer will be here for them.  Thanks for posting this as I learned something in the process too even though I haven't had the problem.

[Moe 6]

No need to apologize. In aviation we have a saying. " The only stupid question is the one you don't ask " I ask questions here every week. Some might roll their eyes and think oh it's Moe's stupid question of the week... again. But I don't care and like 188AHC said we lay out information for the next guy with a similar problem. Everybody wins. Keep the questions coming.

 

Moe