I don't know if it was a bug so much as a deficiency. OS Improvements to branch prediction will most likely not be backported to Win10
vikingtons
joined 1 year ago
I don't think this is related to the OS. What displays do you have connected?
It's like that episode of futurama - the mirror wernstrom put in space to reflect sunlight, which gets tapped by a little space rock, and tilts into a solar powered death beam
I gather that the nt kernel isn't inherently bad, rather that the aging win32 subsystem is the problem.
who asked for this?
Higher end phones have the capability to gear down to 1hz to save power on static representation. Would be nice to see that on notebook eDP and hell, even with dekstop monitors too.
I think below that range they can frame double (low framerate compensation LFC) to go as low as 24 FPS
Up until relatively recently, it was great to see that Vulkan and DX12 were in a practically even split.
Still great to see that some of the best talent in terms of visual fideltiy showcases Vulkan, like rdr2 (originally defaulted to dx12, now vulkan), doom eternal and so on. Fully expect the next GTA to.
stadia was derp but it forced interested publishers to get acquainted with vk. I think it ended up doing more good for the industry in the end as a failure, rather than harm by succeeding and locking subscribers into such a restrictive game "ownership" paradigm.
Good for them if it help eliminate the mark up of displays advertising gsync ultimate. I have my doubts but it'd make sense if they're no longer using dedicated boards with FPGAs and RAM.
One has to wonder if VESA will further their VRR standard to support refresh rates as low as 1Hz
feels to me that people who work on other parts of the OS are getting fed up with the default shell experience to such an extent that they have to build their own skunkwoks solutions
What I was alluding to with regards to idle mclk behaviour is that there are two factors at play: vertical balanking interval (intrinsic to available display modes for each physical monitor) and combined display bandwidth (cumulative of all connected displays to the adapter).
Your mclk will idle high with 'incompatible' VBIs, and it'll also idle high to sustain a lot of display throughput.
This can be observed regardless of GFX vendor, though symptoms may vary somewhat between them. I suppose it could be considered a limitation of GDDR (the same behaviour was never really observed on HBM GPUs like the Vega 64 or Radeon VII)
That said, friends of mine with nvidia gpus have fixed various multi-display specific issues using nvidia profile inspector