Missing LVAR after 3066 Lvars loaded (since SU11)

[John Dowson]

2 hours ago, Clamb said:

Apparently the iniBuilds A310 uses more than 3066 LVARs.

Ok, yes it does. I will update to allow more lvars by default in the next release, up to 4088. I will also look into adding a new WASM (and maybe WAPI) ini parameter so that the max number of lvats available can be set by the user, up to a hard-coded maximum of 9198 - but maybe not in the next release, I will see...

2 hours ago, Clamb said:

I also noticed that PMDG does not create all LVARs when the aircraft is loaded, but some are only created when they are not 0 anymore.
For example, all EGPWS Callout Lvars in the PMDG 737 only come into existence when the event is trigger. Like "egpws_baba" for the bank angle voice alert.
Of course, this is not a bug by your WASM module, but has to be taken into account when working with them.

Yes, some lvars are created only once used for the first time. currently you have to issue a reload command when this happens, so that the lvar scan is done again. I have been thinking of doing this automatically in the WASM, so that new lvars are automatically pushed to clients (including FSUIPC) when they are detected. I will look into this as well.

John

[John Dowson]

5 hours ago, Clamb said:

Apparently the iniBuilds A310 uses more than 3066 LVARs.

Yes - it has 4684 lvars on first load - maybe more are created later...

I have updated now to handle up to 9198 lvars. I don't think there is a need for an ini parameter to specify the number of lvars used.
I will release this as a beta in a few days (next week sometime) - I will post here again when available.

John

[Clamb]

22 hours ago, John Dowson said:

I have updated now to handle up to 9198 lvars. I don't think there is a need for an ini parameter to specify the number of lvars used.

Excellent, thanks. That should hopefully be enough.

On 2/8/2023 at 1:13 PM, John Dowson said:

Yes, some lvars are created only once used for the first time. currently you have to issue a reload command when this happens, so that the lvar scan is done again. I have been thinking of doing this automatically in the WASM, so that new lvars are automatically pushed to clients (including FSUIPC) when they are detected. I will look into this as well.

I have worked around this by creating the LVARs I want to monitor, but don't exist yet, myself. Works just fine.

 

[michel78320]

On 2/8/2023 at 4:21 PM, John Dowson said:

I have updated now to handle up to 9198 lvars. I don't think there is a need for an ini parameter to specify the number of lvars used.
I will release this as a beta in a few days (next week sometime) - I will post here again when available.

John

Excellent news. Thank you very much for that.

[John Dowson]

Now available: 

 

John

[Fragtality]

Hey, just saw this in the SU12 Beta Release Notes under SimConnect:

Quote

It is now possible to request Lvar using AddDataToDefinition

Maybe that enables another way of accessing L-Vars in the future? 

[John Dowson]

7 minutes ago, Fragtality said:

Maybe that enables another way of accessing L-Vars in the future? 

Yes, I have also seen this. I need to think about whether to use this or not....

Btw, I have just released FSUIPC7 v7.3.17 (as well as WASM/WAPI v1.0.0), which has support for > 10,000 lvars, as well as automatic scanning for new lvars (i.e. no need to issue a WASM reload command anymore).

John

[Fragtality]

Yeah, read it - great, thanks for that 🙂

Greatly reduces the likelyhood that my lua-scripts get broken 😄 

[NovemberUniform]

On 2/25/2023 at 4:33 PM, John Dowson said:

Btw, I have just released FSUIPC7 v7.3.17 (as well as WASM/WAPI v1.0.0), which has support for > 10,000 lvars, as well as automatic scanning for new lvars (i.e. no need to issue a WASM reload command anymore).

Thanks John! This is awesome. One problem less. 

[John Dowson]

Still a few issues in that version though - please try the latest beta, v7.3.18c (and WASM 1.01, WAPI 1.02), available here:

 

John