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

FSX SODE aliased textures fail to show


Resource contributor
I'm trying to figure this one out and was curious if anyone else has ran into a similar issue.

All of my SODE models use aliased textures on another drive. This is to ensure that I don't have hundreds of MBs of textures in the ProgramData folder. The textures all show up fine in P3D v3, P3D v4, and P3D v5. However, they do not show up in FSX:SE. Nothing is different. The alias paths are the same no matter what. The models do display.

I'm not sure if this is something finicky with FSX that I need to handle a little differently on my end or if it's simply an issue with the latest version of SODE. I have had this working in the past, so I'm leaning more towards the latter, which is unfortunate, as it's been quite a while since we've had an update.

Any ideas would be greatly appreciated..