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

Everyone check your MFD (GPS) screens that use P3D V2.1

Hello Developers,

If you have created XML MFD screens using the FS9 GPS data/system in them, check them if they work in Prepar3D V2.1. All of my MFD screens (GPS layers) in P3D V2.1 are now inoperative with P3D 2.1. Something like 5 aircraft product lines.

I wonder if they can be repaired.

sigh...
 
Last edited:
Gday
I fly the Epic with a flight plan Most the time and it flies spot-on in V2.1 but the Mfd shows Time to arrival ect up top of the screen but no map, My Dnav wont even find an ICAO that I enter and the AutoLand by Francois Dore mars 2012 V2.1 Don,t Work no more (It only uses radio alt for its operation ) My auto takeoff which uses similar coding works fine.
I'll keep trying but I ain't no XML guru
 

n4gix

Resource contributor
Bill, something has changed for sure, and not for the better. All of my custom GPS units cannot read or display the GPS database any longer...

What is truly "weird" is that the default fs9gps.cab's g_500.xml script hasn't changed one bit! Yet it works. Go figure! :censored:

At least the G1000 used in the Mooney Acclaim works, but it's using the FSX "Aces" XML syntax, so that doesn't really help here. :confused:
 
Its not good.... Way not good.

I'll have to stop selling planes for V2. Only 1.4. They took quite a while to do an update for V2, so Im sure this will be a long while to do a V2.2. Makes me sick in my stomach. There goes a lot of business...
 

arno

Administrator
Staff member
FSDevConf team
Resource contributor
They took quite a while to do an update for V2, so Im sure this will be a long while to do a V2.2.

It's only 2 and a half month since the release now, not? I think we Microsoft we had to wait much longer for updates normally. But of course when a new bug prevents features of your addon any waiting time is annoying.
 
According to Jessica Bannister, P3D updated or revamped their XML Parser. I guess a lot of Carenado planes no longer have functions either.

sigh..
 
This just posted at Prepar3D by Beau, team member;


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 the 'scrip evaluator' stays, no fixes for broken planes.
 

JB3DG

Resource contributor
Simple solution to all to yo P3D XML problems:

Come over to the dark side and learn C++ :p . You will discover that its actually the light side and XML has been keeping you in the dark :D
 

n4gix

Resource contributor
Jon, with respect... As I just commented in another thread, a certain amount of XML is unavoidable, as it is currently the only option in the modeldef.xml file.

Gauges aside for the moment, a questionable parser that treats non-error in syntax as though they were errors, is a H U G E problem... :yikes:
 
Jon, with respect... As I just commented in another thread, a certain amount of XML is unavoidable, as it is currently the only option in the modeldef.xml file.

Gauges aside for the moment, a questionable parser that treats non-error in syntax as though they were errors, is a H U G E problem... :yikes:


Bill, I massively agree. I see this as a huge mistake on their part. They are trying to blame us now for the OOM's. Well, this didn't happen in 1.4, so what changed?

Naruto-sahn, I don't know if I could learn C++. I am still learning XML and it is still a burden on me. Just learning how to mouse-drag has taken me 3 weeks.
 

JB3DG

Resource contributor
Lol just pulling legs. @n4gix I know but at least one can keep the modeldef.xml as dumb as possible that way.
 
Top