March 2nd, 2023 Development Update

Asobo

• SimConnect
  • We fixed a crash while inspecting Data Definition with no unit or a wrong unit entry (using SimConnect Inspector).
• Aircraft Editor
  • We updated the aircraft template names.
  • We added default and min value for static_compression of contact points to avoid division by 0 later.
  • We added new Glider parameters.
  • We fixed a data loss when there is optional data in struct added in the Aircraft Editor.
  • We fixed a crash caused by the Aircraft wizard. Now the aircraft .cfg files are automatically saved when opening the Aircraft Editor after using the Wizard.
  • We updated template aircraft contact points.
  • We fixed the parsing of n1_and_mach_on_thrust_table in the Aircraft Editor, which would break the A320 and probably other jet aircraft.

Working Title / MSFS Avionics Framework

• MSFS Avionics Framework
  • We are still working to finalize the framework update for AAU_01 content, including plug-in documentation – stay tuned.
  • Remember you can find the MSFS Avionics Framework on GitHub here.
  • Upcoming framework updates:
    • Expanded ADC (Air Data Computer) SDK data publisher to include air density. (AAU_02)
    • Expanded NumberUnit/UnitType utility to support air density units and conversions. (AAU_02)
    • Expanded VNAV Path Calculator to support idle descent prediction and planning. (AAU_02)
    • Continued work on a framework autopilot update adding more configurability to the directors and standardizing common logic. (AAU_02)

• Avionics Framework Feature Highlight: Components and Refs
  • What are Components:
    • At the core of the Avionics Framework is the DisplayComponent class. Aptly named, DisplayComponents are used to render content to the actual display on your instrument. Within the framework, any time you want to actually render something on the display you use a DisplayComponent. DisplayComponents are essentially smart divs and are incredibly flexible; you can use as many as you like and they can be nested.
  • What are Refs:
    • Refs are simply code references to these display components; if you create a DisplayComponent and assign it a Ref, then you can reference that display component from outside the component (by passing the ref wherever it is needed) and, thus, be able to update, show, hide or otherwise manipulate your DisplayComponent from anywhere on your instrument.
  • Why use Components and Refs:
    • DisplayComponents and their Refs simplify the exercise of creating and manipulating rendered content on the instrument – by using refs, your logic code can reach inside the component and change anything about it, such as CSS styles or classes, rendered text, rendered SVGs and more. You can also pass a DisplayComponent a Subject or have your component subscribe to events from the Event Bus, in order to update itself based on one or more input data types. DisplayComponents are very flexible – they can be “smart” and contain their own logic and event subscriptions to be entirely autonomous, or they can be “dumb” and rely exclusively on an outside logic/controller class to reach into the component to make changes when appropriate – they are suitably flexible to support a variety of different development styles and purposes.
  • Simple example:
    • Imagine you wanted to display an altimeter with a moving (or scrolling) altitude bar as is common on many glass PFDs. You would create your DisplayComponent and assign it a ref. Within your DisplayComponent, you would use the render method to define the HTML/DIV structure of the component, as well as assign CSS classes to your HTML. You might then create your update methods inside the component – those that translate the scrolling altimeter bar (via CSS) and change the displayed altitude numbers by updating the displayed digits (text content). Then, within your component, you can create two ConsumerSubjects (discussed last week) – one for the altimeter setting and one for the indicated altitude, and tie those subjects to their respective EventBus events so they stay constantly updated. Now that your display component has all the data it needs to render what you want it to render, we just need to create a subscription inside the DisplayComponent to those two ConsumerSubjects, and when either of these values change, you call your update method and the component will update itself.

• Read more about Components and Refs here.

 

Community Video

You can submit your screenshot via Twitter with #MSFSchallenge or the Weekly Forum Post! This week’s screenshot challenge: Color Series – Purple

This past week’s Screenshot Challenge was “New Zealand“

Screenshot by YusufWardana (Forum)

Screenshot by vp_sim (Twitter)

Screenshot by ukaka5656 (Twitter)

Screenshot by tsujiKa_air (Twitter)

Screenshot by PerkyWhisper578 (Forum)

Screenshot by MihamaBlend (Twitter)

Screenshot by mbraortns (Forum)

Screenshot by JohnStarp (Forum)

Screenshot by dlh747 (Forum)

Screenshot by AlphaSierra5534 (Forum)

 

---

NEXT DEVELOPMENT BLOG UPDATE – March 9th, 2023

Sincerely,

Microsoft Flight Simulator Team