The Microsoft Flight Simulator development team has recently published the first out of four updates to come this month for the new simulator which is constantly being refined to fix bugs and improve the overall user experience.
The Microsoft Flight Simulator development team started out the update with a small notice about how COVID-19 is affecting the team. Due to new restrictions in France, much of the MSFS team are working from home and states that the safety of all employees is a top priority and they hope everyone can understand that.
The development update shows two new feedback snapshots with progress on community suggested ideas/bugs, as well as showing the existing development roadmap for 2020 valid until November.
The snapshots mainly touch on issues that have already been identified by the team, and issues/changes that have been implemented in the most recent update.
The team has also mentioned an SDK update which means, that the developers are going to be able to have a better experience creating new content for the simulator.
To conclude the post, the team shared their November Q&A which provides more detail into the development of the simulator and discussion of community ideas.
SDK Update
DevMode:
- Node-based Visual Effects System continues to be improved with more and more useful features, allowing setting-up great effects in the sim. We are now focusing on improving the system’s performance.
- We started designing a way to easily create new assets from within the Project Editor, starting from given available asset templates. We should essentially focus on types: new Mission, new Airport & new Aircraft.
- Improvements, new options, and small features keep on being added here and there in tools.
- To list just one of them: a new auto-hide feature is now available for the DevMode bar.
- As a background task the DevMode team is always working on improving the overall stability of the DevMode, especially giving special focus to the Project Editor, the Scenery Editor, and the Aircraft Editor.
WebAssembly:
- Mouse events are now correctly forwarded when multiple WASM gauges are used in one single Virtual Cockpit.
- Lowered memory consumption during WASM module compilation.
Source: Microsoft Flight Simulator Forum
