Forum Discussion
Below is a link to the correct method for obtaining the correct view projection that would eliminate this issue:
https://github.com/ValveSoftware/openvr/blob/master/headers/openvr.h#L2040
- 5 years ago
+1, please fix this
Same issue, Pimax 5K+, 1080Ti, Ryzen 3700x, Steam version
- 5 years ago
Thanks for posting that here, the solution is indeed found in #2040 of Valve's OpenVR master.
It's the most cost effective approach to get it done right just once.
The Devs won't have to manually put in new headsets that get released afterwards: OpenVR API takes care of that henceforth! The scaling will be right, the depth perception will work, even for unreleased future newcomers like the G2 - without any manual adjustments by the Devs later.
P.S. Do not clean nulls or anything about the matrices given, some don't use all variables, some headsets require/fill them, some adjust for manufacturing tolerances with them, etc. 🙂
- 5 years ago
Defo. Hope they implement soon. Thanks for the breakdown of how to easily fix for the devs.
That performance is really needed in VR. Especially on the flagships like Index, Reverb and 8KX.
@Straatford87please see this thread for fix for all the above headsets now and into the future.
- 5 years ago@willacegamer is this something that has to be implemented by the devs or can use this and if so, how?
- 5 years ago
Where is this done? o0
About Star Wars Games Discussion
Recent Discussions
- 18 seconds ago
Make AIs more dangerous
Solved2 days ago