"long" flight causes fsx to shut down

[mith]

Anyone else have this problem?

My system's fairly new. My hard drive is an NTFS, processor is dual core 2.4 ghz 6600. Video is Nvidia GTX 460 driver 8.17.12.8026... (that's all I know... LOL)

Anyway, I have FSX with all the updates. I'm having problems flying long distances (using cerados's skymaster). I fly from Brackett airport (In San Dimas) to Las Vegas. I got one error, "Out of memory".... and other times, the sim just shuts down.

Any clues why this is happening?

[nickg44]

Have a look at this post...

http://forum.avsim.net/topic/279201-freezing-during-long-haul-flights/

You need to get the uiautomationcore.dll file and place this in your FSX folder if you have not already done so. It can be down loaded via Google...

[mallcott]

Doesn't sound like the GUI problem, not with out of memory errors. You probably need the Highmem fix in the FSX.cfg

[icarus2]

read this..

http://www.flightsim.com/vbfs/showthread.php?214058-Fsx-out-of-memory-problem

[mith]

replacing putting uiautomationcore.dll in my fsx file didn't work.... any other suggestions?

[mallcott]

Did you try the highmem fix? It was suggested for a reason!

[mith]

Not sure what the highmem fix is.... but let me update this thread:

I reduced a lot of the settings. I reduced the mesh settings. I also reduced the antializing settings to X8. I put the pre-rendered frames to zero (not sure what that does... but I figured it meant that he was pre-rendering the scenery in advance). I also shut of vertical synchronization. I was able to fly from Brackett (San Dimas) to Las Vegas X16 speed. Once there, I flew back to Brackett at a normal speed. Both trips were uneventful. I also changed from 32 to 16 bit (didn't notice a scenery quality difference).

So I guess I've solved the problem. I added the above .dll, but it also froze with it installed.

So bottom line is, that I guess you have to reduce the scenery quality (though I'm not sure why this is the solution as my computer is not a slow computer.

But for now.... my problem is solved.

[schick]

i have the same problem too. except instead of FSX shutting down, my laptop gets shut down!

[mith]

Try lowering you video settings.... as I have mentioned. My anisotripic setting is zero (application controlled). I suspect that the antialiazing setting needs to be lowered. Put your pre-rendered frames to zero. (as I said, I'm not sure what this means, but I turned it off as I can't see a difference in quality).

I can't believe that a system like mine is not able to handle FSK.... but apparently isn't not. Try lowering the above settings as I have mentioned (not just in the game, but also with your video card). I wish you good luck.... taking a LONG flight only to have the sim stop is FRUSTRATING! You'd think that with all the newer technology, this type of pcrap would no longer be an issue.... apparently it is.

I'm not a computer geek (though I probably know more than the average computer person).... but I'm not able to follow all the advice about uppering the virtual memory limits etc.... LOL

[Paxx]

i have the same problem too. except instead of FSX shutting down, my laptop gets shut down!

This sounds like a heat issue. FSX will heat things up. If your ventilation is blocked, reduced or overwhelmed, the safety features of your processor will shut your system down to avoid permanent damage.

Laptops are not ideal for FSX. Check your system for dust or failed cooling fans. Lowering your FSX graphical settings as suggested above will help somewhat with heat issues as less load will be placed on the system.

[mallcott]

Not sure what the highmem fix is.... but let me update this thread:

I reduced a lot of the settings. I reduced the mesh settings. I also reduced the antializing settings to X8. I put the pre-rendered frames to zero (not sure what that does... but I figured it meant that he was pre-rendering the scenery in advance). I also shut of vertical synchronization. I was able to fly from Brackett (San Dimas) to Las Vegas X16 speed. Once there, I flew back to Brackett at a normal speed. Both trips were uneventful. I also changed from 32 to 16 bit (didn't notice a scenery quality difference).

So I guess I've solved the problem. I added the above .dll, but it also froze with it installed.

So bottom line is, that I guess you have to reduce the scenery quality (though I'm not sure why this is the solution as my computer is not a slow computer.

But for now.... my problem is solved.

Typing highmem fix into the search box is a good place to start, then you can learn about it as well as the best process for seekling help. Yours is not a unique problem therefore it follows that you should have at least looked for the solution before trying these wild (and sorry to say, ludicrous) fixes. If you won't take advice, then why ask?

But don't worry, I've used the search tool for you and come up with the attached, which will provide a solution.

http://www.flightsim.com/vbfs/showthread.php?215869-FSX-s-newest-silent-and-uneventful-quot-crash-quot-....-Help&highlight=highmem+fix

[Cas141]

I'm afraid the fact is that 2.4 ghz processor speed for FSX is on the slow side these days. Latest 'puters are running at 4 ghz or more and can still be tamed by FSX if the sliders are too far right. IIRC FSX uses only one core and benefits better
from processor speed than a top notch graphics card etc.
Flying FSX? - get the fastest processor you can.

Gawd knows what we'll need to run MS Flight when it comes out -lol

[mallcott]

I'm afraid the fact is that 2.4 ghz processor speed for FSX is on the slow side these days. Latest 'puters are running at 4 ghz or more and can still be tamed by FSX if the sliders are too far right. IIRC FSX uses only one core and benefits better
from processor speed than a top notch graphics card etc.
Flying FSX? - get the fastest processor you can.

Gawd knows what we'll need to run MS Flight when it comes out -lol

No, that is not why the error message is generated. It has nothing to do with processor speed. You should also read the link.

[mith]

I'm afraid the fact is that 2.4 ghz processor speed for FSX is on the slow side these days. Latest 'puters are running at 4 ghz or more and can still be tamed by FSX if the sliders are too far right. IIRC FSX uses only one core and benefits better
from processor speed than a top notch graphics card etc.
Flying FSX? - get the fastest processor you can.

Gawd knows what we'll need to run MS Flight when it comes out -lol


I'm using So. California photo scenery and never use the option for generic houses etc. I don't think they (MS) got the scales right, besides with photo scenery.... the auto-gen scenery makes it look like crap.

I will soon be purchasing that produce of photo scenery of the usa... I'm gonna LOVE that! hehe. But ya, one can never have too fast of a computer when dealing with MS FSX LOL