Double the GNS 530W ... three times the flight plan.

sg_aviation

@Bert-Pieke said in Double the GNS 530W ... three times the flight plan.:

Just to add one observation.. the panel state saving has also been inconsistent for me, so I hardcoded the LVars into the runway.flt file (as I learned from the Carenado planes)

This sounds interesting, since I am also suffering fragile aircraft state saving (support ticket in progress).

Could you advise what needs to be done to hardcode the LVars and share your runway.flt (or the relevant section of it)?

Thanks,

Stefan

Bert Pieke

@sg_aviation What I do, is when the panel loads up incorrectly, save the flight in-game, then select the correct gauges and save the flight in-game a second time.
If I compare the two saved flt files, I can find the variables that matter. For the TBM and A36, I got a similar, but slightly different set of variables. As an example for the TDS GTN in the TBM, I got:
GTN750_INT_HIDDEN=1
XMLVAR_GPS_DISABLED_GTN750=0
AS530_1_HIDDEN=1
KX155B_1_HIDDEN=1
AS530_2_HIDDEN=1
KX155B_2_HIDDEN=0
XMLVAR_GPS_DISABLED_AS530_1=1
TDSGTNXI_INACTIVEVAR=0
var_radio2Mode=1
XMLVAR_GPS_DISABLED_AS530_2=1
TDS_GTN750_VIZ=-1
TDS_GTN650_VIZ=-1
XMLVAR_NEXTGEN_FLIGHTPLAN_ENABLED=0
WT_GNS530_INSTALLED_2=0
These lines then are added to the runway.flt file in the [LocalVars.0] section.

Geoff BJ

@Bert-Pieke I have to confess that the whole LVars thing and such like is quite beyond me. However, I get the gist and what I will say is that many of your observations are very similar to mine. The state saving issue is another problem that is, as mentioned, both fragile and intermittent. In other words, for no apparent reason I start a flight and discover that the GNS is no longer selected, rather it is the GTN for example. In addition, I will find the engine state/condition back to 100% and and previously left as is failures cleared.
In all this is a fantastic plane and the work that Black Square has put into realising it is nothing less than exemplary. However, I very much favour flying with the GNS530 and KX155 combo in particular (not least because I have a FlightSimBuilder GNS panel) and I seem to encounter a very, as you say, 'flaky' experience. This is not the case in most other GNS equipped aircraft. Recently, more times than not any flight plan entered into the world map simply does not arrive in the TBM's GNS and state saving is a little hit and miss.
It's all a bit strange and I do hope the developers involved will see these issues raised and provide a useful update at some point.

Bert Pieke

@Geoff-BJ I will try to put a mod together that can be dropped into the Community folder as an interim fix. As you said, lets hope the developer shows up and provides a proper fix..

Bert Pieke

@Geoff-BJ Try unzipping this into your Community folder and start up the TBM850.
Please report back!
https://www.dropbox.com/scl/fi/9s3mm2pkus72v7a4jmki8/bksq-TBM850-GNS-panel.zip?rlkey=ausrmi019p76ehf1gzdj091j3&dl=0

sg_aviation

@Bert-Pieke Thank you, I'll give it a try next days.

sg_aviation

@Geoff-BJ said in Double the GNS 530W ... three times the flight plan.:

@Bert-Pieke It's all a bit strange and I do hope the developers involved will see these issues raised and provide a useful update at some point.

Just for transparency, these are my observations with the state saving I put in a support ticket to JustFlight:

Aircraft state is not saved after loading a flight on apron, making adjustments, ending flight and quit to desktop (even after waiting 30 mins before ending flight)
Outside Air Temp. unit (°C) is never saved between flights (however cabin Temp unit (°C) is saved)
Last fuel level is not saved
A successfully saved aircraft state (incl. all states & settings in WXR setup manager) is reset to default after:
(a) ending flight, viewing the aircraft in Profile > My Hangar, then closing to desktop (not using "X" as instructed!)
(b) loading a flight starting on the runway

I will cross-reference this thread within the ticket.

Bert Pieke

@sg_aviation Let us know what you find!

Geoff BJ

@Bert-Pieke Thanks for doing this, I have been quite busy this last couple of days but as soon as I get some free time I'll try it out and let you know how it went. :-)

Geoff BJ

@Bert-Pieke Good news! . have tried your interim fix and it appears to work very well indeed - at least flight plans entered into the world map now appear reliably loaded into the GNS, even those with ILS approaches which were previously guaranteed not to appear! Thanks again.

Bert Pieke

@Geoff-BJ Happy it is working for you!

Bert Pieke

@Geoff-BJ said in Double the GNS 530W ... three times the flight plan.:

Recently, more times than not any flight plan entered into the world map simply does not arrive in the TBM's GNS and state saving is a little hit and miss.
It's all a bit strange and I do hope the developers involved will see these issues raised and provide a useful update at some point.

To the developer.. It appears to me that when the state saving does not work correctly, and a second GPS appears, which can be switched off by the switches in the cockpit, the flightplan is no longer available, either to the primary GPS or the VFR map.

Adding the LVARs to the apron and runway.flt files appears to force the loading of the correct configuration, and keeps the flightplan intact..

sg_aviation

@Bert-Pieke Thank you, I have saved a flight and got all the LVars to put into the apron.flt. In addition I found another way to identify the right LVars and settings, especially because some have dependencies between each other:

Enable Developer Mode, in-flight go to Dev Mode -> Tools -> Behaviors -> LocalVariables.

Here you can see the LVars being updated live as you handle the aircraft.

Bert Pieke

@sg_aviation Yes, that is actually a better way to understand which variables change, as you push the buttons... either way, if you find a set that works for you.. you should be OK. :-)

sg_aviation

@Bert-Pieke I now had time to test this in-depth. Tried to add the following LVars to apron.flt:

XMLVAR_YokeHidden1=1
var_CabinTempUnitMode=1
var_InstrumentLightingKnob=100
var_PanelLightingKnob=12
var_ReadingLightSwitch_L=1

Only the first two work. All lighting related settings are working upon starting flight, but disabled after a second. What did I miss? Does it only work upon starting flight battery on?

Another question: How do I start the flight with pilot door open and pilot stairs extended?

Bert Pieke

Sorry, you are asking the wrong guy... I have no idea..

sg_aviation

@Bert-Pieke Roger, no worries!