-
Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:
- Tag FS2020 specific questions with the MSFS2020 tag.
- Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
- Questions about aircraft design can be posted in the Aircraft design forum
- Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
- Questions about terrain design can be posted in the FS2020 terrain design forum.
- Questions about SimConnect can be posted in the SimConnect forum.
Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.
By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.
MSFS Aircraft creation pipeline
- Thread starter DeDrake
- Start date
- Messages
- 52
Have a look at the file structure of the samples in the SDK doc. Study it. Then have a look at the folders of default aircrafts. Just by looking at how stuff is packed together can be very useful.
Then, i guess the workflow is about the same as any other game. 3D model, texture, config files, flight dynamics.
One tip would be to NOT use the sample aircraft xml, but instead use one from a default aircraft. For some reason, Asobo used the old [Partinfo] stuff in the samples, when really, you should use the premade templates used in all defaut aircrafts.
And to be honest, i dont think the SDK is as poor as you think, specially for the early stages. It is lacking, but not on that side i think (Check section Getting Started and all reealted subsections)
Then, i guess the workflow is about the same as any other game. 3D model, texture, config files, flight dynamics.
One tip would be to NOT use the sample aircraft xml, but instead use one from a default aircraft. For some reason, Asobo used the old [Partinfo] stuff in the samples, when really, you should use the premade templates used in all defaut aircrafts.
And to be honest, i dont think the SDK is as poor as you think, specially for the early stages. It is lacking, but not on that side i think (Check section Getting Started and all reealted subsections)
- Messages
- 44
- Country
-
^ SDK documentation
- Messages
- 10,088
- Country
-
Some people are using the simple airplane sample as a hands on, actual sample. Then you modify it like a template. Copy/paste/rename all files in it. That might take you a day to 3 days to figure out as there are tons of things that need to be carefully edited.
The Cessna 152 model XML's (note, interior and exterior models) will have the 'behavior' animations codes to get you started. Then you need to learn how to find those in the Asobo files Behavior XML's in your simulator.
I use other planes in the sim, like the Cessna 152, 172, SR22 (though its DRM and missing files), etc, etc, to study.
You will need to learn how to create a 'Developer Projects' folder and how to activate your project plane each time you test it in MSFS. It will be located outside of your sim in a projects folder (anywhere) and you click on the Open Project/project xml and your plane shows up in the airplanes folder. You can 'resync' to get it going each time you make changes, but its shakey. Sometimes its best to reboot the sim.
You will need to resynch your project files each time you make changes, even to one file, like your system.cfg or your plane model.
So much... but for now, that should help get you going.
This is the Asobo Behaviors center. Learn to flip through these to find your 'Behaviors' or find them in planes already copy-able in their model XML's. Good luck on that. Its so very complicated on copying out sections from here, from the Behaviors XML's. If you can find it in planes, it is a copy/paste deal. From here, you need to edit them to go into your plane model XML. You'll see.
The Cessna 152 model XML's (note, interior and exterior models) will have the 'behavior' animations codes to get you started. Then you need to learn how to find those in the Asobo files Behavior XML's in your simulator.
I use other planes in the sim, like the Cessna 152, 172, SR22 (though its DRM and missing files), etc, etc, to study.
You will need to learn how to create a 'Developer Projects' folder and how to activate your project plane each time you test it in MSFS. It will be located outside of your sim in a projects folder (anywhere) and you click on the Open Project/project xml and your plane shows up in the airplanes folder. You can 'resync' to get it going each time you make changes, but its shakey. Sometimes its best to reboot the sim.
You will need to resynch your project files each time you make changes, even to one file, like your system.cfg or your plane model.
So much... but for now, that should help get you going.
This is the Asobo Behaviors center. Learn to flip through these to find your 'Behaviors' or find them in planes already copy-able in their model XML's. Good luck on that. Its so very complicated on copying out sections from here, from the Behaviors XML's. If you can find it in planes, it is a copy/paste deal. From here, you need to edit them to go into your plane model XML. You'll see.
Last edited:
- Messages
- 10,088
- Country
-
This is an example of my Trinidad I am working on. The Source files are the plane. The Sync system (compiler) uses these to copy over to the 'Packages' folder system. Time stamp files not logged (anything you change) will be updated over to the Packages folder system.
Your Model file saves and your PSD files, etc, would go in your Art/Texture folder system. Your saved Max or Blender files will go in your Art/Model section. Your saved glTF model file things go in your 'Source' folder structure, which inside will have your plane folder.
Gauges backups was my own, non related.
Your Model file saves and your PSD files, etc, would go in your Art/Texture folder system. Your saved Max or Blender files will go in your Art/Model section. Your saved glTF model file things go in your 'Source' folder structure, which inside will have your plane folder.
Gauges backups was my own, non related.
- Messages
- 10,088
- Country
-
Great examples;
Simple Aircraft in the SDK
DA62 in the SDK, also the Max version to see how they do animations, names, Dummy's, etc, etc. Materials. Comp textures.
If you have MCX, you can open the glTF's of non-DRM planes, like the Cessna 208. That plane is an awesome example for studying. SO much in it.
Simple Aircraft in the SDK
DA62 in the SDK, also the Max version to see how they do animations, names, Dummy's, etc, etc. Materials. Comp textures.
If you have MCX, you can open the glTF's of non-DRM planes, like the Cessna 208. That plane is an awesome example for studying. SO much in it.