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

Reminder about texturing - FSX SP1 vs FSX SP2

Messages
689
Country
ca-quebec
I recently install SP2 and I note some issues in FSX.

Wrapped texture on vertical tube (ex: lighthouse) in Y axe
SP1 : work.
SP2 : black texture**.

Texture with no alpha saved in DXT1 format
Sp1 : work.
SP2 : black texture**.

** Can cause flickering or misplaced parts on 3D objects.

Edit : the problem was a conflict between two sceneries how have a library with the same name, so the solution I found was to rename one of the library.
 
Last edited:
HI JP

I am not sure I understand the new problems you are seeing but I just made a tube and wrapped a texture on it in the Y-axis with no problems.

If you have a texture with NO alpha channel I thing DXT1 with MipMaps works very well.

If you use an alpha channel DXT5 with MipMaps works well.



“** Can cause flickering or misplaced parts on 3D objects.”

Another very important thing to watch out for is if you tell FSDS that you are going to use a night texture make sure you put in a night texture.

I think from what you are describing this may be your trouble.

H_Farfy
 
Hi Farfy,

I had these issues when I updraded to SP2 and I solved them like I writed. Mip maps are set on the textures.

My video card may be involved, or other settings. It's just a note to help somebody who have the same problems.
 
Hi,
The reminder is a very personal reminder...! The problem seem to be a conflict between two sceneries who have the same BGL library name. For a unknowed raison, the objet of one scenery look for textures in the other scenery...and dont find them. May be a bad link dispatch during the upgrade to SP2.

Solution : rename one of the library, chek if all is right... and edit the first post.
 
This will be guid conflict, rather than an FSX bug.

The library name does not matter but duplicate GUIDs do matter. Therein lies the problem
 
Ok. So if copy-paste a library, do I also copy-paste the GUI of the MDLs in it?

When I reinstalled FSX and installed SP2, I installed also the same sceneries witch where nice before. Why do they dont display nicely after réinstall?

I also note that a missing texture on an object can produce misplacement of parts of it and flickering on objects around it. I dont checked how far the bug produce flickering. Sure it is in the same BGL but is it possible that it cause problem on other BGL, near or far, same scenery or others?
 
Last edited:
Ok. So if copy-paste a library, do I also copy-paste the GUI of the MDLs in it?

I'm not sure I understand your question. You cannot cut/paste the GUIDs from a compiled library, unless you decompile it and process it using a tool like modelconverterX

When I reinstalled FSX and installed SP2, I installed also the same sceneries witch where nice before. Why do they dont display nicely after réinstall?
If the scenery has not been made using the proper material settings and techniques it will "fall apart" under the batching engine in FSX SP2. NO-one should make scenery for FSX RTM or SP1 in my opinion. Everything should be made for the most up-to-date version.

I also note that a missing texture on an object can produce misplacement of parts of it .....
Yes it can.


I dont checked how far the bug produce flickering. Sure it is in the same BGL but is it possible that it cause problem on other BGL, near or far, same scenery or others?

It is more likely that these are faults in the geometry of the objects themselves, now evident under SP2 when the objects are displayed as a batch (this is a guess, obviously)
 
Back
Top