Many of the 3D Virtual Cockpit textures disappear as FSX transitions to dusk, when using the PMDG 747 . I know, there are numerous posts about this, but as usual, nobody seems to agree on a solution. This is probably an FSX problem, but it doesn't happen with the FSX stock A/C. I have UTX products, but I still have the problem, even when they're disabled. I have a new machine with plenty of power, but it still happens. I don't like to mess with the .CFG file since, according to some posts I've read, it sometimes causes more problems than it solves. This is is especially true for someone like me with very limited computer knowledge. I would, however, attempt it, if I had some very specific proceedures to follow.

Excuse me if this post is in the wrong place, but, I really don't know what else to do at this point, except to fly during daylight hours.

Thanks

Unfortunately, adding stability tweaks to FSX is sometimes necessary in order to . . . achieve better stability! If you keep track of what entries you add or alter, you can always restore them later (or even automatically rebuild FSX.cfg by deleting it).

 

Two essential stability tweaks many people recommend are:

HIGHMEMFIX=1 in FSX.cfg, which eliminates aircraft rendering ("skeleton") issues most likely similar to the ones you are experiencing

UIAutomationCore.dll in the FSX main folder, which eliminates memory insufficiency/usage errors (e.g., after long flights, using menus too frequently, etc.)

 

For detailed, specific instructions, please reference the appropriate sections in Word Not Allowed's Guide (use the Find function in your browser).

Many of the 3D Virtual Cockpit textures disappear as FSX transitions to dusk, when using the PMDG 747 . I know, there are numerous posts about this, but as usual, nobody seems to agree on a solution. This is probably an FSX problem, but it doesn't happen with the FSX stock A/C. I have UTX products, but I still have the problem, even when they're disabled. I have a new machine with plenty of power, but it still happens. I don't like to mess with the .CFG file since, according to some posts I've read, it sometimes causes more problems than it solves. This is is especially true for someone like me with very limited computer knowledge. I would, however, attempt it, if I had some very specific proceedures to follow.

Excuse me if this post is in the wrong place, but, I really don't know what else to do at this point, except to fly during daylight hours.

Thanks

Unfortunately, adding stability tweaks to FSX is sometimes necessary in order to . . . achieve better stability! If you keep track of what entries you add or alter, you can always restore them later (or even automatically rebuild FSX.cfg by deleting it).

 

Two essential stability tweaks many people recommend are:

HIGHMEMFIX=1 in FSX.cfg, which eliminates aircraft rendering ("skeleton") issues most likely similar to the ones you are experiencing

UIAutomationCore.dll in the FSX main folder, which eliminates memory insufficiency/usage errors (e.g., after long flights, using menus too frequently, etc.)

 

For detailed, specific instructions, please reference the appropriate sections in Word Not Allowed's Guide (use the Find function in your browser).

 

The above is a brilliant answer, tell us if that solves it

Tried the HIGHMEMFIX, but it didn't help. I'm still having the same problem. I'll probably try some of the stuff in Word Not Allowed's Guide, but frankly, I don't really understand a lot of what's in there. Thanks for the reponse.

Tried the HIGHMEMFIX, but it didn't help. I'm still having the same problem. I'll probably try some of the stuff in Word Not Allowed's Guide, but frankly, I don't really understand a lot of what's in there. Thanks for the reponse.

You're welcome.

 

The two tweaks I suggested are probably your best bets. The rest of the software portion of Word Not Allowed's Guide consists mainly of performance tweaks, which are not necessary if you do not feel comfortable experimenting. Make sure that you have placed HIGHMEMFIX=1 under the appropriate section of FSX.cfg.

I put HIGHMEMFIX=1 in the GRAPHICS section of FSX.CFG., is that right?

You didn't specify where, or maybe I just missed it. I thought the UI AutomationCore fix was for crashing problems. I'm not experiencing anything like that. It's just the transition from day to night, with the loss of half the VC, that's giving me fits. Everything else works great!

I had this problem on my old machine, but this new one has really powerful components. That's why I'm rather frustrated at the moment.

FSX is like an old car. You can only fix it so many times, and then it's time for a new one. Thanks again.

I put HIGHMEMFIX=1 in the GRAPHICS section of FSX.CFG., is that right?

You didn't specify where, or maybe I just missed it.

That is correct. To save myself from having to type the specific instructions multiple times a day, I meant to suggest that you reference the instructions contained within Word Not Allowed's Guide. Regardless, I am surprised that this tweak did not work. I would wait for some other answers before trying a reinstall, if the latter is a severe inconvenience.

 

I thought the UI AutomationCore fix was for crashing problems.

Yes. UIAutomationCore.dll helps with general memory errors, which may be expressed by the loss (i.e., blackening or graying) of textures, so it's worth a try, especially since HIGHMEMFIX=1 did not work. What are your computer specifications?

I attatched my computer specs to my signature. Again, I appreciate your responses.