HIGHMENFIX not having in fsx.cfg should not interpreted as a bug. Just think about when fsx was released... 2GB of RAM were common where 4GB were pretty high end! Even single cores were the main cpu's used. Only later multicore's came to the market. I don't think they've ever imagined that there will be quad cores with 16gb of ram and 64bit os environments.

 

Also having fsx on 3 or 4 cores shouldn't matter much because there is only 1 main thread on 1 core which is the fps limiter. All other cores are idling or on low power. There shouldn't be any difference in having 2 "other" cores at 20% each or 3 "other" cores at 16% each beside the main 100% core.

 

I'm wondering if you get more fps when setting no affinity mask and disabling core #0 for other applications or when using affinity mask with physical core #0 disabled?

Yeah, HIGHMEMFIX apparently helped with some kind of texture loading problem on some cards back when FSX came out, not sure which. I've seen glitches with it today, a few momentary blank facets over urban leaving Heathrow, none showing with HIGHMEMFIX removed, ground shadows on, internal frame limiter at 19.

 

...back after a few more runs, confirmed consistently smoother simulation with no highmemfix, high density urban with ground shadows. I've not found any reason to change my mind on that matter.

Yeah, HIGHMEMFIX apparently helped with some kind of texture loading problem on some cards back when FSX came out, not sure which. I've seen glitches with it today, a few momentary blank facets over urban leaving Heathrow, none showing with HIGHMEMFIX removed, ground shadows on, internal frame limiter at 19.

 

...back after a few more runs, confirmed consistently smoother simulation with no highmemfix, high density urban with ground shadows. I've not found any reason to change my mind on that matter.

 

So how do you explain an improvement in performance using highmemfix on my system?  I am running a Titan.

 

Personally I think it is pointless doing all this guessing, what Rob needs is someone to log on and configure 'his' machine.  We can all have identical setups with different results.  

 

@Rob, if you want we can setup a Teamviewer and troubleshoot this.

 

Regards 

Mighty nice if you Rob :-)

 

But things are looking good with OPUS not running on core 0.

 

I dont see the fact that I need the HIGMEMFIX as a problem, nor as a corruption in my system.

It has been recommended by FSX specialists (software developers) for years that this should allways be in the .cfg!

All of sudden we are second guessing this?

I am not!

I will use HIGHMEMFIX, and everybody else should test for themselves if they need it or not.

 

 

I might come back on that offer if things go crazy again though ;-)

 

thx

So how do you explain an improvement in performance using highmemfix on my system?

I have no idea. The fix if it actually applies to the GPU, is likely to slow it down marginally.

My FSX used to freeze and stutters even when I upgraded or installed new scenery or aircraft.

 

Pentium I7 @ 3.8GHz, Quad, Win 7 64bit

16Gb RAM

120 Gb SSD for Windows 7

256 Gb SSD for FSX.

 

i even used to run out of memory when this happened.

 

I did one simple thing.

I changed my virtual memory from auto to system managed.

I have not had any problems with freezing or stutter since. I fix my framerate at 25Hz which works for me.

I have a very smooth running FSX, regardless of what aircraft or scenery files in use.

 

I do have a separate computer for GA-Panel and Plan-G.

My FSX used to freeze and stutters even when I upgraded or installed new scenery or aircraft.

 

Pentium I7 @ 3.8GHz, Quad, Win 7 64bit

16Gb RAM

120 Gb SSD for Windows 7

256 Gb SSD for FSX.

 

i even used to run out of memory when this happened.

 

I did one simple thing.

I changed my virtual memory from auto to system managed.

I have not had any problems with freezing or stutter since. I fix my framerate at 25Hz which works for me.

I have a very smooth running FSX, regardless of what aircraft or scenery files in use.

 

I do have a separate computer for GA-Panel and Plan-G.

 

A system with 16GB of RAM doesn't even need virtual memory though, I'm not sure how this makes sense... The entirety of FSX's VAS footprint can be placed directly into system RAM unless your system is somehow using 12+GB of RAM for other tasks while using FSX (which seems virtually impossible to me).

A system with 16GB of RAM doesn't even need virtual memory though, I'm not sure how this makes sense... The entirety of FSX's VAS footprint can be placed directly into system RAM unless your system is somehow using 12+GB of RAM for other tasks while using FSX (which seems virtually impossible to me).

 Windows does pre-cleaning (http://en.wikipedia.org/wiki/Paging#Pre-cleaning). Basically the OS will selectively write pages out to disk while keeping it in memory also so that when memory pressure goes up, it will be able immediately overwrite the in-memory pages.

 

The resizing process requires that the virtual addresses for everything to be recalculated so it could potentially freeze FSX.

 

Not saying that this is what is happening here, but at least theoretically it could be an explanation.

This is rediculous!

 

I said in post 23 + 24 + 28 + 30 + 41 that I am testing on a fresh Windows 7 installation, with a fresh install of FSX + Acceleration, with no other addons except the PMDG777 and the OPUS weather engine.

All brand new, standard, default stuff (except the 777 and OPUS).

 

This has gone far enough, as in nowhere, I am going stop responding to you.

Yes, me too.

 

But I am still testing to see if it is really FSX stock AI related or if maybe I get freezes as well without the stock AI.

 

So far I have done two flights with ALL forms of stock AI off, from JFK to Europe without freezes!

8 more to go. but that's for tonight/tomorrow.

Have you tried turning your OC down a bit? Was your comp OC'd before you installed FSX?

Yep, I figured this much. Did'nt make sense to me.

Did know why I used to run out of memory when fsx has such a very small footprint.

I do have FTX Global. FTX England, Orbx NW, Pacific NW and UT Canada, USA, Europe and Caribbean

VOXATC, Multicrew, Radr Contact, Ultimate Traffic and MY Traffic. Ground Services X

Texture resolution at 4096.

I use a TrackIR.

My scenery files at extreme setting and Aviation /GA Traffic at 80% and a couple of addons that run in the background.

And not too techy to investigate.

 

But it is the one thing I did and I have not had a any issues with FSX in a very long time.

 

 

Have you tried turning your OC down a bit? Was your comp OC'd before you installed FSX?

thx, but if you continue reading through this thread you will see I found a solution already.....I have not seen freezes since.

thx, but if you continue reading through this thread you will see I found a solution already.....I have not seen freezes since.

That's what I get for reading these forums on my phone lol.

[GRAPHICS]

HIGHMEMFIX=1

 

After a bit of testing I found it can cause problems with the graphics and contribute to sound anomalies. The sim may continue to run normally after an error, but cause an exception in ntdll.dll when exiting FSX, or may cause other problems there and then. It used up to 100Mb more VAS during the [exact] same flights and so could contribute to OOMs.

 

The "HIGHMEMFIX=1" line is not added by the service pack because it's not a universal fix. When FSX came out there were a few card that may have

benefitted from it.

 

 

Are we at a conclusion guys?  I don't have the stuttering problem mentioned on page one, but I do get OOMs landing at certain airports after a long flight.  I know I may have to tweak my graphics settings inside the actual FSX program, but, how do these figures look for in my .CFG?  

 

Windows 7 64

i2500K Sandy Bridge Quad

8gb ram

2gb Vid ATI

 

[bUFFERPOOLS]

PoolSize=5000000

UsePools=1

[GRAPHICS]

SHADER_CACHE_PRIMED_10=1693458432

SHADER_CACHE_PRIMED=1693458432

D3D10=0

TEXTURE_MAX_LOAD=2048

NUM_LIGHTS=8

AIRCRAFT_SHADOWS=1

AIRCRAFT_REFLECTIONS=1

COCKPIT_HIGH_LOD=1

LANDING_LIGHTS=1

AC_SELF_SHADOW=0

EFFECTS_QUALITY=2

GROUND_SHADOWS=1

TEXTURE_QUALITY=3

IMAGE_QUALITY=0

See_Self=1

Text_Scroll=0

HIGHMEMFIX=1

ForceFullScreenVSync=1

[GRAPHICS]

HIGHMEMFIX=1

 

After a bit of testing I found it can cause problems with the graphics and contribute to sound anomalies. The sim may continue to run normally after an error, but cause an exception in ntdll.dll when exiting FSX, or may cause other problems there and then. It used up to 100Mb more VAS during the [exact] same flights and so could contribute to OOMs.

 

The "HIGHMEMFIX=1" line is not added by the service pack because it's not a universal fix. When FSX came out there were a few card that may have

benefitted from it.

 

 

Let me put that into perspective for you:

 

Tests without "HIGHMEMFIX=1" recorded no errors whatsoever - 100% error free.

Only test runs with "HIGHMEMFIX=1" yielded problems.