Version: *1.5.19
Frequency: Consistently*
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
Bug description:
Having
nav_proportional_control = 20.00
nav_integrator_control = 2.00
nav_derivative_control = 5.00
nav_integrator_boundary = 1.00
nav_derivative_boundary = 10.00
from an older 2020 aircraft will cause 2024 to CTD when you try to reuse the systems.cfg
I see that 2020 SDK has updated to names with _ex1 and 2024 SDK also
The sim will build the aircraft project - however there are 5 fatal errors that are not flaged to fail the sim build.
Repro steps:
Attachments:
Private attachments: Send a PM to @PrivateContent with the link to this topic and the link to download your content
User error - missing model.xml files causes CTD. why no red error on build - package Build.
Had to remove PackageBuild filter to show missing model.xml error
However the red errors still stand
Should this “RED” error cause a build not to work - ie. fail?
Hello @DA40CGDFQ
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.
Regards,
Sylvain
Correct it was all my mistake.
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.
Here is a link to the project files.
Delete the two model.xml files
SocataSt10_exterior.xml
SocataSt10_interior.xml
link
Socata-ST10-2024.zip
EDIT: the systems.cfg file has corrected nav_proportial_control_ex1 parameters - you may want to change to test the bad parameters issue.
1 Like
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.
Just tested on SU3 beta 1.5.19.0 but in my case, it just spawns the aircraft with no model displayed, which is the expected behavior.
If you can consistently trigger a CTD this way, a dump file will definitely help us.
Regards,
Sylvain
1 Like
Sorry, I can’t seem to generate any dump file. That seems to be because it really does not CTD. What happens is that it hangs.
It usually will zoom into the airport where I select. But it just sits at 60,000 feet over the earth.
I assume CTD because this is what happens to me on other CTDs.
The sim is still responsive to ESC key and will go back.
I test at CYCE.
EDIT: note missing group category in console log.
Taken too much of your time here on this. Just a user error. We can close this issue.
That’s ok.
Infinite loading is something I’d rather avoid if we can have a better error handling, so I’ll have this looked at anyway.
Regards,
Sylvain
1 Like
