Forum Discussion
Can we get lens separation exposed to the Config Utility?
Hello Oculus!
I received my DK2 yesterday, and it's awesome.
One thing that bugs me though and greatly detracts from usage is the IPD range - my IPD is 69mm, which means it's out of the 64mm-ish perfect range by quite a bit. It ends up blurry for one eye or the other because of this.
I've gone ahead and ordered these separation extenders, which will help a lot, but the problem then becomes the separation distance for the lenses being wrong, and the wrong value being reported to games and apps.
It can be hacked to the right value inside individual games' DLLs or EXEs, but that is hardly ideal and potentially prone to error.
So could we get this exposed to the config utility (hide it under advanced!), pretty pretty please? I'd love to have a clear picture through the Rift without having to individually hex edit a bunch of games.
I received my DK2 yesterday, and it's awesome.
One thing that bugs me though and greatly detracts from usage is the IPD range - my IPD is 69mm, which means it's out of the 64mm-ish perfect range by quite a bit. It ends up blurry for one eye or the other because of this.
I've gone ahead and ordered these separation extenders, which will help a lot, but the problem then becomes the separation distance for the lenses being wrong, and the wrong value being reported to games and apps.
It can be hacked to the right value inside individual games' DLLs or EXEs, but that is hardly ideal and potentially prone to error.
So could we get this exposed to the config utility (hide it under advanced!), pretty pretty please? I'd love to have a clear picture through the Rift without having to individually hex edit a bunch of games.
4 Replies
- That's an interesting use case, but I somehow doubt there's time to implement a feature that would only be used by a small number of people using 3rd party mods for the headset. But it is a valid concern and I can share it with the team.
"cybereality" wrote:
That's an interesting use case, but I somehow doubt there's time to implement a feature that would only be used by a small number of people using 3rd party mods for the headset. But it is a valid concern and I can share it with the team.
If not something in the config utility itself (I know that requires a lot more than just changing the value... gotta get it into the SDK, handle all the GUI stuff blah blah), then even just a config text file or something that we could dump it into to override it would be *awesome*!
I assume it'd probably be less work to get it exposed into a config file or something than all the way into the GUI Config Utility, so if that's something that makes it more likely, I am all for it.
The main thing is just making it so we don't have to hex edit each game separately.
Thanks Cyber!
Edit: Also, I assume that you're going to need something like this for CV1, or if not that, then CVx. At some point, anyway. Might as well add it now, right? :P Point being that, while it's a small use case right now, eventually it will be common.- There now is a new software solution to this problem, details here: viewtopic.php?f=20&t=15355
Just getting the word out to those who have either bought adjusters or done modifications themselves. Cheers "cybereality" wrote:
That's an interesting use case, but I somehow doubt there's time to implement a feature that would only be used by a small number of people using 3rd party mods for the headset. But it is a valid concern and I can share it with the team.
If its pure number-of-users affected, then +1.
The current route I'm exploring now is a custom firmware that causes the DK2 to reply with the correct IAD. I don't really want to do that, but the DK2 is difficult to use, let alone develop for, due to IAD-IPD mismatch (distortion, blurriness, inaccurate chromatic aberration correction, and exacerbated AMOLED fill factor).
