Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

MSFS 2024 variable for DTK?

Featured Replies

In MSFS 2020 I made a button for my Streamdeck that synced the autopilot HDG with the flightplan DTK for the next waypoint. I did it with the following script:

(L:WT_LNavData_DTK_Mag, Degrees) (>A:AUTOPILOT HEADING LOCK DIR, Degrees)

The first variable, L:WT_LNavData_DTK_Mag, does not seem to exist anymore under MSFS 2024. Any idea how to look this up now? I'm not finding any information online yet, nor anything that matches under DevMode, Behaviors, and Variables. I found the previous variable from this website, but haven't found an equivalent resource for 2024 yet: https://microsoft.github.io/msfs-avionics-mirror/docs/framework/enums/LNavDataVars/ 

  • Author

One of the WT team members in the Working Title group on Discord said they stopped writing those LVars in part due to performance reasons. They plan to publish updated documentation soon, but all those LNAV LVars were removed in the latest version of the avionics SDK. He gave me a substitute to use instead that is working great though:

(A:GPS WP DESIRED TRACK, Degrees) (>A:AUTOPILOT HEADING LOCK DIR, Degrees)

 

  • Commercial Member
15 hours ago, aaronpriest said:

they stopped writing those LVars in part due to performance reasons.

Interesting. I was wondering about that. Since the beginning of MSFS so many developers were implementing LVar logic. And MSFS apparently holds all of them in the program memory all the time - ALL LVARS, not only those that the current aircraft needs. Plus, the LVar logic is always associated with some form of polling mechanism = something has to watch the LVars for them changing value, so it can react. LVars are not events, they don't do anything - they only hold a numerical value. And that is always sub-optimal, because there is always a delay between you changing an LVar value, and that change being registered in the aircraft logic.

Edited by Lorby_SI

LORBY-SI

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.