What You could do as well is reduce the graphic quality to a small size an to lowest quality in all options. This will reduce startup time.
There is also an option how to build your model outside the MSFS using cmd.exe. I'll drop you the setting if you are interested.
If you have small changes that you can do directly in the xml file, you don't have to do this in MSFS.
Switching on are of taxiway lights or reducing the size of this or that or changing COM data, all this can be done in the xml file.
Hello:
It would be helpful to the FS Development Community to read more about these options as sub-topics arising from this thread.
I'm thinking many of use here might benefit from identifying how to optimize MSFS-2020 performance in "Developer Mode" by setting up a custom 'configuration profile' to be used when not actually flying.
Perhaps in another thread we might discuss ways to establish optimized settings that can be toggled on / off in MSFS-2020 "Developer Mode" that make use of the sim more of a manageable experience even on older computer builds ?
Perhaps via a GUI utility or CMD mode batch files, we can toggle a MSFS-2020 "Developer Mode" performance profile on / off ?
Might this be done by dynamic edits / saves of the 'active' MSFS-2020
UserCfg.OPT and
ex: SimConnect and/or a custom utility ?
I'm thinking that, although obviously we would all do well to see this new sim as
THE reason for an immediate hardware upgrade, some of us here may not plan to put that into our budgets until some time later in this new year (...at the earliest).
FYI: I am personally still in the process of fine-tuning a costly hardware upgrade which was prompted mostly by how much of a '
stuttering mess' MSFS-2020 became when in "Developer Mode", even though I was otherwise able to achieve a relatively satisfactory run time rendering performance if I was (only) flying on my prior moderately older computer build.
GaryGB