• 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 2020 SDK NEEDED ADDONS

Is this so:

Reading the "getting started" introduction of the 2020 SDK I noted it requires the folling
in order to generate "scenery and airports in the Sim:

Microsoft Visual Studio 2019
Autodesk 3D Studio Max
Blender2MSFS toolkit,
Support for WebAssembly requires Microsoft Visual Studio 2019 with the Clang tools installed

Did I understood this correctly or is it really "Too Much"

Thank You
 
What are you looking to do with the SDK?

If you want to create new 3D models in 3ds Max, you need it (between 2016-2020 versions). If you want to do this in Blender instead, get the toolkit Vitus posted.

If you want to write C++ gauges you do need VS2019, any edition, with the optional Clang tools.

Everything else can be done through the dev mode / package tool and a text and image editor directly.
 
For scenery the only thing you would need is Blender plus the Blender2MSFS toolkit. Visual Studio is only necessary if you are making C++ gauges.
 
For scenery the only thing you would need is Blender plus the Blender2MSFS toolkit. Visual Studio is only necessary if you are making C++ gauges.
do you have any idea how to get started with a basic scenery setup? Im confused about all the samples included regarding the xml headers needed to get it running

also what happens if I want to make a scenery with mesh edits and tree placements, it seems I need different packages for each? (biome , mesh, airport, scenery)
It really isnt very clear
 
do you have any idea how to get started with a basic scenery setup? Im confused about all the samples included regarding the xml headers needed to get it running

also what happens if I want to make a scenery with mesh edits and tree placements, it seems I need different packages for each? (biome , mesh, airport, scenery)
It really isnt very clear
I am still just figuring alot of this out myself and am by no means an expert but as far as the XML headers those seem to be generated as needed by the inputs you put into the in-sim tools. I don't really think any outside XML is necessary unless you're trying to do some very specific advanced things and even then maybe not. I'm just scratching the surface here but you can build airports and scenery using the in-sim tools (once you figure out how they work as I am still doing). If you want to bring in custom models then you will need a 3d modeling program like Blender. That's 90% of what you will need and use for airports/scenery right now. Aircraft, gauges, and other types of content will likely require more...
 
Top