This are the (new) Support Forums for FSUIPC and related products.

These forums replace the old support forums which have been running for 20+ years. The old forums contain a wealth of information on all FSUIPC products, and are still available (until the end of the year) for read-only here.

At the moment these new forums are quite empty – I will be updating the FAQ section and copying across the User Contributions from the old forums in the next few months.

Please note that you will need to Register and Login to post for support, and also to download attachments. You can view these forums without registering.

Support is also available via Discord. Please use the following invite link to join the FSUIPC Discord server:
https://discord.gg/zjwUTrxmmE

Forums
FSUIPC
FSUIPC7
FSUIPC_WAPI: No lon…
 
Notifications
Clear all

FSUIPC_WAPI: No longer consistently getting lvars

 
Page 1 / 2
Posts: 4
 wcruppel
Registered
Topic starter
December 24, 2025 9:07 pm
(@wcruppel)
Joined: 3 weeks ago

Not sure when this stopped working properly, but with current version of both MSFS 2020 and 2024 and the most recent version of both the WASM package (1.0.7) and the client (from GitHub), I am not longer consistently getting lvars returned by the WASM module. And when I DO get the variables, very often they shortly “go away” i.e. the client loses them.

Are there any known compatibility issues? What can I provide w.r.t. logging to help determine root cause?

Thanks.


Topic Tags
WASM WAPI
5 Replies
Posts: 4
 wcruppel
Registered
Topic starter
December 24, 2025 10:31 pm
(@wcruppel)
Joined: 3 weeks ago

Hmm. I think this issue may only occur when I am using the Developer Camera…! Does that make any sense to anyone?!


Reply
Posts: 113
 FSUIPC
Admin
December 28, 2025 3:21 pm
(@fsuipc)
Joined: 6 months ago

Posted by: @wcruppel
↑

I think this issue may only occur when I am using the Developer Camera…!

What is the ‘Developer Camera’?

It could be related – the Camera State variable is used to determine when the aircraft is loaded and the initial lvar scan should be performed. Do you know the values of this simvar when using the ‘developer camera’? If you let me know what this is, I can check here.

Posted by: @wcruppel
↑

And when I DO get the variables, very often they shortly “go away” i.e. the client loses them.

Not sure how this can happen…

Also, if you have any issues, try setting Debug level logging in both the WASM and the WAPI, and show me both your WASM and WAPI log files.

John


Reply
Posts: 4
 wcruppel
Registered
Topic starter
December 28, 2025 6:25 pm
(@wcruppel)
Joined: 3 weeks ago

What is the ‘Developer Camera’?

Enable Developer Mode in the simulator, then select Camera -> Developer Camera from the developer menu.  This camera allows you to quickly move and pan around pretty much anywhere.

Not sure how this can happen…

I’ve found a consistent repro case. Developer Camera is indeed the problem.

  1. Launch MSFS 2020
  2. Load up an aircraft.
  3. Start your “WASMClient” sample program and connect.
  4. List Lvars. Note LVars are listed in the UI and in FSUIPC_WASMIF.log
  5. Select “Camera -> Developer Camera” from the developer mode.
  6. Note camera mode goes to 18. From FSUIPC_WASM.log: [DEBUG]: Sim data received: cameraState=18
  7. List Lvars from WASMClient again. Note LVars are NOT listed in the UI and we get “[INFO]: We have 000 lvars:” in the log file.
  8. Disable the Developer Camera and wait a few seconds.
  9. Note camera mode goes to 2. From FSUIPC_WASM.log: [DEBUG]: Sim data received: cameraState=2
  10. List Lvars from WASMClient again. Note LVars are listed in the UI and in FSUIPC_WASMIF.log

Thanks.


Reply
Posts: 113
 FSUIPC
Admin
December 28, 2025 6:38 pm
(@fsuipc)
Joined: 6 months ago

Posted by: @wcruppel
↑

Enable Developer Mode in the simulator, then select Camera -> Developer Camera from the developer menu.  This camera allows you to quickly move and pan around pretty much anywhere.

Ok, thats interesting – will take a look.

Posted by: @wcruppel
↑

Developer Camera is indeed the problem.

This doesn’t surprise me, as quite a few things depend on the value of the Camera State simvar. The lvars certainly shouldn’t disappear though. I will check why this is happening and update to correct. It will be low priority though, and may take me a couple of weeks before I get a chance to look into this.

John


Reply
Page 1 / 2
Forum Jump:
  Previous Topic
Next Topic  
Related Topics
Topic Tags:  WASM (3) , WAPI (1) ,