Win10 2004: WDDM 2.7 Support

From the looks of it, it still doesn't allow us to disable the vsync on window mode games, right?

I hate the vsync in window mode. It just prevents tearing but doesn't sync the framerate with the refresh rat. As a result it ends up stuttering randomly. On top of that it has floaty laggy feel to inputs.

 

mine says unknown
https://imgur.com/a/P7u64Qm

 

And we still don't even know what scenarios the hardware accelerated GPU scheduling actually will benefit, aside from the vague description of "Reduce latency and improve performance" when being able to check the option within Win10 2004.


I had missed this but at least Microsoft has published an official summary of WDDM 2.7 now.
https://docs.microsoft.com/en-us/wi...w-for-windows-10-display-and-graphics-drivers
Whereas the previous assumptions floating around seems to have been put together from the various articles on the DirectX blog.

 

Slightly reduce CPU overhead, GPU driver overhead, APIs overhead.
Slightly reduce CPU usage.
Improve input lag.
Some software algorithms, which were usually executed in <OS - graphic driver> now are now executed on the side GPU hardware and direct to graphics layers.

 

I still want to see a reference source claiming al this that is not a social media or a "tech site". GPU schedulers are more specialized and less general purpose than some people think. The only thing I could image some improvements is moving some pre-WDDM 2.0 APIs (e.g.: DirectX 11 graphics) runtime tasks related to memory management to GPU driver to increase parallelism, but honestly I do not know how much a linked list management could improve performance if moved from a runtime thread to a GPU driver thread outside specific bottlenecks scenarios (e.g.: resources overcommitment).

 

Microsoft were supposed to have a blog post up when it released.

 

https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-2004

Check out the known issues before updated to 2004

 

It's been updated in 2.32

 

it apparently still misreports mesh shaders as unsupported on Turing/450 drivers.

 

That is also a DWM issue, but we are but a minority to demand solutions from MS to that.

 

Yeah it sucks. So we can't even get properly vsynced smooth performance, neither can we get responsive latency for the DWM. And unfortunately many people dont notice the lag or stuttering. So RIP.


By the way, does freesync on window mode get rid of the input lag? Can freesync bypass the DWM?

 

By the way, does freesync on window mode get rid of the input lag? Can freesync bypass the DWM?[/QUOTE]
Freesync can work with vsync on as itis a form of variable sync. It works both windowed and fullscreen mode afaik.

 

Can you install the inf device driver thru dev manager and control it through this win store driver ?

 

from wikipedia :

• Hardware-accelerated GPU scheduling: an additional option in the system settings, which increases the minimum and average fps to reduce latency, requires a minimum version of shader model 6.3 in hardware from the video card. nVidia GeForce has support since the 10th series or later, but AMD Radeon only with the RX 5000th series, Intel removed support in the final drivers.
• is this true? https://en.wikipedia.org/wiki/Windows_Display_Driver_Model#WDDM_2.9

 

Damn it, that's is probably correct.
No love for the VEGA, I guess

 

nah i don't think so, afaik not even the 5000 series support hw scheduler rn. imo amd is dropping support for older cards way too fast.. it's making me angry.

 

No, no AMD cards support GPU scheduling at the moment. Or, no AMD drivers support it, to be more precise.

 

nobody supports it, because Microsoft isnt

https://twitter.com/WindowsLatest/status/1268099559680430081

 

Bull.

 

Hardware Scheduling is a Work In Progress, both on MS and AMD/NV side. Coming Soon ™