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: if applicable
Context: What package? When editing or mounted from Community? In main menu or in flight? etc…
Similar MSFS 2020 issue: insert url here if applicable
So the crash has nothing to do with the systems.cfg parameters you mentioned?
I agree these CFGCompiler validations should be warning instead of errors if they do not fail the package build and this will be changed.
How did you see the error about missing xml file if that’s causing a CTD? CTD does not occur right away?
What is the error showing exactly?
My assumption is that these are ModelBehavior errors, which, if you are not using compiled behaviors, are evaluated when the aircraft is loaded.
In all circumstances, this should not trigger a CTD.
Please provide us with a dump file or a repro package so we can investigate this crash.
While I was testing the ASOBO Blender exporter for 4.2 I was removing as much info as possible to test the exporter. However, I removed the [model].xml files.
When I went on to do other work I tried to build my test project and all this is when I found the red error that said nav_proportional_control was an incorrect parameter. I then assumed it was this. My bad for jumping the gun and reporting it.
I updated my bug report to say “user-error”
The CTD was after building the project and trying to do a free flight. With no [model].xml the sim CTDs.
I found out that it was a missing [model].xml by removing the filter for PackageBuild and looking at ALL the red errors. This is where I found the report that there was a missing [model].xml.
[face_palm]
my mistake
I believe that any “silly” errors like missing [model].xml - or any other critical files need to be shown in the PackageBuild filter.
A lot of errors cannot be detected before runtime.
For this particular case, this will be covered if you move to compiled behaviors.
A lot of runtime errors will become build errors and will prevent you from building the package.
These parameters are flagged as obsolete: CFG Parameter Index
The PID parameters from the ai.cfg STICKANDRUDDER section are used instead.
This topic has been automatically closed after 60 days of inactivity since it was marked as fixed.
If there is important new information about this same report, you can use the “Request reopen” button below to ask the moderation team to review it again.
For other issues or broader discussion, please open a new topic in the appropriate category.
