MSFS20 Texture and Material Names

[rhumbaflappy]

I've read some about the idea that texture or material names have a strict size limit or cannot contain spaces. Attached is a project that contains an absurdly long set of material and texture characters for their names (and spaces).

    "materials" : [
        {
            "doubleSided" : true,
            "name" : "MyVeryLongMaterialName which is probably NOT allowed In MSFS and includes spaces between the words",
            "pbrMetallicRoughness" : {
                "baseColorTexture" : {
                    "index" : 0
                },
                "metallicFactor" : 0,
                "roughnessFactor" : 0.5
            }
        }
    ]

and later...

    "textures" : [
        {
            "sampler" : 0,
            "source" : 0
        }
    ],
    "images" : [
        {
            "mimeType" : "image/png",
            "name" : "american-flag-large and includes spaces as well and is probably not allowed in MSFS",
            "uri" : "american-flag-large and includes spaces as well and is probably not allowed in MSFS.png"
        }
    ]

It compiles and shows fine in MSFS.

 

[Peter Hornfeck]

Thanks, that would be great.

 

[=rk=]

I've read some about the idea that texture or material names have a strict size limit or cannot contain spaces.

Well just yesterday I downloaded Alpha India Groups AI software and first time starting, it raised a popup that informed long file names had not been enabled on my machine and interrogated would I like it to edit the registry to allow them. I clicked yes and just now Googled it, apparently it's a thing:

Enabling Windows Long Path (Windows 10 - 1803 build) - Filr 4.3: Desktop Application Guide for Windows

www.microfocus.com

 

[GaryGB]

Hi Dick:

Considering the dilemma MSFS 2020 users may encounter with input strings for file names etc:

https://www.fsdeveloper.com/forum/t...he-object-list-please-help.452948/post-886683


...use of double quote (") escape characters in Windows 10 long paths may (also ?) be a work-around without RegEdit or GpEdit:

Long paths with spaces require quotation marks - Windows Server

Solves an issue that occurs when you specify long filenames or paths with spaces.

docs.microsoft.com

Quotes, Escape Characters, Delimiters - Windows CMD

ss64.com

How to Escape Spaces in File Paths on the Windows Command Line

Want to type spaces in file paths on the Windows command line? Here's how. (Did you know you can use the caret character ( ^ ) to escape spaces in Command Prompt?)

www.howtogeek.com

Interestingly, this may also prove useful in scenarios where UNC paths are involved:

Long filenames - Windows CMD

ss64.com

"There is an alternative for accessing very long filenames: for file I/O, the "\\?\" prefix to a path string tells the Windows APIs to disable all string parsing and to send the string that follows it straight to the file system.

dir "\\?\UNC\Server64\Teams\Personnel\some - very - long - file - name.txt"

Because it turns off automatic expansion of the path string, the "\\?\" prefix also allows the use of ".." and "." in the path names, which can be useful if you are attempting to perform operations on a file with these otherwise reserved relative path specifiers as part of the fully qualified path. This syntax can be used in both CMD and PowerShell."


Some related query results:

https://www.google.com/search?q=Win...hUKEwjsy9fWx7byAhWBbs0KHVIvANIQ4dUDCA0&uact=5

GaryGB