I realize that I may be overlooking something in one of my addon's configuration options, but I'm trying to figure out a strange occurrence that keeps happening with my FSX setup. I've got my FSX.cfg tweaked and machine setup for optimum performance, and just recently got my first OOM. Then, it kept happening- even without AI traffic. I scratched my head, and took a quick look in my FSX.cfg, only to see that my TML setting had been changed to 4096. 

 

Now I know there are many threads here that are about preventing FSX from changing this setting BACK to 1024, but mine is the opposite problem: My TML keeps getting changed to 4096, an HD setting- and my OOMs keep returning after I thought I've fixed the problem.

 

I've double checked with FSDT's addon manager, and confirmed that "force 2048/4096" is "off"- 

 

does anyone know what other addons "edit" fsx.cfg to force these HD textures? REX? ORBX? Will the guilty developer please stand up!

Do you have the Texture Max Load Editor service running?

 

regards,

Joe

That sounds like it- what is it? A process/exe running in the background?

That sounds like it- what is it? A process/exe running in the background?

 

If you don't know what it is, then you probably don't have it, as it's a 3rd party utility. One thing you may have is te FSDT's Addon Manager, that will force this setting, as well as others if set to do so. Check if it's set there, if it is just turn it off.

 

Check if it's set there, if it is just turn it off.

If you read the op first post he has stated  that he has turned it off, the only other addon I can think off  is  orbox   has  a tool where  you can set it to 1024 or  4096.

Some Aerosoft airports do too, like Helsinki ( I think) 29 Palms etc etc

If you read the op first post he has stated  that he has turned it off, the only other addon I can think off  is  orbox   has  a tool where  you can set it to 1024 or  4096.

Or 2048. I use this tool as it used to lock the fsx.cfg to whatever you chose whatever messing about with graphics/scenery/why. Sadly, this doesn't seem to work as it did. (DX10?) I've had to revert to checking every so often. <_<

Or 2048. I use this tool as it used to lock the fsx.cfg to whatever you chose whatever messing about with graphics/scenery/why. Sadly, this doesn't seem to work as it did. (DX10?) I've had to revert to checking every so often. <_<

 

I'm with you Ron... It is happening where it will stay at 1024 for several FSX start cycles, and then somehow reconfigure. I have to check every so often as well. 

strange  doesn't happen with me   although I don't use dx10

SimLauncher has the option to manage TEXTURE_MAX_LOAD and also LOD_RADIUS.  As long as you use this program to load and start your flights, the settings will remain.  If and when you use the FSX load/start then the settings will revert to the FSX default of 1024 and 4.5

 

Various virus checkers will return a false positive on parts of SimLauncher but those can be identified and quarantined.

 

 

If and when you use the FSX load/start then the settings will revert to the FSX default of 1024 and 4.5

 

Nope, only happens if you access the settings page.

 

Otherwise we would never be able to have higher settings.

 

regards,

Joe