System Requirements For Pimax 8k x using Foveated Rendering?

Assuming foveated rendering becomes usable with the Pimax 8k x, what do you think the requirements to run it smoothly in terms of GPU will be? (In demanding games such as Arizona Sunshine or Elite: Dangerous)

Too many unknowns to answer this.

We don’t know how much foveated rendering will save and in what situation.
Don’t know how demanding the game you want to run is.

1 Like

another topic opened so we can speculate on shit we don’t even know something about…please…

Its all fine, but whatever answers you will get, none of them are really worthy to consider in the end, because its all speculation…but if you just want speculation to fill your time and to get upset and set up disccusion about speculations A and B, go for it.

:smiley:

3 Likes

Keep in mind that enabled eye tracking will (probably always) consume CPU (same as hand tracking module)
Info from FOVE hmd users and leap users with mid ranged CPU’s

Assuming that foveated rendering becomes usable with the Pimax 8K HMD (assuming you mean eye-tracked foveated rendering) and assuming that games such as AS or E:D support it and assuming that GPU manufacturers will (contonue to) support this, I assume that the requirements in terms of GPU will be less than without it, assuming the same level of rendered detail in focus as compared to a solution without eye-tracked foveated rendering.

Hope I could clear that up for ya! :wink:

Not in the case of the AdHawk system, which does not use cameras and already passes the information of the position to the computer, without it having to do anything. That’s why I recommended it.

1 Like

Advertisement said that cameras are power hungry. I accept that.
But no info on other specs of that MEMS sensor
(Used by Dr. Sarkar in breakthrough MEMS microscopes and i can’t find any on market, maybe i’m wrong customer).
Even polling rate of gaming mouse (125hz to 1000hz) differs cpu load.
I convinced myself already for no miracles from PiMax + AdHawk rather than waiting for something spectacular.

I don’t know, we’ll see.

Artifact-free Foveated Rendering might become feasible within the next 3 years. It’s not going to be useable when the 8k-x ships. To really see a performance difference is going to require a high frame rate, low latency eye tracker, and foveated rendering support in the graphics card driver. Considering Pimax isn’t even going to have any eye tracker at all at 8k-x launch, and other eye trackers on the market aren’t good enough for decent foveated rendering…

Next gen GPU will come with hardware better suited for foveated rendering Nvidia hinted. So if you are on very low budget but want a Pimax better to see what they will come up with. They also said they will make things like fixed foveated rendering easier to integrate for developers and that would help Pimax users a lot already.

On a different note, why not consider a fixed (foveated) rendering, especially for the 8K(X) ? This would mean you do not have/need eye-tracking, and simply render anything outside a certain range in the middle in a lesser resolution to lessen the strain on the GPU/CPU. In that case of course you would occasionally look outside the fully rendered area, when you move your eyes towards the boundaries, so you cannot permit the rednering to be only 20% of the full rendering, because then you probably will always notice the boundary between the fully rendered and the peripheral part, even when not looking at it.
But if we for the peripheral part used only the rendering resolution applied by the 8K, and made use of the full resolution only for the center vision, it could alleviate the GPU/CPU load to some extent.
Doesn’t some NVidia tool already allow for such fixed rendering split to support different resolutions ?
Surely not the ideal approach, but we are talking about trade-offs when it comes to powering the 8K(X) because otherwise your favourite game just simply may not run at all on the 8K(X)…

I like the idea of an optional fixed foveated rendering for lower end GPU’s. Such a software setting would increase the customer base for Pimax because people with lower end GPU’s can still have the 200 FOV Pimax headset and have good FPS

1 Like

We are talking about the 8K(X) - your lower end GPU here would be the GTX1080Ti… :wink:

Or perhaps you were thinking more generally about applying it to the 8K too ? Yes, I thought about that too when the news of this feature from NVidia was released, but never followed it up. Would be interesting to see which ration of lesser quality rendering would be okay without creating a disturbing rift between the pretty and the ugly part of the screen… and if the software really wordks as envisaged, and saves any significant amount of GPU load.

It seems likely that graphics chips will be upgraded with VR-friendly features, in the next few years. Foveated rendering and other techniques (like warping) are bound to be arriving at some point.

The features (API) need to be easy to use though, or game developers won’t use them.

1 Like

I’m sure Pimax will include the option even for the 5K version if it means more people would buy their product. And rightfully so. I love how Pimax just tries to do everything because however shoddy, in the end it does work and they will be the first

Didn’t Tobii have a working headset using eye tracked foveated rendering at Ces this year? From what the people who’ve tried it have said it’s unnoticeable. Right now I don’t think the problem is with foveated rendering, but with getting the eye tracking to work on every facial structure.

Eye-Tracking Is Both Incredibly Important And Very Risky

1 Like