Concerning the "strict naming" of "custom LOD files". This paragraph appears to be inaccurate and/or superceded by code changes* in two ways. First, I recall that it was the naming of the objects in the file that had the strict suffix requirements, not the naming of the files. Second, this requirement seems to have been relaxed, even with ImporterLegacyNaming set to False. Thus the file combinations listed in BUG-8996 are uploaded successfully whether ImporterLegacyNaming is True or False. Neither the file names, nor the object names in those files have the prescribed suffixes. This is presumably because something like the changes requested in that jira, which make life much easier, were made. This part of the documentation was probably written before those changes. {*tests in release viewer 3.8.4 (305119)}.
(Note however that this may change again with recent commits for 8.3.5)
Facebook
Instagram
Twitter
YouTube
Flickr
Uploading a mesh model
in English
Posted
Concerning the "strict naming" of "custom LOD files". This paragraph appears to be inaccurate and/or superceded by code changes* in two ways. First, I recall that it was the naming of the objects in the file that had the strict suffix requirements, not the naming of the files. Second, this requirement seems to have been relaxed, even with ImporterLegacyNaming set to False. Thus the file combinations listed in BUG-8996 are uploaded successfully whether ImporterLegacyNaming is True or False. Neither the file names, nor the object names in those files have the prescribed suffixes. This is presumably because something like the changes requested in that jira, which make life much easier, were made. This part of the documentation was probably written before those changes. {*tests in release viewer 3.8.4 (305119)}.
(Note however that this may change again with recent commits for 8.3.5)