...Have to be careful during tests, I found that ShadowPlay can cause errors during running the sim but are not reported, although FSX can exit with an exception. I have the latest nvidea driver and beta ShadowPlay, but it was set to a sleeping drive.

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.

Ok. But what do you suggest people do when if they dont use HIGHMEMFIX, they have a skeleton aircraft?

I think the missing wings type of thing is down to a problem like selecting too dense scenery. GPUs since FSX came out all handle the texture load no problem. Look at any modern HD game able to run 100fps+, the GPUs are all good these days.

[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.

 

Sorry Steve, this is 100% wrong. This setting was supposed to be defaulted to 1 in FSX SP2 and Acceleration (and actually is in ESP) but it was missed by the ACES devs when that stuff was released. When the setting was discovered by Bojote, we talked to the former ACES team members involved and they confirmed for us that it was supposed to be on and that there were no ill effects to be had from it. If you don't have it on with a modern system you're going to see missing textures and skeleton models as the VAS load increases toward the 4GB limit. I have never had a single freeze as described in this thread and have been using that setting since the day it was discovered - it's not caused by that.

Yes, I know that's the theory seems to have emerged over the years, it's not like I don't understand that. Back when it was introduced I had a couple of PC's that went wrong with it in use. Since then I never used it. The only times I've had issues, it's when that's been set for experimental reasons. It may not be in itself alone the cause of any issues, like with the problem I had with ShadowPlay came up the first time I had that set, after several weeks flight after flight and no issues, and now OK. In reality it's supposed to do nothing (recent hardware) at all.

if i were you. i'll just reinstall FSX. that's the only possible fix.

 

 

Yes, I know that's the theory seems to have emerged over the years, it's not like I don't understand that.

I wonder if you do ? it is not a theory, but a fact. or did the Aces team just guess about highmem fix ?

 

The thing is, not everyone runs the same set up, hardware and software. if settings have to be so low to run without highmem fix, I would rather have highmem fix.

Why remove something that works for the majority. All you are doing is confusing the issue.

To compare, what is your system specs, and what about FSX, care to share your display settings. It is very hard to verify what you say without seeing your configuration.

 

 

I think the missing wings type of thing is down to a problem like selecting too dense scenery

how low must one go ?

Sounds like a really fair idea. Give me a situation that HIGHMEMFIX=1 fixes, and I'll eagerly replicate it here to see for myself. I'm waiting.

Sounds like a really fair idea. Give me a situation that HIGHMEMFIX=1 fixes, and I'll eagerly replicate it here to see for myself. I'm waiting.

 I don't have to prove that highmem works, you have to prove that it is not required.

All you need to do is provide your display settings and system specs. Why are you turning the request i made to you back at me ?

Rubbish, if you are applying a fix then show me why you need that fix, that is my argument. Your argument is that it is required, show me why. I'm waiting.

Once you provide your system specs and display settings, then we can talk, until then forget it.

Roll back to the earlier part of the discussion; my point to locate a problem is to pare back the sim of any stuff non-standard to begin isolating from the simplest setup, including remove highmemfix=1. Which the topic become a fork in the thread about highmemfix.

 

 

3960x+GTX680+1920x1200

 

 

Rubbish, if you are applying a fix then show me why you need that fix, that is my argument. Your argument is that it is required, show me why.

I'm waiting

Bare bones, clean fsx cfg, I get a black screen going from full screen, window back to full screen. More so with add on planes like PMDG and AS Airbus extended.

Sometimes I get a skeleton plane and performance is crap.

 

I7 2600K GTX 580 1920 X 1080

Bare bones, clean fsx cfg, I get a black screen going from full screen, window back to full screen. More so with add on planes like PMDG and AS Airbus extended.

Sometimes I get a skeleton plane and performance is crap.

 

I7 2600K GTX 580 1920 X 1080

I'm waiting

Bare bones, clean fsx cfg, I get a black screen going from full screen, window back to full screen. More so with add on planes like PMDG and AS Airbus extended.

Sometimes I get a skeleton plane and performance is crap.

 

I7 2600K GTX 580 1920 X 1080

 

The presence or absence of highmemfix=1 has absolutely no impact on my system in those respects. I've never had a skeleton plane, but I've been running all the PMDGs and the AXE etc. anything with an FMS. Plus I've got scenery from Anchorage to ORBX etc. 

 

Nothing fixed by highmemfix=1 here so far...

 

Quite a challenge would be to provide a problem notably fixed by adding highmemfix=1.

 

:smile: 

 

 

 

 

 

 

Maybe my 580  needs it Steve ? It certainly fixes the skeleton and black screen issue. I don't get ntdlll errors or CTD's freezes etc etc.