Following on from the latest patch for MSFS, the Microsoft Flight Simulator team have provided further details on the development process in their regular Development Update.
They start off by simply stating that they have got their dates wrong in regards to removing the ‘Press Any Key to Continue’ from the opening screen. They wrongly stated it would be in the recent update 4 but, in fact, it is scheduled for update 5 (to be released on the 22nd October 2020).
The team then go on to inform what they will be focusing on in the meantime. The feedback snapshots indicate that they have started work on some of the bugs, including autopilot related issues with the Garmin G1000/G3000, and issues with the night lighting. The latter being addressed in the next update. Other concerns addressed in the next update will be, left and right swaying of the A320 and a pitch oscillation issue.
On the wish list the developers are sorting out the metric units (kilos v pounds) and the ability to disable cockpit tooltips, both to be addressed in update 5. A full list of bug issues and wish list requests can be seen in the images below.
The developers are also working on updating the SDK especially in relation to DevMode and WebAssembly. Stability and implementation of a new ‘Export Window” in the project editor are at the top of the list of DevMode. Full details are listed below.
Finally, The Microsoft Flight Simulator Team have announced that they have nearly 60 partners already approved to be part of their Marketplace Partnership Program. These will provide more content for the simulator over the coming months. 5 more airports have been added to MSFS as of today. These are, Kelowna Airport (CYLW), King Shaka International (FALE), San Diego International Airport (KSAN), Tivat Airport (LYTV), and Mayor Buenaventura Vivas Airport (SVSO).
SDK Update
The SDK team continues to improve many areas of the SDK based on input from the developer community. Recent work focused 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 effort
sto improve debugging and reduce iteration times. - The WASI layer has been fixed to enable the usage of opendir/readdir from within WASM modules.
Source: Microsoft Flight Simulator
Credit to Gold787Flightsim from Discord
