Option to save FPS with a low render zone at edges?

This is not a wish or request but I've been following the VR HMD threads of the most used ones for quite a while and lots of people write about blurry edges that force them to turn heads further bc they can't recognise details at the edges.

So the idea and my question is:

Is it possible to implement a zone with selectable width at the edges that renders much lower details to save GPU (or even CPU?) power for a smoother VR experience without losing the resolution and details in the centre where they matter?

Certainly the result won't be as pretty as what we have now but maybe this could be a good trade for those who struggle with VR performance or have blurry edges anyway?

Certainly it is called foveated rendering to be used with eye tracking, technology is currently being worked on I know by Oculus and am sure others also.

https://www.oculus.com/blog/half-dome-updates-frl-explores-more-comfortable-compact-vr-prototypes-for-work/

Certainly it is called foveated rendering to be used with eye tracking, technology is currently being worked on I know by Oculus and am sure others also.

Thanks. I heard about that and combined with the reports from lots of users about blurry edges I thought a "static foveated rendering" without eye tracking could be helpful lots of months or years before we get eye tracking in DCS or even before we get eye tracking with the most selling HMD manufacturers.

With a selectable width it would be at everyone's preference how much detail is sacrificed for a smoother experience.

Yeah, it might be worth it, it might not. I doubt ED is gonna sink the resources into developing it.

Honestly for me foveated rendering is the white whale of VR. I don't think its coming soon, and I think its much harder to actually implement than the oversimplifications are making out to be.

Maybe if NVIDA or AMD actually make a VR optimized card, FR might become "a thing". But I'm not seeing it.

Harlikwin said:

Yeah, it might be worth it, it might not. I doubt ED is gonna sink the resources into developing it.

Honestly for me foveated rendering is the white whale of VR. I don't think its coming soon, and I think its much harder to actually implement than the oversimplifications are making out to be.

 

Maybe if NVIDA or AMD actually make a VR optimized card, FR might become "a thing". But I'm not seeing it.

Agreed. I fear and hope the same way. And that's why I wondered if it really takes too much effort to reduce rendering in a certain static zone at the edges.

My major concern is how large that zone has to be to have a significant impact on frame rate.

Pimax has it implemented and working for Nvidia RX users in DCS. On the other hand, Index users have almost perfect visibility at the borders so it will not be an option for us.

Pimax has it implemented and working for Nvidia RX users in DCS. On the other hand, Index users have almost perfect visibility at the borders so it will not be an option for us.

That's interesting. Both of the info. Any numbers of the FPS gain with the pimax? Or any screenshots of this running on a pimax?

Pimax has it implemented and working for Nvidia RX users in DCS. On the other hand, Index users have almost perfect visibility at the borders so it will not be an option for us.

Yes but true foveated rendering with eye tracking should certainly help performance, hence more eye candy to run. Probably still a ways off from that though, Oculus is still working on it with Half Dome technology - or at least they were as it was shown at the last OC6.

.

Honest question. I have pretty darn clear periphery in my index and I’m happy. Other product users are complaining about blurry edges and seem unhappy. 
How would lowering resolution outside the sweet spot help either party?  Seems it would just make edges on all units blurry. 
thanks. 

On 12/17/2019 at 4:54 PM, Tom Kazansky said:

 

 

That's interesting. Both of the info. Any numbers of the FPS gain with the pimax? Or any screenshots of this running on a pimax?

8kx DCS VR standard settings SP The 3080 with FVR had 5 FPS more than 6800xt. Look at our big benchmark thread here.

If FVR is not fixed, it will add another layer of delay to it. Non fixed vs. fixed will not improve your FPS. It totally makes sense to use fixed FVR on headsets like pimax 8kx and G2, because the edges are blurry anyways. So why render that blur stuff in full quality?

Edit: Had a look at it in MP. There it looks different. Fixed FVR adds additional stress to the CPU (5900x) so ends in worse Framerates because the CPU cant deliver it. So fixed FVR with Pimax doesnt help in MP.