So I just left LIPZ in a thunderstorm four times with and without, and both times without was smoother and 19fps was held, whereas I saw 6fps with HIMEMFIX=1. Perhaps seven years ago the GPUS may have responded but I never saw it then. Some guys here seem all too easily upset. I'm not attacking personal feelings on the subject, i'm saying "eliminate your stuff", so what if there's not been issues with it before. The guy in the fancy story had a new version of a plane he used regularly before he got the new PC so he felt new PC and new version would be nice altogether, spent all night with it.

 

To be honest that sounds like something wrong with your system. Graphics card on it's way out?

Guys being personally affected by the idea of turning off anything to test stuff by elimination seems a bit sad.

Guys being personally affected by the idea of turning off anything to test stuff by elimination seems a bit sad.

 

Nice - you've turned from defensive to offensive. This shall be my last communication directly with you in this forum. Have a good ride  ^_^

Insulting my GPU? I'm reporting you to NVIDIA. :lol:  So I tested again and with himemfix, in-cockpit, was worse every time. Maybe some simple changes to a system, maybe multiple monitors whatever has differing results, I've not tested them all. Will be interesting to find what the freezing is, maybe it'll clear up with the service pack.

Everyone does.  I have no idea what the intention of that message was.  Part of it was almost a question.  Regardless, how HIGHMEMFIX could cause stalling is completely beyond me.

 

I'm no expert but I think it's an old fix to allow GPUs more than 512Mb textures? Not required with more recent hardware. I think it could do something else now. In the tests this afternoon, I'm using the 777, stock FSX and with HIMEMFIX initially there appeared to be a few spikes of high fps, interspersed with lows. Once on the move I noticed the controls were less responsive, and a few fps dropped. Back with the HIMEMFIX gone there was an apparent smoothness.

You have to run without HIMEMFIX to be sure. I just googled around for a bit and found mostly stuff about how completely useless it is. :rolleyes:

 

I most definitely disagree.  Lots written about this on the old ACES blogs.  Useless it is not.

 

I just googled around for a bit and found a lot of stuff about the world being flat, too.  :shok:

 

Regards

I've been going through the logs of VAS used during testing with stock FSX + 777 this afternoon; generally around 1.4Gb without HIMEMFIX, and 1.6Gb with HIMEMFIX=1, each time flying from standstill to finishing a turn at the IDF. If anything I stayed in the cockpit longer on the final few non-HIMEMFIX flights just now and showed only 1.35Gb and 1.45Gb, I had 50% FSX Ai across the board.

 

Here it seems the only tweak said to be worthwhile, and yet finishes inconclusive. I would say a mere difference like 1920x1080 vs 1920x1200 might just cause the memory layout changes to make a difference. Anyway, I've tried it on all my systems since way back, and I'll check it again later to be sure, and I'll do it again with my next PC.

http://forum.aerosoft.com/index.php?/topic/33964-the-fix-for-fsx-stability/

This time flew up to the cruise altitude and only saw 1.49Gb VAS used, verses the 1.6-1.75 with himemfix.

 

 

..on the old ACES blogs...

 

Yes, maybe you hit the nail on the head there, Bob.

 

All the best

Anyway, back to the thread. Looks to me that it's the wise man that chooses to eliminate everything to be sure. Running with any kind of tweak, fix, or addon can add to your problem or mask true results. I showed less vehemence to himemfix than was shown to FSX ATC. No need to bicker so much about people on public forums simply because they hold another opinion, It's like Liverpool vs Chelsea. :rolleyes:

Just out of curiosity.....where should this "HIGHMEMFIX=1" statement be in the fsx.cfg file?

Just out of curiosity.....where should this "HIGHMEMFIX=1" statement be in the fsx.cfg file?

 

In the [GRAPHICS] section

[GRAPHICS]

HIGHMEMFIX=1

 

What I'm saying is, this makes a change to the memory layout on the GPU and also the FSX memory footprint. In a support situation this should be removed along with any other fix, tweak, or addon, in the first instance.

Lol, just for the heck of it I took HIGHMEMFIX out of the .cfg

 

FSX started in full screen.

I changed to Windowed mode so I could turn on the OPUS weather engine.

Immediately some knobs and buttons disappeared from the VC.

 

Upon changing back to full screen I got a black screen and nothing else.

 

Had to CTRL + ALT + DEL out of it.

 

Cant recommend taking HIGHMEMFIX out of the .cfg.

Guess PMDG and my source were right.....it is required ;-)

 

 

 

Further,

 

As for my test flights with the 777 to determain what causes the freezes....

 

As previously mentioned, I did two flights with ALL AI traffic disabled and with the OPUS weather engine running. Those two flights showed no freezes.

 

Then I did two flights with Airline AI on and the OPUS weather engine running.

Both frooze!

So I thought....SEE it is that AI traffic again.

 

Then I did another two flights with all kinds of AI on and the OPUS weather engine NOT running.......and.....NO freezes!

 

So now it looks more like a combo of 777 with AI and OPUS weather.

 

I will do more tests to try and establish a pattern.

 

If a combo is the cause....then it could be any combo on other systems (whatever combo taxes the system too much I guess).

And then each user just has to find out what he needs to turn off or down to stop the freezes.

Just my half-a-penny here, I had these 3-5 second freezes in the sim that have been plaguing me lest week. Using the search function I found that someone fixed it by removing their FSDT JFK. And I though it may have something to do with addon manager.

 

Sure enough, I reinstalled addon manager from the fs dreamteam website and I no longer have these momentary brainfart moments in the sim.

 

It may not be anyone's issue here but just sayin'.

Also,

 

anyone have any of these two programs/modules installed? I found that the FSCaptain module was doing FSX to CTD when loading the MD11 and the Aerosoft Module was doing FSX to CTD when loading the FlightSimLabs Concorde.

I'm not having any freezes but maybe you guys could use these to test.

Also, these is no use for those testing with a bare install of FSX.

 

  <Launch.Addon>

    <Name>FSCaptain</Name>

    <Disabled>True</Disabled>

    <ManualLoad>False</ManualLoad>

    <Path>FSCaptain\bin\FSCaptain.dll</Path>

  </Launch.Addon>

 

  <Launch.Addon>

    <Name>ASE-Data</Name>

    <Disabled>False</Disabled>

    <ManualLoad>False</ManualLoad>

    <Path>Aerosoft\ASE_DATA\AseData.dll</Path>

  </Launch.Addon>

Lol, just for the heck of it I took HIGHMEMFIX out of the .cfg

 

FSX started in full screen.

I changed to Windowed mode so I could turn on the OPUS weather engine.

Immediately some knobs and buttons disappeared from the VC.

 

Upon changing back to full screen I got a black screen and nothing else.

 

Had to CTRL + ALT + DEL out of it.

 

Cant recommend taking HIGHMEMFIX out of the .cfg.

Guess PMDG and my source were right.....it is required ;-)

 

You must have seriously hacked up your fsx.cfg to get that obviously weird result from simply changing just the HIGHMEMFIX setting. Just as well you kept a copy of your cfg. None of my systems exhibited any kind of behaviour like that. Right now I'm running full sliders on a non-overclocked 3960x+GTX680. The first thing I notice is a general chugginess to the controls. I can't use HIGHMEMFIX on it but it is a professional system.

 

Anyway at least you found it's a combo of FSX/OPUS/AiTraffic. You've got some weird problems with that setup, and really, you shouldn't be on a support forum with your faults. You should come back when you have a reliable system.