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

MSFS20 Destination Paths too long?

clements

clements

Messages
124
Country
unitedstates
Is anybody else running into issues with the destinations path being too long when working with/installing textures? If so, how are you solving it?

Things are fine in my development folders, but when I go to install the files into the sim (I am using the Microsoft Store version), I get a message from Windows about the Destination path being too long. The only solution I have found is to shorten the folder names but that results in a pretty cryptic folder structure. It becomes more challenging because the v
 
I can offer no solutions, but I wholeheartedly agree with you on the path lengths as well as those horribly long texture names. The older FSX convention was perfect for the job - from the main microsoft fsx folder it was four clicks down to the texture folder. Example: \Microsoft Flight Simulator X\SimObjects\Airplanes\A2A_PiperJ3_s\texture.swiss

At the moment the maximum path length is 260 characters if memory serves me correctly - hang on, I can check.... yes! go to microsoft power user website The good news is that the 260 limit can be extended - read the page.

Trying the same in msfs: msfs\Community\Eagleskinner-Livery-C172sp-classic_Demonstrator\SimObjects\Airplanes\asobo_c172sp-classic_demonstrator_eagleskkinner\texture.demonstrator -that's seven layers! And those long name formats are dictated in the SDK - in this particular case thats 153 characters plus the ones in the texture sheet name.

But the longer the paths get, the easier it is to snafu things. Make one small typo and you can crash the game. A period instead of an underscore in a texture name will case the game to crash unexpectedly at runtime, just as will an underscore instead of a minus.

One possible "rescue" might be to install the game as close to top level as you can. In my case I am using a one terabyte partition called F:\ that saves the install into C:\Program Files - OK, so it only saves one click and 13 characters but the suggested MS Power user fix above could be the final rescue.

Luck and fun!
 
You must log in or register to reply here.
Back
Top