LVar Set by Checklist Copilot Action Getting Reverted Back/Overwritten by Aircraft Itself

[MSFS 2020] Questions & Community Discussions Aircraft
1

Hey guys, I’m currently working on an improved checklist for the Milviz 310R
because the original checklist that came with the 310R was broken and can’t be
used in Assisted Checklist mode. During working on the checklist I’ve
encountered a really weird issue where one particular LVar will be revert
back to its original value after the checklist copilot action altered that
LVar’s value. The affected LVar is for the Control Lock and it’s a boolean
which 1 = Control Lock Installed/Visible and 0 = Control Lock
Removed/Invisible This Control Lock can be removed by clicking on it or via
the EFB tablet and can only be installed via the EFB Tablet.

2010×1295 498 KB
The issue is that when I want
the checklist’s copilot action to either change the LVar value from 1 to 0
(Remove the Control Lock) or from 0 to 1 (Install the Control Lock), _ the
change will be performed_ ** _ _but the value will immediately revert back
to its original value.__** My first checklist item is to verify if the control
lock is removed and remove it if it’s not. I used the normal code that anyone
can think of to program this part and here it is:

        Code="0 (>L:C310_Control_Lock)**"/>

But as I mentioned above, changing the LVar to 0 (Remove and Invisiable)
will only work for a split second then it’ll be reverted back to 1
(Installed and Visible). Then I turned to the interior.xml of the Milviz
310R and found the code of the Control Lock item. I borrowed the code for left
click interaction which will remove the Control Lock (Bolded text below).
Here’s the entire code for this Control Lock in the interior.xml:

    C310_Control_Lock
    
        
             **-1 (>L:C310_Control_Lock,bool)**
        
        Control Lock Visibility
    



    C310_Control_Lock
    
        (L:C310_Control_Lock,bool)

With that weird -1 (>L:C310_Control_Lock,bool) code, I’ve managed to
successfully make the Control Lock go away for good with the checklist copilot
action!

        Code="-1 (>L:C310_Control_Lock)**"/>

I’ve used the BehaviourDebug window to monitor the value of this LVar and
similar to before, the value got changed briefly into -1. But then, unlike
before, the value went to 0 (Removed and Invisible) and stayed there.
It didn’t revert back to 1 (Installed and Visible) which is the original
state!

1090×842 1020 KB
With that, I thought I
can also make the installation of the Control Lock stick as well but
unfortunatly, it’s not working. Due to there’s no existing codes in the
interior.xml file for installation of the Control Lock for me to copy, I can
only use the only code that I can think of to set the LVar to 1 (Installed
and Visible) in order to install the Control Lock.

        Code="1 (>L:C310_Control_Lock)**"/>

Unfortunetly, this is not working. The LVar can be set to 1 (Installed and
Visible) by the copilot action but it’ll be immediately revert back to 0
(Removed and Invisible). I’ve talked with Matt from WTT and he suggested
that maybe it’s the EFB tablet’s JS codes that’s setting the LVar every frame
based on the state stored in the EFB. I’ve also posted this issue to the
Milviz Discord but at this moment, no respond yet. I would like to thank you
all for your time to read my post and please, let me know your thoughts!
Please let me know if there’s a way to make the LVar change stick or how to
troubleshoot the issue and find exactly what’s the reason of the LVar keeps
reverting back on itself! Regards, Meo

2

Hi Meo. You should have received some answers by now if you’ve brought this to
our attention elsewhere, but I thought I’d reply here as well to give some
insight as to what is likely going on. Much of the 310R is controlled via WASM
code, including many, many items that have their state saved via individual
tail numbers. It’s very likely that there’s a conflict between the lvar you
are trying to set and the code wanting to revert it. We’re investigating the
issue of the checklists breaking and will likely provide an update for the
aircraft at some point down the road. However, it’s very likely that the in-
game checklist will be for reference only and not include any auto-complete
features.

3

Hey man, thank you for the answer! I’ve finally managed to figure this one out
as well as the pitot cover, engine cover, etc. After digging through all the
LVars in the game and checking them one by one while installing and removing
the control lock, I’ve managed to find another LVar that’s also related to the
control lock. It turns out that there’s another set of LVars also being
changed while these self-reverting actions take place: It’s called
L:C310_TAB_XXXX. So I’ve managed to make the control lock installation
stick with these 2 commands:

And for the checklist with auto-complete features, I’m actually almost
done with the pre-flight checks and the shutdown procedure. I can try to
finish it all and I’m happy to share that with you guys to implement it to the
aircraft instead of posting it to flightsim.to.
Everyone deserves a good assisted checklist. I’ve also identified some small
issues like some switches missing PART_ID (i.e. C310_Nav_Selector,
DEICE_Switch_PitotHeat), and orders of the LEFT_SINGLE_CODE were reversed for
some of the circuit breakers (i.e. CB_PITOT_HEAT, CB_FLAP_MOTOR ). And the
tooltip is not changing when you pop the Left Alternator breaker in and out.
It’ll say “Closed” forever due to one line of animation code missing from the
LEFT_SINGLE_CODE. As I keep discovering these little issues and fixing them,
can you share with me a good way to communicate and share these bugs with you?
Can I DM you with my current findings? The 310R is a fantastic plane and I
just can’t wait for your PC-12!

4

You can absolutely DM me. We’re not doing a PC-12, that must be someone else!

5

It doesn’t look like we can DM on here, but can I point you towards our public
discord channel? You can certainly send me a message once you’ve joined on
there: https://discord.gg/WMK8qupwX9

6

That was awkward lol. I meant for PC-6. Haven’t bought it but I’ll definitely
get one real soon. (As soon as I finish up the 310R’s checklist lol) I’ll DM
you shortly!

7

Hey man I’ve just sent you a DM. It’s the same name Meo Chan and the same
profile pic as here.