New SDK 13 is available.
Hello:
I have not yet had time to test this today, but I am compelled to inquire:
Has anyone tested use of underscore (aka "underline" or _ ) characters instead of blank spaces in MSFS-2020 SDK v13 paths for files / folders ?
Does MSFS-2020 SDK v13 still require hyphens (aka "dash" or - ) characters used in MSFS-2020 for content names in SDK project input fields ?
CAVEAT: MSFS-2020 SDK v12 'rules' for Package name varies with the intended package contents:
SDK Documentation
docs.flightsimulator.com
"THE PROJECT EDITOR > Creating A New Project > Adding A Package
- Package Name: The name of the package. There are some strict rules on how the package should be named depending on the contents of the package. The list of naming conventions to use is as follows (if a type of package is not mentioned here then you are free to name it as you see fit, but it's recommended to adopt a similar formatting style/structure, for example a visual effects package could be named vfx-<name>):
- Airports: airport-<ICAO>-<airport_name>
- Aircraft: aircraft-<aircraft_name>
- Aircraft Liveries: aircraft-<aircraft_name>-livery-<livery_name>
- Landing Challenges: landingchalenge-<ICAO>-<name>
- Sightseeing Missions: sightseeing-<name>
- Bushtrips: bushtrip-<name>
- Model Libraries: modellib-<name>"
[EDITED]
MSFS SDK v13 (now linked via MFS-2020 Developer Mode menu > Help > SDK Installer), also appears to enforce "strict rules" stated in MSFS SDK v12:
Although the online SDK docs have not 'yet' been updated from v12:
SDK Documentation
docs.flightsimulator.com
...the 'installed-to-disk' MSFS SDK v13 docs have been updated accordingly:
[MSFS SDK 0_13_0_0 install path]\Documentation\html\Developer_Mode\Project_Editor\The_Project_Editor.htm
"THE PROJECT EDITOR > Creating A New Project > Adding A Package
- Package Name: The name of the package. There are some strict rules on how the package should be named depending on the contents of the package. The list of naming conventions to use is as follows (if a type of package is not mentioned here then you are free to name it as you see fit, but it's recommended to adopt a similar formatting style/structure, for example a visual effects package could be named vfx-<name>):
- Airports: airport-<ICAO>-<airport_name>
- Aircraft: aircraft-<aircraft_name>
- Aircraft Liveries: aircraft-<aircraft_name>-livery-<livery_name>
- Landing Challenges: landingchalenge-<ICAO>-<name>
- Sightseeing Missions: sightseeing-<name>
- Bushtrips: bushtrip-<name>
- Model Libraries: modellib-<name>
- Package Title: The package Title is essentially the "display name" for the package that the end-user will see, and is also the display name for the package on the Marketplace.
- Package Creator: The name of the company or user(s) that is creating the package.
- Manufacturer: The name of the manufacturer of the element in the package (this is only required when creating an aircraft package and can be ignored for anything else).
- Content-Type: The type of package that you are making. The available content types are shown below:
Which one of these different content types you select will depend on the package you are creating and the choice should follow these rules:- Unknown - This package type will only be shown when none of the types listed below are selected. This type will not permit you to build a package and a content type must be set before you can (this is done from the Inspector window for the package)
- Aircraft - This package type is only for use when adding a new aircraft model to the simulator, and will require you to use The Aircraft Editor.
- Instruments - This package type permits you to bundle cockpit instruments together for use in several aircraft.
- Scenery - This package type is for scenery elements made using the The Scenery Editor (and is also used for Airports, but you should use the Airport Wizard as explained here instead)
- Livery - This package type is for adding liveries to existing aircraft (see here for more information)
- Mission - This package type is for creating missions using the The Script Editor.
- Misc - This package type is for use for anything that doesn't fit into any of the "main" package types listed above (like Visual Effects, for example)."
FYI: There are many non-MSFS applications / utilities which also do not accept blank spaces in paths for files / folders.
NOTE: We also must NOT include the 'Caret' ( < or > ) characters used to demarcate parameter variables for input strings in MSFS-2020 SDK:
and Make Sure Not to Include the < or > in the name. I have lost count of the number of posts about failing to create a project and they show a project name of <EGCW>-<Welshpool> and wonder why it doesn't work
Indeed, Asobo must also put that additional CAVEAT into the MSFS SDK docs for v13 ...when the "revised edition" is finally posted online.
GaryGB
BTW: Regarding a related topic of path length under Windows 10, do some MSFS users still have issues with Windows 10, 32-Bit long file names ?
Naming Files, Paths, and Namespaces - Win32 apps
All file systems supported by Windows use the concept of files and directories to access data stored on a disk or device.
docs.microsoft.com
PS: Got some "maintenance" to do now ? Here is some more related info on how to deal with VERY long MSFS-2020 project file / folder paths:
How To Fix ‘Filename Is Too Long’ Issue In Windows
If you’ve ever seen this issue, it was probably a simple fix for you. If you’ve seen this error more than twice, then you also know that it can be a complex issue to fix sometimes. Let’s hope you only run into the easy fix variety, but we’ll prepare you for the less easy, guaranteed
helpdeskgeek.com
GaryGB
Last edited: