touchdown84

Sorry to bother you again but I seem to have a bug when having a Fast Turn and a normal assignment to the same rotary, that also depends on the order of the entries in the ConfigDatabase_MSFS.xml. This is with AaO 2.07 b12 and MSFS. I made a very simple example to reproduce it with a Fast Turn and a normal assignment where on Fast Turn it should increase the heading bug and on a normal turn it should increase the altitude bug. When in the config xml the normal entry is before the fast entry (like in the xml example below), then on each input both HDG and ALT are increased, even when it's too slow for a Fast Turn. When in the config xml the fast entry is before the normal entry (the reverse of the example xml), then on a slow turn it only increases ALT as expected), and on a Fast Turn it increases HDG (as expected) but also ALT as well (what I would not expect). Maybe it's possible to have a single assignment for normal/fast like with the Long/Short-Click option? Thanks, Jan The example xml-snippet: <buttons> <GlobalHotkey> <downEvent> <Group>Autopilot</Group> <Description>Increments reference altitude</Description> <SimulatorEventName>AP_ALT_VAR_INC</SimulatorEventName> <MinValue>0</MinValue> <MaxValue>0</MaxValue> <ValueToSet>0</ValueToSet> <IsAaoVirtualEvent>false</IsAaoVirtualEvent> <type>SINGLE</type> </downEvent> <repeat>16384</repeat> <repeatFrequency>1</repeatFrequency> <joystickGuid>3e1d4070-447c-11eb-8001-444553540000</joystickGuid> <joystickName>Bravo Throttle Quadrant</joystickName> <joystickButton>12</joystickButton> <joystickPovControl>-1</joystickPovControl> <joystickPovDirection>-1</joystickPovDirection> <midiDeviceId>-1</midiDeviceId> <midiChannel>-1</midiChannel> <midiEvent>-1</midiEvent> <endless>false</endless> <midiEncoder>NONE</midiEncoder> <isSimKey>false</isSimKey> <comboSuppressesEvent>false</comboSuppressesEvent> <comboIsToggle>false</comboIsToggle> <longClick>false</longClick> <longClickTimeoutMs>0</longClickTimeoutMs> <fastTurn>false</fastTurn> <timeoutMs>0</timeoutMs> <assignedKeys /> <vkModifiers /> <vkKeys /> <Action>AP_ALT_VAR_INC</Action> </GlobalHotkey> <GlobalHotkey> <downEvent> <Group>Autopilot</Group> <Description>Increments heading hold reference bug</Description> <SimulatorEventName>HEADING_BUG_INC</SimulatorEventName> <MinValue>0</MinValue> <MaxValue>0</MaxValue> <ValueToSet>0</ValueToSet> <IsAaoVirtualEvent>false</IsAaoVirtualEvent> <type>SINGLE</type> </downEvent> <repeat>16384</repeat> <repeatFrequency>1</repeatFrequency> <joystickGuid>3e1d4070-447c-11eb-8001-444553540000</joystickGuid> <joystickName>Bravo Throttle Quadrant</joystickName> <joystickButton>12</joystickButton> <joystickPovControl>-1</joystickPovControl> <joystickPovDirection>-1</joystickPovDirection> <midiDeviceId>-1</midiDeviceId> <midiChannel>-1</midiChannel> <midiEvent>-1</midiEvent> <endless>false</endless> <midiEncoder>NONE</midiEncoder> <isSimKey>false</isSimKey> <comboSuppressesEvent>false</comboSuppressesEvent> <comboIsToggle>false</comboIsToggle> <longClick>false</longClick> <longClickTimeoutMs>0</longClickTimeoutMs> <fastTurn>true</fastTurn> <timeoutMs>200</timeoutMs> <assignedKeys /> <vkModifiers /> <vkKeys /> <Action>HEADING_BUG_INC</Action> </GlobalHotkey> </buttons>

With MSFS and I was using an automated script to set two lvars with the current heading in degrees so I could display those in the same gauge: (A:PLANE·HEADING·DEGREES·TRUE,·Radians)·rddg·(>L:CUSTOM_HEADING_TRUE,·number)·(A:PLANE·HEADING·DEGREES·MAGNETIC,·Radians)·rddg·(>L:CUSTOM_HEADING_MAGNETIC,·number) But for some reason the issue seems to have resolved itself, I cleaned up my streamdeck profile and removed all buttons/gauges and recreated them again, and now it works and I cannot reproduce it. Had it all day yesterday, so not sure by what it was caused. The second point is still there though, a very simple to reproduce: Create a TextGauge where both variables are set to A:BRAKE PARKING POSITION, bool . When the parking brake is set shows two "1"s, but when not it shows only one "0" and nothing else.

I've tried with plugin version 3.0 and 3.15, same result on both: When I use a TextGauge to display two different(!) LVars it does not work. Both LVars show fine on their own or when I use the same LVar for "Variable 1" and "Variable 2", but when I use two different LVars it does not (display does not update, for neither variable). Also another small glitch I noticed, when "Variable 2" is "0" it shows up as an empty string instead of "0" (with both A: and L: vars). Thanks

I'd like to ask the same question. Using the trim wheel on the Honeycomb Bravo there is no button to hold down for repeat. I can set the trim wheel value (in the -16k/+16 range) via the K:ELEVATOR_TRIM_SET event, but I have not been able to get the current value of the trim wheel with RPN to increase it by, lets say, 100 per tick. What I'm doing at the moment is with RPN 1·(>K:ELEV_TRIM_DN)·1·(>K:ELEV_TRIM_DN)·1·(>K:ELEV_TRIM_DN)·1·(>K:ELEV_TRIM_DN)·1·(>K:ELEV_TRIM_DN) which kinda works but I don't really like it. Anyone knows if there is sim var to read the position of the trim wheel in the same range used to set the event?

This lever can be stuck when state saving was active. To unstuck it you can deactivate state saving and then load a state like "Ready For Takeoff".

Do you have another device attached that is mapped to rudder? I had those rudder problems when I had a gamepad attached that had the rudder axes mapped on the triggers.

I noticed that when using Navigraph that the names for airports where Navigraph is updating the navdata the name of the airport is missing. In the change notes for LNM 2.6.1 beta I see "Updating administrative names like city in airports now. This also corrects missing city and airport names for the Navigraph navdata update.", so maybe this was already addressed but no longer working in LNM 2.6.6? Maybe it's possible that when the airport name is missing it will fallback to either the next lower file in the hierarchy of that airport or to the data from the Navigraph database used in LNM? Thank you

Are you using an (external) FPS limiter? Because then the FPS will be halved when you pop out a window.

The Navigraph cycle, not MSFS.

Install 2013 rev. 3. That bug was fixed in that revision.

Yes. The Honeycomb Alpha has dual-trim-switches like real yokes (like one big switch but split into two halves) and the realistic behavior is that you have to have both circuits closed for the trim to activate. In MSFS itself it works (it will show something like "Button 4 + Button 6" in the assignment). In AAO it's weird that it works on one combo assignment, but not anymore when you add another assignment with different buttons.

Hi, I'm trying the demo of Axis And Ohs with MSFS but I cannot get combo buttons to reliably work. I have those two assignments: But only the one added or updated last (whichever it is) will work, I cannot get them to work both. I also checked the ConfigDatabase_MSFS.xml, and except for the key-down-event and the button numbers the entries are identical.

For my with MS store installation, but using custom paths: Main installation from store (the small installation before the patcher) -> %localappdata%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe As I have custom set drive G: as my Windows store installation drive, in 1. there are mostly only junction points to -> G:\WpSystem\S-1-5-21-201337448-39919387-1056124691-1001\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe Custom directory specified during the patcher installation -> G:\MSFS\Microsoft Flight Simulator That is where most of the sim data is stored, including the Official and Community folders (e.g. G:\MSFS\Microsoft Flight Simulator\Official\OneStore or G:\MSFS\Microsoft Flight Simulator\Community)

Navigraph just released the beta of their MSFS updater, it even adds missing airports like EDDS in (only the runways and navdata though).

I noticed that when I was trying to create a dgml and had to mostly rely on looking up dgmls of other maps to see how it works. No worries, what I did now was create a simple http proxy between the dgml and the OFM page that on the fly resizes the images from 512x512 to 256x256 in the response, that way I have the more user-friendly zoom level of the smaller tiles while not impacting the performance of LNM. http://s000.tinyupload.com/index.php?file_id=00123782338147292791 Proxy implementation in case anyone is curious, dgml needs host/port of the proxy server and 256-tile-setting, otherwise the configuration is same as going directly to the OFM server.

I had a further look and managed to create a map definition that pulls the tiles remotely from the Open Flightmaps page: http://s000.tinyupload.com/?file_id=66428361868327531392 It's basically a composite of two tile layers, one base JPG-tile and a PNG-tile containing the aero/nav data blended on top (as defined by the dgml). That's not an official API, the URL contains the AIRAC and only the last few AIRACs are kept available, so the URL in the dgml needs to be updated regularly and there is no guarantee it will work in the future. It seems only the 512x512 tiles are available this way and only zoom levels 7 to 12 (in contrast to 4 to 11 in the download ZIPs). To have some indication for where you are I copy/pasted the cartolight tile layer until zoom level 6 to the definition. OFM is also only available in parts of Europe, so once you are zoomed in 7+ somewhere else in the world you only see blank space. @albar965 Is it somewhere configurable which tile-zoom-level LNP is using for a current in-application-zoom-level? As the map style changes and increasing information is added with higher zoom it would be nice to composite more detailed tiles already on a lower zoom on the map (for example the low zoom levels contain very little details and only the level 12 tiles contain VRP-flight-paths). If that's not possible a workaround is to change the tileSize width and height in the dgml from 512 to 256 or even 128. That has the effect that even though 512-tiles are loaded from the server the higher level ones are already used one zoom step earlier. Basically each decrease in the configured tile size shifts the zoom level by one. But this also has a performance impact, the program seem a bit more sluggish (probably because the raw data displayed is 4, 16, ... times the size as normally. Edit: Just checked, as expected RAM usage of LNM increases when using a lower tile size configuration: 512x512: 200MiB; 256x256: 500MiB; 128x128: 1400MiB on the same effective zoom level

Well, it's working without a problem with the OpenFlightMaps tiles. You download them as a zip package that already includes all the zoom level folders and the directory/filename structure is already in the OSM-format so no need for custom modes, just OSM-mode in the marble-dgml, serve the tile root from the web server and it works.

Navigraph claims it will support updating MSFS navdata in the future. Otherwise hope that MS/Asobo will get better integrating navdata with there advertised Navblue partnership, but I highly doubt it as there are so many inconsistencies already (long gone NDBs still in the sim, airports missing and navaids/navpoints around those airports not included as well).

How to use OpenFlighMaps tiles in Little Navmap: Run a local web server that serves the tiles Create a marble-compatible, OSM-mode styled structure (dgml, preview, 0/0/0 dummy) and add to the LNM maps directory (data\maps\earth) (see example) (optional) convert all tile PNGs to remove transparency Example map definition: http://s000.tinyupload.com/?file_id=09950983582843687034 (extract into <LNM_root>\data\maps\earth) You can run a simple web server with python, just run python -m http.server 7878 (port must match port defined in dgml) inside a tile root (the directory that contains the 4, 5, 6, ... directories, e.g. slippyTiles_original\original\merged\256\latest\). If the tile root contains more levels than 4-11 adapt the minimumTileLevel and maximumTileLevel in the dgml. If you want to use tiles other than size 256 adapt the tileSize in the dgml. Hint: This changes the detail at zoom level in LNM because OFM has different map styles for different zoom levels. For example if you are using the 512 tiles from OFM you have to zoom in further in LNM until the map style that includes roads is shown. On removing transparency: Little Navmap does not handle tiles cut off with transparency well, when moving the map it will produce heavy ghosting/duplicating in the transparent areas (hard to describe). When you download the tiles from OFM in the settings you can select clipped or non-clipped, clipped has much more transparency because the area is cut out much more detailed, but even the non-clipped variant can have some cut off (transparent) areas in some border tiles on certain zoom levels. I suggest removing all transparency/alpha from the tiles completely, you can do that easily with a command line script using ImageMagick and Powershell. Example script: http://s000.tinyupload.com/?file_id=00282460439308057246 Multiple regions You can serve multiple regions from the same web server, just put the tile roots in sub directories for the regions (e.g. ed, lo) and serve from the directory that contains the sub directories. Then create/clone map definitions for each region and in the dgml adapt path="/" to point the matching sub directory. You can try to serve multiple regions from the same tile set by just copying the tiles together, but there can be differences between the regions for the same tile, mostly in the less detailed, zoomed out levels containing the regional boarders. If you do this make sure to use the non-clipped tiles! Serving from LNM You can also use the inbuilt web server from LNM to serve the tiles, copy your tiles directories to the web root (default <LNM_root>\web), adpat the port and path in the dgml and make sure the LLN web server is running. For me the inbuilt server was a bit slower in serving the tiles.

Would it be possible to filter/blacklist airspaces by name or id? Maybe a (sub)simple string or regex blacklist? There are some airspaces that clutter the map and are largely irrelevant, e.g. in Germany the LANTA restriction zones, which are only active for a few hours at night and are not even drawn on the official German ICAO maps, but they are included in the Navigraph data.

You can use an external frame limiter (be aware this will half your effective FPS when you detach an ingame window), but forcing VSync from the outside (e.g. Nvidia driver) will not work since MFS does not run in Exclusive Fullscreen.

I use Landing Rate Monitor. It collects data for takeoff and landing and also tracks your flight and can sync it with fshub.io for a nice flight journal. No guarantee that it works with MSFS, but as it uses FSUIPC there is a chance it will work with the FSUIPC version for MSFS.

Could also be that they have a separate source for wind turbines. For example wind turbines are also included in the obstacle database for the GTN 750. So probably somewhere is a database that contains the coordinates of wind turbines.

How can it be it includes an outdated runway? I thought we were getting monthly AIRAC updates and e.g. in the Navigraph data there is indeed only one runway at EGPH. Even if the airport scenery is not kept up-to-date, I would expect that all data needed for operation (runways (+runway designators), navaids, procedures) are updated with the monthly cycle! If a runway is removed, just mark it as closed. If a runway is added, just auto-generate a generic runway in the scenery. Better have a broken scenery than a missing runway.

If you already had the database created once (or are using data from navigraph) it is probably just using the existing data from before, you would have to manually trigger a rebuild of the database from the MSFS data files, if that is possible at all.