If this has been addressed in the huge thread, please forgive me for asking again, but I didn't see it. 

 

The GPS units in all of my Carenado planes are stuck on a range of "0 ft" and they can't expand the range. The Avidyne unit in the B1900 is likewise crippled. I know people have discussed this on the LM forums, but I didn't see any solution offered. Does anyone know of some way to get them to work properly?

 

Thanks.

No one?

http://forum.avsim.net/topic/434856-caravan-ex-in-p3dv21/

Also here:

 

http://forum.avsim.net/topic/434749-gps-broken-after-p3d-21-patch/

Thanks guys. I'm sorry to see that there isn't a solution yet.

The "problem" is that L-M tightened up the XML parsing engine such that it's less tolerant of what have been up until now very minor 'errors' in syntax. This is a problem that Carenado will have to solve...

...just as I will have to rework my own custom GPS projects that are currently inop in P3Dv2.1... :blush:

Well, it is certainly a "problem" if their patch makes planes that are marketed to work with their product not work! I would have thought that someone would have caught this during testing and at least given us a "heads up"  when the patch was released. 

 

Not assigning blame. Just stating the obvious.

Concerning the "disagree" from RoboRay, what exactly could you possibly disagree with in that post? 

 

I have $150 worth of planes marketed for it that now don't work. How dare I point that out, or hope that someone at either of the companies involved might have noticed? I didn't even blame anybody for it.

 

Or is it somehow my own fault that the planes don't work? Or should I just keep quite and hope they fix it? Or should I not even hope that they fix it, but be OK if they don't? Let me know!

Also other third party GPS units (Simflyer, Friendly Panels) that functioned in P3D v2.0 exhibit that same behavior in 2.1. I have substituted the default Garmin 500 in the meantime, which works OK. FYI...

Have posted this elsewhere, but seems appropriate here:  the Milviz default Garmin 430 and 530 units in their C310R and B55 also are not fully functional in version 2.1, though they worked fine in 2.0.  If Bill n4gix is correct that this is due to LM's tightening of the xml parsing engine so that it now detects syntax errors that were not previously detected (presumably an upgrade) then it is not so easy to say that this is an LM problem to correct rather than that the developers should upgrade their own products to correct their errors.