AxisAndOhs Demo Version
Please make sure to use the demo version first to find out if your hardware is supported!
The demo version is fully functional, but it will shut down after 20 minutes.
The demo version is fully functional, but it will shut down after 20 minutes.
|
|
| ||||||||||||||||||
The password for the ZIP file is: LORBY
All Lorby-SI products are constantly screened for malware with "Norton Security Premuim". You may still get false positives though, especially the SpursInt trojan or a simple "I don't know you, so you must be bad" by Windows Defender.
Plugins for the Elgato Stream Deck
|
AxisAndOhs has an API based on web technology (XmlHttpRequest or JSONP). This Plugin for the Elgato Stream Deck hardware demonstrates how this API can be utilized for bi-directional communication with the simulator. Not only can you send simulator events to trigger systems or buttons, but you can also read simulator variables and display the results on the StreamDeck.
The following download is a Plugin for the Elgato software with generic buttons. You can assign any simulator event or variable to them, including the MSFS hidden or undocumented ones (AAO v2.04 is required). With a few modest graphics skills, you can make your own rotating or sliding gauges too - Start the sim and AAO (AAO must be run "As Administrator"!) - Make sure that the WebAPI is activated in the AAO "Tools" menu
|
| ||||
Desktop and Web instruments
With AxisAndOhs you have the option to add your own gauges to the Desktop/Web instrument feature.
The AxisAndOhs gauge logic uses a simplified version of the legacy XML format in RPN notation (like FSX did).
The AxisAndOhs gauge logic uses a simplified version of the legacy XML format in RPN notation (like FSX did).
- The place to save your XML gauge is: "\Documents\AxisAndOhs Files\UserGauges\"
- The graphics should be standard PNG 32bit format with transparency.
They go here: "\Documents\AxisAndOhs Files\UserGauges\1024\" - The size of the background should either be 240x240 or 512x512 pixels.
- You can only read simulator variables (A: and P: only), but you cannot write to them
- L: variables are local to AAO gauges and scripts, they are not injected into the simulator
- <GaugeText> is possible, but the text should be simple. AAO doesn't support conditional string formatting (use <Visible> instead)
- Mouse areas work differently than in a real gauge. At present you can only call single events with an assigned value - no scripting
Here are a few examples for MSFS (in other sims they may have limited functionality).
More examples will be added when they become available.
More examples will be added when they become available.
Unpack the ZIP-file to \Documents\LorbyAxisAndOhs Files\UserGauges.
(AxisAndOhs will pick up the gauges automatically when you start it the next time) Lorby MCP: Take a look at the LorbyMCP.xml - it has gauge text, turning things (the dials to the right), buttons to be pushed and LEDs that are there under certain conditions. Lorby Switch Panel: This gauge has the main switches of a GA aircraft. <Visible> tags are used to visually toggle the switch positions.
|
| ||
|
Lorby Status gauge: this one uses <Shift> a lot to move the pointers according to the variables in the simulator. The flaps indicator is split into leading edge (left pointer) and trailing edge flaps (right pointer).
|
|
|
Lorby PFD: this is an approximation of an Airbus PFD, but it works in a generic way - it doesn't tie in with the FMC or the other Airbus specific systems, so it can be used with every aircraft.
|
|
|
The Lorby MFD shows the flight plan that has been loaded into the simulator as your route. It will not react to or understand flight plans that are loaded into a 3rd party FMC/MCDU. With MSFS, make sure to build a full flight plan with departure and arrival, then the route display will be
most complete. On the MFD instrument there are 4 clickspots in the lower quarter of the display. With these clickspots you can change the range of the display or switch between the two variants (route/plan and nav) Furthermore, this instrument reacts to the following simulator events, so you can assign them to joystick buttons with AxisAndOhs: G1000_MFD_PAGE_KNOB_INC, G1000_MFD_PAGE_KNOB_DEC: to switch display type G1000_MFD_ZOOMIN_BUTTON, G1000_MFD_ZOOMOUT_BUTTON: to change display range. |
|
|
This gauge shows jet engine parameters. There are two separate gauges, one for engines 1&2, and another for 3&4
|
|
VRInsight MCP Combo II - PROTOTYPE
|
This is a small program that connects the VRInside MCP Combo II Boeing to the AAO Web API
- FSUIPC or LINDA must NOT be running! - Start the MCP first - Start the sim and AAO (AAO must be run "As Administrator"!) - Make sure that the WebAPI is activated in the AAO "Tools" menu - Start the Bridge program - Add a device with the "+" key, select the corresponding COM port and give it a name - Once created, click on the green LED to connect the device - You can doubleclick the device control to set it to connect automatically. A button press on the MCP will register in the AAO button assignment dialog. That way you can (rather: have to) configure the button actions to your liking in AAO. An initial template for all buttons may be provided at a later date.
Password for the ZIP-File is LORBY
No installer yet, just unpack the archive anywhere you like and doubleclick the exe to start the Bridge program. |
AAO templates to use with the Bridge
| ||||||||||||
