• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Texture problem

K

keatles

Messages
5
Country
newzealand
After finding the problem in the screenshot below (red moire patterns on the canopy and other highly reflective surfaces), I uninstalled nHancer and reset nVidia Control Panel to default settings, RESTARTED and found the same problem.

SNAP_04.jpg


This happens with several models, and persisted with this model even after a full reinstall. I have not altered any of the texture files.

Does anyone have any ideas or solutions?

Thanks

Alan


i7 920 OC to 3.2
Win 7-64 bit, 6GB DDR3
GeForce 285 GTX 1GB
 
I disabled a file in FSX/Texture called GlobalEnvTest.dds and this has fixed the problem - but why? It is a small dds file consisting of alternating red and black vertical lines (256x256).

:confused:
 
Something has corrupted your file then! This is what that file should look like...

This is the image that provides the "scenery reflections" on shiny surfaces. :D

BTW, the T-38A installer does not touch any default files at all!

GlobalEnvTest.dds 8/11/2006 6,145 KB 3072x512 pixels...
 

Attachments

  • GlobalEnvTest.jpg
    GlobalEnvTest.jpg
    101.6 KB · Views: 612
Last edited:
Thank you Bill

I keep a virgin backup of FSX on a separate drive, all read-only, so I can replace corrupted files when found, and sure enough, I now see the corruption. I use FS Repaint v2 to check my repaints while working in Photoshop, and think I might have inadvertently saved some changes to a repaint I was working on (but I am 100% sure I would not have altered that particular texture).

It is most gratifying that experts like yourself are so willing to help amateurs like me. I have found the answers to many of my problems by simply reading your replies to the relevant thread.

You may chalk up another 'kill' on your canopy rail (this time South African Air Force)! :D

Kind regards

Alan
 
Honestly Alan, I get back from the community as much as I give. I'd be a much poorer person if I didn't try to "pay it forward" as much as I can.

Just this morning I finally got the answer to a problem that's been the bane of my existence for the past few months! Granted I got pretty much the same answer from AVSIM as well, but I read it here first... :D

Since I'd also asked the same question in the Prepar3D forums as well, I felt honor bound to post the solution there also, giving proper credit for the assist, and where I'd gotten it. :cool:

Smart thinking regarding keeping a "virgin" copy of FSX elsewhere. I've still got virgin install of FS9 as well, just in case! It's such a trivial matter to copy/paste the entire ..\FSX folder structure to another hard drive, or at least another folder on the same drive. I simply do not understand why everyone doesn't do it! :eek:

Of course in this case since I'm intimately familiar with the T-38A, having worked on the thing for the past eight months, I knew immediately what the problem was. :rotfl:
 
You must log in or register to reply here.
Back
Top