Version: 1.7.35.0
Frequency: Consistently
Severity: High
(Low - quality of life, workflow optimization, rare enough to not impact production, etc…
High - critical but workarounds are available, important feature not working as expected, frequent enough to impact production
Blocker - prevents from working on the project, prevents from releasing the product)
Marketplace package name: miltechsimulations-uk-carrier-strike
Context: If one of the worldscripts is loaded from a .FLT file
Similar MSFS 2020 issue: Works fine there
Bug description:
When adding a mission script to a mission .FLT file like this:
[ObjectFile]
NbFiles=2
File.0=Missions\Miltech\MissionHub\Default\MiltechMission
ReferencePosition.0=N23° 48' 20.5788", W43° 46' 10.9553",+000000.00
ReferenceOrientation.0=0.000,0.000,0.000
File.1=Scenarii\Miltech\Carrier\UK Carrier Strike\Miltech_UK-Carrier-StrikePW
ReferencePosition.1=N23° 48' 20.6434", W43° 46' 11.2395",+000000.00
ReferenceOrientation.1=0.000,0.000,0.000000
The first file Missions\Miltech\MissionHub\Default\MiltechMission will load fine, but the second file Scenarii\Miltech\Carrier\UK Carrier Strike\Miltech_UK-Carrier-StrikePW that contains spaces in the path, will not load.
Repro steps:
Attachments:
Private attachments: Send a PM to @PrivateContent with the link to this topic and the link to download your content