lvar_support
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Last revision Both sides next revision | ||
|
lvar_support [2015/10/26 01:28] c0nnex [Simulator integration] |
lvar_support [2015/10/26 01:28] c0nnex [SPAD.neXt integration] |
||
|---|---|---|---|
| Line 33: | Line 33: | ||
| ==== SPAD.neXt integration ==== | ==== SPAD.neXt integration ==== | ||
| - | {{:lvar_example_bombardier_fsx.png?nolink&200 |}} | + | {{:lvar_example_bombardier_fsx.png?200 |}} |
| To be able to use LVAR with SPAD.neXt SimConnect has to be enabled, as SPAD.neXt talks to the bridge using SimConnect, which allows to access the LVAR even if you have a networked installation. | To be able to use LVAR with SPAD.neXt SimConnect has to be enabled, as SPAD.neXt talks to the bridge using SimConnect, which allows to access the LVAR even if you have a networked installation. | ||
| If everything is fine and the loaded aircraft has LVAR defined, you will find those when configuring an event within the Simulation Data browser in the subtree LVAR.((Depending on the aircraft the names of the LVAR are more or less meaningful. SPAD.neXt has no influence on the naming.)) | If everything is fine and the loaded aircraft has LVAR defined, you will find those when configuring an event within the Simulation Data browser in the subtree LVAR.((Depending on the aircraft the names of the LVAR are more or less meaningful. SPAD.neXt has no influence on the naming.)) | ||
lvar_support.txt ยท Last modified: 2016/02/24 13:34 by c0nnex
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 3.0 Unported
