Archived

This topic is now archived and is closed to further replies.

AirWayMan

Crash on Spawn - ALOT

Recommended Posts

I can barely get to a Job - the aircraft crashes the moment it spawns and I then lose joystick & keyboard input  if I 'Restart Mission'  (It loads using the restart) :(

If I exit and choose another mission then I crash again - I can load FreeFlight OK but I do have this problem on rare occasion, I just select 'Fly' and land to fix it in FreeFlight.

 

If I keep trying (exit game-restart game-restart a job) I can eventually get it to load but it may take as many as 7-8 tries  :(      usually 2-3

 

This just started (I thought 'joystick' at first) and I haven't changed anything except maybe using repaints, but I have been using them since before this problem started.

 

No updates to windows, drivers, etc

 

Has anyone else had this kind of a problem?

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

I know that on certain airports the C-46 is too large for the parking space it gives you. Not sure which plane you're using, but you may want to try the Maule or Cub, or takeoff from a larger airport. As for the joystick, make sure it's plugged in well, then go to Options, Aircraft Controls/Game controls, make sure that the game can recognize your joystick by switching the input device from keyboard to your joystick. If it doesn't show up with your joystick try a different USB port.

Share this post


Link to post
Share on other sites

I know that on certain airports the C-46 is too large for the parking space it gives you.

Does this mean it crashes the C-46? Mostly happens with the Maule but the cub and icon do it too (I don't have the C-46)

Also it is more prevalent in Alaska were it crashes every load with the Maule and every other load with the cub (happens only every 3-4 loads in Hawaii) :(

 

Joystick shows and is plugged in the same as always - but will try a different port for good measure - I did remap a button yesterday for TeamSpeak (also installed TS yesterday) but this started the day before - I have racked up 30+ crashes in 2 days and only got to fly 3 times :0

Share this post


Link to post
Share on other sites

After some more testing (and more 'crashes')  :)

This appears to have something to do with placing of the aircraft at a new location.

If I save my place in freeflight it will load - if i change locations 'crash'

If I start in the air in freeflight it loads.

If I load a mission (even at the same airport) 'crash'

I can load a mission i don't want to fly 'crash' exit freeflight (without exiting the game) then chose another mission from the same airport and it loads.

I just sent Microsoft a message (are they really using Facebook for a support forum?) lets see how long till they respond :)

I know not alot is known about the inner workings of this new a game so I appreciate the suggestions - thank you.

Share this post


Link to post
Share on other sites

I suggest you do some trouble shooting. Lets start with not expecting MS to respond. They never once responded to my questions in the last 8 years. Second try to isolate if the problem is software or hardware. Get another joystick or unplug the one your using and fly with the mouse. Someone you know must have a joystick or game controller you can borrow. Then try as suggested a different USB port. Re examine your game controller settings. Do you use separate software for your controller? could there be some such software operating and conflicting with MSFlight's own software. Saitek controllers for instance have not only their own drivers but there own configuring software. So lets start there.

 

Moe

Share this post


Link to post
Share on other sites

This is very strange. I have never had any kind of problem like this. Yes, try a different joystick to begin with. MS is more likely to respond in the Steam forum I think. 

 

Steve

Share this post


Link to post
Share on other sites

More tests - more crashes  :)

 

First thank you all for the suggestions

 

My joystick is a Saitek Cyborg v1 - I never installed the 'SST Programing Software' as its optional (Plug & Play - Windows installed the drivers - Maybe try the software?)

 

1st test unplug joystick, reboot, & try game -> crash
2nd test remove joystick drivers, reboot, & try game -> crash
3rd test reinstall drivers, reboot, & try game -> crash
4th test plug in joystick & try game -> crash

 

I did quite a few more tests with different aircraft & locations but no change still crashes anytime the game relocates my aircraft.

 

Not sure why you suspect the joystick, its been working for 2-3 wks (with this game - the stick i've had for most of a yr) with no changes but thnx I want try everything to eliminate any possibilities :)

 

I don't have access to another joystick atm but will borrow one tomorrow (tried without one at all so not sure this is necessary)

Sherlock Holms - “Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth.”

Share this post


Link to post
Share on other sites

And what about your joystick assignments? Did you change them? Can you unplug the joystick and perform a test with joystick defaults?

Share this post


Link to post
Share on other sites

4th test plug in joystick & try game -> crash

 

Yes this was with 'default joystick assignments' I guess - I have before and since changed them

 

Guys do you really think it could still be the joystick?  Even when the program crashes with no joystick or drivers installed (and a cold reboot in between) ?

 

It only crashes when the aircraft is relocated by the menu (on about every 3rd crash I can see the aircraft 'falling' from what looks like 20 ft up)

Share this post


Link to post
Share on other sites

I think you have ruled out the stick. In the old days when Things got mucked up enough with FSX FS9 and P3D I would just wipe out the config file and let the program just build another. I can see the config easily for Flight and you could delete it but I don't know if Flight will rebuild it. You could save it to another location and see what happens.

 

Moe

Share this post


Link to post
Share on other sites

The next time you crash, could you provide a screenshot of what happened? I think it would be easier to analyze what's going on if we could see it.

Share this post


Link to post
Share on other sites

Tried a Logitec FlightPro joystick this morning with the same results

 

The next time you crash, could you provide a screenshot of what happened? I think it would be easier to analyze what's going on if we could see it.

Sure :)

 

Loading a flight then ...

 

Hard to catch this one as it happens immediately on spawn

 

Final Result  :(

And here is the same thing in FreeFlight (no Mission selected)

 

 

 

Again I reiterate this only happens when I RELOCATE the aircraft either by selecting a mission or changing airports in FreeFlight from the menu- I can Airport hop all day (reloading as many times as I want) so long as I DON'T change locations from the menu.

 

Also to clarify: In my first post I said -

 

I then lose joystick & keyboard input  if I 'Restart Mission'

This should say I lose ALL input - joystick, keyboard, & mouse (the only key that works is ESC)

But this is only if I use the 'Restart Mission' button - if I exit the Mission and start a new one I don't lose inputs.

Share this post


Link to post
Share on other sites

It sounds to me like you have a bad install. Any chance you could delete (after backing up your career files) and re-installing Flight?  This is the first instance I've heard of this happening.  If you have a Steam install, verify your local files and let Steam d/l any that are corrupt or missing.

 

Sometimes with a problem such as this, it's necessary to start over and only install one thing at a time in order to identify the culprit.

 

Keep us posted as you go and maybe someone can key in on what the problem might be.

Share this post


Link to post
Share on other sites

Do you use the Map key (M) to move your aircraft around to different airports rather then the menu? Or does it make no difference either way? just wondering!

Share this post


Link to post
Share on other sites

Any chance you could re-installing Flight?

Yes that's my plan  :)   but I have 3g Broadband (~70kb/sec max)  atm - waiting until Monday for High speed cable to be installed

 

Do you use the Map key (M) to move your aircraft around to different airports rather then the menu? Or does it make no difference either way? just wondering!

I hadn't used the (M) before but checked and It makes no difference

Share this post


Link to post
Share on other sites

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?

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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  :)

Share this post


Link to post
Share on other sites

Sounds like you have justified a new computer to me.

 

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

 

Just saying

 

Moe

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

 

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites