Hi, just saw that my bug report about foveated rendering (and VRS) doesn’t work with DX12 was closed as won’t fix on Feb 7th without explanation; I didn’t even get a notification. The public link (with 8 votes) has some generic explanation about dev prios, which I understand, but: a main VR feature is broken, there is no way using foveated rendering or VRS in PCVR. You can’t be serious about that?
I agree, we need some clarification about this.
This should be working with URP, do you have an issue tracker link to share?
Thanks. I asked the team responsible to re-review it and either reopen it or come up with a better explanation.
@Tautvydas-Zilys Any update on this? We are waiting since more then 6 months for a fix on this.
Not yet, hopefully soon.
The bug has now been reopened.
Thank you! llll
thanks, this is good news. albeit it says now “Under Consideration for 6000.6.X”…
How do you prioritize these kind of bugs? I mean, this bug is basically a very important XR feature being completely broken for PCVR.
All bugs always first target our “trunk” branch, which corresponds to either the latest alpha or the release after the latest alpha, depending on where we are with our branch off. Once the bug is investigated, then the team determines which releases the bug fix is backported to. This decision is deferred to after it is known what it takes to fix the bug so that the risk profile plays into the backporting decision. This is the process for all bugs we fix - we cannot populate backports until it is “fixed on trunk”.
In other words, “Under Consideration for 6000.6.x” today just means the bug is open and that it hasn’t been fixed yet.
Today I found out that it also does not seem to work with Vulkan… It gets deactivated in builds (at least when Meta OpenXR features are installed). If we force to activate it with a build script, it runs, but it breaks rendering, at least in our setup.
This basically means the SRP Foveation feature does not work on ANY platform.