This week, Microsoft Flight Simulator’s development update was rather brief, although it was expected in accordance with their roadmap from last week.

The team jumped straight in by making an apology for not removing the “Press any key to start” screen, admitting an error on their end led to the top wish not being addressed in update four.

The update was released earlier this week and contained mainly bug fixes and improvements in several areas.

“Unfortunately due to an oversight on our end (yes we are human) we inadvertently posted the wrong date for the ‘Press Any Key To Continue’ change on the previous [week’s] Feedback Snapshot,” said Microsoft.

“As such this change did not go live in this update but instead will go out with Update 5 as we had originally intended.

“As always our goal is to maintain transparency and collaboration with our community as we continue to evolve the sim.

“With that said, the team would once again like to express their gratitude for the feedback and patience from those of you who encountered some turbulence with the previous patch.

“The team will continue to actively work through the Feedback snapshot and keep the community informed along the way.”

This week’s feedback snapshots see noticeable changes to last week’s.

For example, it can be seen that some of the issues such as Night Lighting - Terrain Emits Light? and Garmin G1000/G3000 & Autopilot Related Issues have had their status changes from not started to started.

As for an update to the SDK, this is what the team has been working on:

DevMode:

• The DevMode team is working on improving the overall stability, giving a special focus to the Project Editor, the Scenery Editor, and the AircraftEditor.
• We’re finishing the implementation of the new “Export Window” of the Project Editor. The underlying process will, among others, feature a validation step. This will ensure that packages built are valid and ready for later publication.
• We’re also working on a Global rework of the Console and logging system, its ergonomics and features, especially to help the community find out faster what could be wrong during the package build process.
• In the long-run, a dedicated team is still working hard on the forthcoming brand new Node-based Visual Effects System.
• The community’s feedback continues to be very helpful in identifying & fixing bugs and thus making the tools better.

WebAssembly:

• The MSFS Platform Toolset linker now properly reports errors in the Visual Studio Output tab.
• We added the “Generate Debug Info” linker option to the MSFS Platform Toolset. It allows users to strip all symbols from the Release version (which makes them much smaller in size).
• We changed the way symbols are exported from WASM modules: only explicitly exported ones are now really exported (which reduces module size even further). No code change is required.
• Continuous efforts to improve debugging and reduce iteration times.
• The WASI layer has been fixed to enable the usage of opendir/readdir from within WASM modules.

Microsoft signed the post with the usual expectation of when the next update will be released, in one week from posting.

If the development roadmap is adhered to, we will see a new Around the World episode looking towards North America, as well as a new Partnership Series video.