- Messages
- 10,158
- Country

I just read this post by Beau at Prepar3D;
So, it looks like we need to fix our planes. The error logging system is now causing a stack overflow (from what I read here) causing OOM's.
I do not know if I will be modifying all of my planes for 2.1. If models are also going to need internal animation codes redone, the job will be quite huge.
So, Bill Leaming, it was smart of you to start working on fixes yourself on your fleet.
I want to think this is a nightmare, but its not. Its reality.
Bill
Models missions and gauges all use the same scrip evaluator. We added some script validation code to help with scripted actions in mission creation, but it appears that the error messages are being logged internally even when content error reporting and gauge debugging options are not enabled in the cfg. There may have been one or two new checks added as well, but we haven't gone through it with a fine tooth comb just yet. If the xml validates, but some scripts have errors, the system can get in a state where the same error string is created and logged over and over again eventually leading to OOMs. I would suggest turning on gauge debugging in the Prepar3D.cfg and either fix the errors or avoid using any content that pop up alerts until the next patch. We're sorry about the legacy content effected by this. A silver lining may be that add-on developers might be motivated to go back and clean up scrip errors.
Beau Hollis
Rendering System Lead - Prepar3D® Team
So, it looks like we need to fix our planes. The error logging system is now causing a stack overflow (from what I read here) causing OOM's.
I do not know if I will be modifying all of my planes for 2.1. If models are also going to need internal animation codes redone, the job will be quite huge.
So, Bill Leaming, it was smart of you to start working on fixes yourself on your fleet.
I want to think this is a nightmare, but its not. Its reality.
Bill


