• 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.

If you want your planes to work in V2.1, you'll need to modify them.

Messages
10,158
Country
us-arizona
I just read this post by Beau at Prepar3D;

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
 
I try to look at this on the positive side; as an opportunity to make my stuff more efficient. :scratchch
 
My 2 cents guys. I think the script validation code may also have some bugs reporting errors that are not real. The constant error I get "playing" with the LHC DA40 "gauge script error are you missing a space else{ " does not look like a real error. So their script validation code is constantly writing errors, where there an no errors.
 
Ron, that may explain the remaining two "errors" being reported in my GNS530. See my thread "Adventures in ContentErrorLog..." for specifics.
 
My 2 cents guys. I think the script validation code may also have some bugs reporting errors that are not real. The constant error I get "playing" with the LHC DA40 "gauge script error are you missing a space else{ " does not look like a real error. So their script validation code is constantly writing errors, where there an no errors.

Ron,

Can you post this at the Prepar3D forums, like on this page concerning gauges not working in V2.1;
http://www.prepar3d.com/forum-5/?mingleforumaction=viewtopic&t=5441


It would be interesting to see what is said.
 
Back
Top