Couldn’t have said it better…
1 Like
Another specific quote from PMDG:
rsrandazzo commented
Yesterday, 17:02
Chris- MSFS is so far behind on it’s ability to support what we do- it is going to be a REALLY long time before we see you there. I love MSFS but it’s ability to support products like ours is… woefully inadequate. They are chipping away at it- but it is going to be a long, long wait. - RSR
end quote
I suspect the “diplomacy” and political correctness will eventually fade to the point that plain speak will finally rule the day and something will finally get done. All this tolerance and “beating around the bush” is getting NOTHING done. All the excuses for such a slow pace will do nothing to help this project succeed.
VR may be a beautiful thing in MSFS, but even it will not help the situation.
2 Likes
Aerosoft’s Project Manager Mathijs Kok directly and crushingly contradicts that standpoint.
“But as Hans shown, we still need some love from Asobo to solve problems. But many (many!) issues have been solved in talking to them. The people at Asobo are really amazing and we are sure they will make our release using all the options the new sim has to offer possible.”
Quite obviously, things ARE getting done, as mentioned by PMDG itself as well and everyone else who has commented on the issue with visibility of what Asobo is doing, nicely debunking your conspiracy theories.
Incidentally, progress on the SDK is listed weekly on the development updates, so, quite obviously, your “getting nothing done” is false.
From the latest development update:
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.
so much for “Getting NOTHING done” 
I am temporarily closing this topic.
It is very clear that tempers are flaring up on this thread, and that is toxic to this community.
I want to remind everybody to read the Code of Conduct.
To quote one section from it:
I will be sending messages to some of the people on this topic. When this topic reopens, I expect people to be civil with each other and disagree respectfully.
6 Likes
This is the second time we’ve had to come to this topic, to deal with multiple posts failing to comply with the Code of Conduct. I am not spending anymore moderation time on this topic, so I am locking the thread permanently.
If we see a pattern in any other threads, we will start issuing CoC warnings.