**Bug description: **
In our 3ds Max files, the maps are linked to a shared location on our server. Some are part of our internal texture library, and others come from C:\MSFS 2024 SDK\SharedAssets\texture.
When we export the project and build it in-game, the SDK reports a lot of errors because it expects all textures to be inside the PackageSources folder. In practice it doesn’t really matter, since the textures are resolved through the project structure and fallback system. But the SDK still produces a ton of warnings.
We aren’t using the 3dsmax Set Projects feature.
Is there any way to skip this verification step, or is it something the SDK absolutely requires?
Repro steps: In 3ds Max, link your maps to a folder outside PackageSources, then export and build. Check the log console for yellow warnings.
I preferred the old behavior where textures in separate folders didn’t trigger issues, but I understand this may be a constraint on your side.
The problem now is that validator warnings will still show up for generic Asobo textures used by creators, even with proper fallbacks.
“Ignore validator errors” works as a workaround, but there’s a risk of missing important errors maybe?
This topic has been automatically closed after 60 days of inactivity since it was marked as by-design.
If there is important new information about this same report, you can use the “Request reopen” button below to ask the moderation team to review it again.
For other issues or broader discussion, please open a new topic in the appropriate category.
