Though rather neglected for quite a while, seeing the Feedback Snapshot get a major update today without being on the roadmap was a great surprise. Much appreciated!
Sim Update 11 looking good with further DirectX 12 optimisations, significant live traffic improvements and FSR 2.x support, besides all the 40th anniversary content.
Not a great sign that WASM may be pushed off to SU 12 now, which almost certainly will be well into next year. I don’t see how the A310 comes to Xbox unless the developers manage to get it working without WASM or through a custom solution. That may be a breaking point for many Xbox users on the fence about the platform.
Interesting that the scenery gateway is possibly going to debut in a limited form in SU12. That’s going to be a fairly major improvement when it comes.
I also saw a mention of possibly improved AI behavior coming in SU11.
All good things to look forwards to.
I’ll echo that this was a very informative dev update, thanks for putting in the effort to get all the snapshots and roadmaps updated.
The provided APIs are sufficient for building a basic (but very useful) accurate weather radar with fixed tilt and variable gain. There are no present plans that I’m aware of for going beyond these graphic APIs.
I mean, you can’t do predictive windshear or lightning detection or that kind of advanced stuff, but for the core of what pilots really need, i.e. what is a reasonably accurate representation of the precip levels in front of my aircraft, the current graphic APIs work just great.
I agree, if this is considered ‘‘fixed’’ with no communication to the 3rd party devs on what they need and given clarification to them, its worrying sadly
Can you fix DLSS 2 before SU11 comes along and breaks more stuff.
New game driver doesn’t work well for some as well need sorting.
I’d rather not see a whole list of more stuff that could come along and cause issues why is DLSS 3.0 coming out for SU11? It’s not like many of us are going to be buying 4000 series cards for some time.
I’d rather see things like optimisation for DLSS 2 and sort runway handling, driver improvements.
Please address what’s broke before, adding more problems into the mix.
As far as I am aware the radar model uses a conical intersection extending from the front of the aircraft, like an actual weather radar. So you will not get returns above or below this, if you have the API set to the appropriate mode. There is a top-down NEXRAD style mode in which all altitude weather is shown, perhaps that’s what is confusing developers.
Clouds are transparent to real radar, unless they have sufficient water density. The bitmap API models this, with the developer able to set colors of their choosing based on the density.
Windshear detection is pretty important in a modern airliners, the absence of which can result in deadly consequences. I don’t think Asobo should be so quick to dismiss the concerns of it’s customers and aircraft development partners.