• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

Question on FSX stability

Editing the panel.cfg to add a GPS is no problem. I've been doing that and more for years. :icon_lol: I went with the GPS parameters from Ant's Trojan, BTW.

As for the original topic, I took several flights yesterday with the first uiautomationcore.dll until I started getting the "out-of-memory" warning so today I will use the second dll and see what happens.

As I mentioned in my original post, if I stay with one aircraft and one flight I usually have no problem. But when I attempt to exit a flight and switch aircraft or flightplans or both then eventually I get the "out-of-memory" warning, message or just FSX quits.

On my system I have a MS desktop theme with sounds, so as I approach the memory issue the computer starts squawking at me that its about to terminate or lock the program. So I basically have to exit FSX before it makes that decision on its own. If I reach an OOM and the program quits, then it records an error log that I can examine which in this case has pointed to the uiautomationcore.dll as being the affected module.

All kinds of fun. :sleep:
 
uiautomationcore is not the cause of OOM errors. having the correct uiautomationcore file will fix CTD's due to menu issues (so if you go to a menu mid-flight and change aircraft, or time or season if FSX crashes immediately with a "fatal error" message that's the crashes that this file will fix) OOM's are caused by you exceeding the 4gb VAS, nothing else. The main reason you are having this issue seems to me the fact that you are changing aircraft etc... without ending the flight and starting over. fsx does not clear VAS properly when you load a new aircraft, so the VAS is now holding the data from multiple aircraft, not just one. if these are high-detail complex aircraft, you can go through your VAS like nothing. other things that eat up the vas is complex scenery, high detail cloud textures, high detail land textures, and having your LOD set too high (you'll get more OOMs at 6.5 than the max default 4.5) you add all these things up, and you will have OOM's some things to try:

One aircraft per flight, make a new flight if you want to fly something else
limit clouds and other textures to 1024x1024, still looks great and doesn't eat up the memory as much
only load scenery you are going to take off or land from. if you fly over high detailed airports that will eat up the space as well.
limit your detail LOD (I fly 5.5 but it probably should be 4.5 if you can live with it)
FSUIPC doesn't prevent OOM's but does give you a warning ding when you're about to go over that can give you time to save your flight.
DX10 mode- still not perfect, but I get FAR less OOM's when running in DX10 mode, and there will soon be available a dx10 fixer app that purports to fix most of the remaining issues.

OOM's have been my bane as well sice I got a high end system. now that frame rates are no longer a concern, I'm pushing the envelope a lot more with scenery and aircraft, which loads up the VAS. hopefully p3d version 2 can be 64 bit which will make this a thing of the past.
 
ShawnG said:
uiautomationcore is not the cause of OOM errors. having the correct uiautomationcore file will fix CTD's due to menu issues (so if you go to a menu mid-flight and change aircraft, or time or season if FSX crashes immediately with a "fatal error" message that's the crashes that this file will fix) OOM's are caused by you exceeding the 4gb VAS, nothing else.
Click to expand...
Agreed. Am working on the uiautomationcore first.

ShawnG said:
The main reason you are having this issue seems to me the fact that you are changing aircraft etc... without ending the flight and starting over. fsx does not clear VAS properly when you load a new aircraft, so the VAS is now holding the data from multiple aircraft, not just one. if these are high-detail complex aircraft, you can go through your VAS like nothing. other things that eat up the vas is complex scenery, high detail cloud textures, high detail land textures, and having your LOD set too high (you'll get more OOMs at 6.5 than the max default 4.5) you add all these things up, and you will have OOM's
Click to expand...
Makes perfect sense. No change to the LOD. It remains at 4.5. I still use simple clouds and avoid realistic weather most of the time. I'll have to research replacing the cloud textures.

As for the complex scenery, the majority of flights are within ORBX PNW and I'm just now adding some of their airports is Washington State is my home state. Flying to and from the airports in the area doesn't seem to cause the problem, it's mainly when I access the menu to change aircraft or some other parameter in flight.

ShawnG said:
some things to try:

One aircraft per flight, make a new flight if you want to fly something else
limit clouds and other textures to 1024x1024, still looks great and doesn't eat up the memory as much
only load scenery you are going to take off or land from. if you fly over high detailed airports that will eat up the space as well.
limit your detail LOD (I fly 5.5 but it probably should be 4.5 if you can live with it)
FSUIPC doesn't prevent OOM's but does give you a warning ding when you're about to go over that can give you time to save your flight.
DX10 mode- still not perfect, but I get FAR less OOM's when running in DX10 mode, and there will soon be available a dx10 fixer app that purports to fix most of the remaining issues.
Click to expand...
I've resolved to limit one aircraft per flight. Yesterday's test of the uiautomationcore.dll included three different flights before I had to shut down FSX. Most likely it's FSUIPC warning I hear. There are also some good suggestions at the FTX ORBX forum I'm looking into as well if things continue.

ShawnG said:
OOM's have been my bane as well sice I got a high end system. now that frame rates are no longer a concern, I'm pushing the envelope a lot more with scenery and aircraft, which loads up the VAS. hopefully p3d version 2 can be 64 bit which will make this a thing of the past.
Click to expand...
Glad you're on our side. :jump: I've only been flying FSX since February, so it may be awhile before I'm ready to jump to P3D.
 
Excellent advice from ShawnG, I also run FSX in the Dx10 mode and cannot remember
the last OOM error.
I use REX addon clouds, complex addon aircraft and routinely use LOD 8.5 in both FTX scenery and photoscenery
without incident.
I look forward to the upcoming Steve Parsons fix programme/program/app.

Regards,
Nick
 
You must log in or register to reply here.
Back
Top