Hopefully, Lockheed can throw some light on what is happening here.
Over the years, I have seen other developers asking about XML gauge size limits, but there is little reponse or info on the subject ?
Problem:
Identical aircraft with lots of XML gauges, in particularly one BIG 2D XML Gauge (900k, with lots of Lvars), cannot establish initial gauge sync, when joining in shared cockpit.
CTD. Widows error message points to FSX.exe & MSvcr80.dll ???,
Planes and their gauges run fine in Free Flight, or in Multiplayer.
(1) Is there a limit on the quantity of data that can be initially exchanged, as the planes check for Gauge matches.
Limit on number of packets to carry this data ( around 86 maybe ??)
(2) Is there a max limit on the number of Lvars ?
(3) Is there a max limit on the length (or significant length of a Lvar)
Assuming there is no XML syntax errors (Gauge runs as expected outside of Shared Cockpit), does anyone have any idea why a 900K XML gauge should be having such issues , just in Shared Cockpit. ?
Geoff
Shared Cockpit CTD: Limit on XML Gauge size ?
Not directly related to your question, so apologies up front, but:
Quote:
Assuming there is no XML syntax errors
You may already know this, but just to be sure, you don't have to assume there are no XML syntax errors. You can have the sim (FSX/Prepar3D) tell you.
In your FSX.cfg (or Prepar3D.cfg) set:
Code:
[PANELS]
GaugeDevDebug=1
to have the sim tell you about XML syntax errors during the XML parsing phase of the aircraft load. This is documented in a rather out of the way place in the SDK, and seems to be something very few people know about or use. I can't imagine doing non-trivial gauge XML work without it.
Quote:
Assuming there is no XML syntax errors
You may already know this, but just to be sure, you don't have to assume there are no XML syntax errors. You can have the sim (FSX/Prepar3D) tell you.
In your FSX.cfg (or Prepar3D.cfg) set:
Code:
[PANELS]
GaugeDevDebug=1
to have the sim tell you about XML syntax errors during the XML parsing phase of the aircraft load. This is documented in a rather out of the way place in the SDK, and seems to be something very few people know about or use. I can't imagine doing non-trivial gauge XML work without it.
adiemus -- Thank you -- Thank you - Thank You 
You even included a link .. Thanks...
XML DEGUB mode identified some errors ..(quite a few typos -- ie mumber instead of number)
Thanks .. got those fixed now .. will be interesting to see how far that goes to fix the Shared Cockpit connection issues !
Geoff
You even included a link .. Thanks...
XML DEGUB mode identified some errors ..(quite a few typos -- ie mumber instead of number)
Thanks .. got those fixed now .. will be interesting to see how far that goes to fix the Shared Cockpit connection issues !
Geoff
