August 6, 201114 yr Not sure if this has been looked into or whether it's a personal problem. But somehow only NGX does this: This is when I click on the NGX on "Free Flight" screen, and leave it there for a while. The textures and all seems to just go and get what you see in the image. Ideas? Thanks Brendan Chen Learning to use and getting use to FSX!
August 6, 201114 yr Commercial Member Please check out the introduction PDF, you need to put HIGHMEMFIX =1 in your fsx.cfg
August 6, 201114 yr Author I do have it in there, under [GRAPHICS] section. And I see also other threads talking about this, but they seem to imply they are at the in-game stage, rather than select aircraft stage. Brendan Chen Learning to use and getting use to FSX!
August 6, 201114 yr Author Can anyone please shed some light on this? As well as an OOME if I leave it on the "Free Flight" screen for too long? Brendan Chen Learning to use and getting use to FSX!
August 6, 201114 yr Hardware you're running? ___________________________________________________________________________________ Zachary Waddell -- Caravan Driver -- Facebook: http://www.facebook.com/zwaddell Avsim ToS Avsim Screenshot Rules
August 6, 201114 yr I have the same problem and have the highmemfix cfg change as well. I get this during spot view with the textures eventually filling in. I'm experimenting with Texture_max_load settings (not at my computer at the moment) so will report if that makes a difference. I don't have any other aircraft that exhibit this behavior BTW. Thanks,Mark
August 6, 201114 yr Might be an issue with your video card. Have you installed the latest drivers? Matthew Bellette
August 6, 201114 yr Author I just want to confirm that it's HIGHMEMFIX, not HIMEMFIX? I will also try play with the max load and see how I go. But I would like to add, this grey problem I'm getting is not on initial loading at "Free Flight" screen. On initial load, it seemed fine, only if I leave it for some time it turns into what you see in my image. If I leave it for a while more, it gives me OOME which doesn't happen to other aircraft. So I'm suspecting it shouldn't be my FSX's problem. My specs are:i7 950 OC 4.0GHzNVidia GTX480 1G (I think)8GB Kingston Ram (9-9-9-27 IIRC)MB is Gigabyte UD7-X58AWin7 64-bit Brendan Chen Learning to use and getting use to FSX!
August 6, 201114 yr 275.33's Latest WHQLfrom nVidia. If this was a driver issue, I'd see it with other AC.HIMEMFIX is an error in the Introductory manual, should be HIGHMEMFIX.
August 6, 201114 yr Author 275.33's Latest WHQLfrom nVidia. If this was a driver issue, I'd see it with other AC. Well I haven't checked the driver version, but what newtie said applies to me as well, this seems to only occur for the NGX... Brendan Chen Learning to use and getting use to FSX!
August 6, 201114 yr Windows 7 uses WDDM 1.1, FSX was built with 1.0 - This is most likely causing your issue. The only way to revert this is to run FSX in compatibility mode for Vista SP2. It will fix it right away.
August 6, 201114 yr Author For the sake of testing, I changed the texture load value to 4096 as suggested by the introduction, to see if this issue happens. And I confirm that it does. Now, when I tried it and left it on that screen for some time, got it to look skeletal, then load into the sim. This is what I get as illustrated in the image below: Sorry if any of my comments seem ignorant. I've just moved from FS9 to FSX purely for NGX, so some of what might seem common sense I might not have experienced. Windows 7 uses WDDM 1.1, FSX was built with 1.0 - This is most likely causing your issue. The only way to revert this is to run FSX in compatibility mode for Vista SP2. It will fix it right away. Tried, issue still remains. But thanks for your suggestion. Brendan Chen Learning to use and getting use to FSX!
August 6, 201114 yr Moderator I had the same issue most likely due to only running 2 GB of RAM in my case, so I resized my exterior repaints from 4096 down to the normal 1024 size and it cleared it up for me. Not saying this will help you, but I usually only run 1024 clouds and a/c textures at 1024 to save some overhead. Now I just wish that there was sometype of automated tool that I could use to downsize all the paints I downloaded yesterday to 1024 since doing each on piece by piece was time consuming. Sean Campbell Avsim Board of Directors | Avsim Forums Moderator
August 6, 201114 yr Author I had the same issue most likely due to only running 2 GB of RAM in my case, so I resized my exterior repaints from 4096 down to the normal 1024 size and it cleared it up for me. Not saying this will help you, but I usually only run 1024 clouds and a/c textures at 1024 to save some overhead. Now I just wish that there was sometype of automated tool that I could use to downsize all the paints I downloaded yesterday to 1024 since doing each on piece by piece was time consuming. Sean Campbell Thanks Sean. When I discovered this issue, it was running at 1024. I changed it to 4096, but it had no effect. Brendan Chen Learning to use and getting use to FSX!
August 6, 201114 yr Moderator Thanks Sean. When I discovered this issue, it was running at 1024. I changed it to 4096, but it had no effect. Brendan, i'm not talking about the fsx.cfg entry of 1024 or 4096. I mean that I actually resized the textures themselves from 4096 to 1024 which cuts the file sizes down from 16385Kb to 1366Kb. That's one reason I never buy McPhat repaints is beause the 4096 textures require too much overhead for the small amout of RAM I have installed. Even if you only have 1024 entered in your fsx.cfg it still needs to load the texture but wont display it at the highest resolution. Sean Campbell Avsim Board of Directors | Avsim Forums Moderator
Create an account or sign in to comment