Oculus Runtime and SDK Thread.
- Thread starter SuperTed
- Start date
With some tweaking I can get a good experience, but it's not 'release ready'. Without the 'Core Parking' tweak i am still getting tracking issues resulting in gamma flashes. In some systems (e.g. Stryx last night) there's a lot of judder. To me this seems all CPU related, where in busy systems the (net)code is freezing up things. In the tutorial missions everything is smooth even in the asteroid fields. I am also using the 'super sampling' tweak to make the visuals (and text) more 'grisp'.
So upgraded to ED3 along with the upgrade to 0.4.3 so I can't tell which it is that is the cause but I'm seeing a huge drop in FPS. I was doing 70+ with the 2.x version of ED and 4.2 for the same area now it's more like 30.
DirectToRift or Extended?
I cant get 0.4.3 to work in any games via direct to Rift. Even the demo in the Oculus config tool is not working correctly. All seems ok in extended mode though.
There is a thread on the Oculus forums about this as I'm glad to say I'm not the only one who has issues with this release.
https://developer.oculusvr.com/forums/viewtopic.php?f=34&t=16299
There is a thread on the Oculus forums about this as I'm glad to say I'm not the only one who has issues with this release.
https://developer.oculusvr.com/forums/viewtopic.php?f=34&t=16299
0.4.3 Runtime + Extended Mode (Rift has to be the primary monitor). For better performance turn off AO, AA, Blur and set Shadows to Medium or Low.
Thanks. It's working fine, frame rates seem OK, but I'm having a hard time adjusting the rift so my eyes dont feel liek they're goining crosseyes to focus. I think it's the seperation, but it seems ED doesnt use the settings from the oculus Config Tool.
Also, I'm getting bad 'rainbow' effects, chromatic abertaions, which make the menus especially bad to look at.
Also, I'm getting bad 'rainbow' effects, chromatic abertaions, which make the menus especially bad to look at.
Yeah, it's IPD related.
You can amend it manually.
C:\Users\YourUsername\AppData\Local\Frontier Developments\Elite Dangerous\Options\Graphics and open Settings.xml in Notepad and change <IPDAmount> to match what your IPD is.
e.g. if it's 69 then 0.069000
I noticed you've just got the DK2. You most probably have already done this, but make sure you've also updated the firmware in the DK2. The last update really helped with the chromatic aberration.
I have updated to BETA 3 and 0.4.3 version of Oculus Runtime, and now I'm experiencing strange graphical glitches playing on my DK2: instead of black color I see reddish tint, plus vertical screen tearings here and there. Overall performance is good, however this graphical issues looks ugly... Prior to 0.4.3 everything was OK.
I'm running GTX 970 SLI, i7-950, 12 GB, Windows 7 64-bit. Latest (vanilla) nVidia drivers. Other games and demos I have tried runs and looks OK, so this is Elite: Dangerous specific issues. Also, I have tried capturing screenshots, and everything is OK on them, so this is something to be with Oculus Runtime, I believe... Any suggestions?
Thanks!
UPDATE: I just have traced problem to SLI. With disabled SLI everything look normal. Also, my single Asus STRIX 970 GTX is able to run maxed out Elite with 70 FPS on Rift (SSAA is 1.5 in settings.xml). While SLI setup showing roughly 75 FPS with 95% load on BOTH GPUs... And those graphical glitches
UPDATE2: This was my faulty SLI connector... Fiddled with it a bit, and everything now works fine. However, my 2x970 SLI setup cannot run 4K Elite on Rift with 75 FPS... Max what I'm getting is ~30 FPS when <SSAA>2</SSAA> is specified in settings.xml... Any other way to make text more readable on Rift? Thanks!
I'm running GTX 970 SLI, i7-950, 12 GB, Windows 7 64-bit. Latest (vanilla) nVidia drivers. Other games and demos I have tried runs and looks OK, so this is Elite: Dangerous specific issues. Also, I have tried capturing screenshots, and everything is OK on them, so this is something to be with Oculus Runtime, I believe... Any suggestions?
Thanks!
UPDATE: I just have traced problem to SLI. With disabled SLI everything look normal. Also, my single Asus STRIX 970 GTX is able to run maxed out Elite with 70 FPS on Rift (SSAA is 1.5 in settings.xml). While SLI setup showing roughly 75 FPS with 95% load on BOTH GPUs... And those graphical glitches
UPDATE2: This was my faulty SLI connector... Fiddled with it a bit, and everything now works fine. However, my 2x970 SLI setup cannot run 4K Elite on Rift with 75 FPS...
Max what I'm getting is ~30 FPS when <SSAA>2</SSAA> is specified in settings.xml... Any other way to make text more readable on Rift? Thanks!
Last edited:
After a while I figured out you really, really need to check how goggles are positioned. Try adjusting up or down , I practically eliminated that effect in both a and b cups. (fiddling with using it with glasses) If only screendor effect was as easy to mitigate :/
- - - - - Additional Content Posted / Auto Merge - - - - -
I would really like to know answer to that too Coupled with astigmatism nav list is unreadable (not to mention it goes out of focus too damn fast)
I found, that retracting from PC and pressing F12 to reposition camera helps a lot! Since then you back to your normal position, you happen to be much closer to text, and it gets MUCH more clear! Try it. Other than that, I can't imagine any tricks to overcome low resolution of DK2... No AA, no SSAA can fix THAT... Hope CV1 will get at least QHD resolution... But then you must have a REALLY decent rig to run game with steady 75 FPS... So, like 3D Vision, gaming in VR will NOT be for everyone in terms of investment in hardware...
Try it. Other than that, I can't imagine any tricks to overcome low resolution of DK2... No AA, no SSAA can fix THAT... Hope CV1 will get at least QHD resolution... But then you must have a REALLY decent rig to run game with steady 75 FPS... So, like 3D Vision, gaming in VR will NOT be for everyone in terms of investment in hardware...I have updated to BETA 3 and 0.4.3 version of Oculus Runtime, and now I'm experiencing strange graphical glitches playing on my DK2: instead of black color I see reddish tint, plus vertical screen tearings here and there. Overall performance is good, however this graphical issues looks ugly... Prior to 0.4.3 everything was OK.
I'm running GTX 970 SLI, i7-950, 12 GB, Windows 7 64-bit. Latest (vanilla) nVidia drivers. Other games and demos I have tried runs and looks OK, so this is Elite: Dangerous specific issues. Also, I have tried capturing screenshots, and everything is OK on them, so this is something to be with Oculus Runtime, I believe... Any suggestions?
Thanks!
UPDATE: I just have traced problem to SLI. With disabled SLI everything look normal. Also, my single Asus STRIX 970 GTX is able to run maxed out Elite with 70 FPS on Rift (SSAA is 1.5 in settings.xml). While SLI setup showing roughly 75 FPS with 95% load on BOTH GPUs... And those graphical glitches
UPDATE2: This was my faulty SLI connector... Fiddled with it a bit, and everything now works fine. However, my 2x970 SLI setup cannot run 4K Elite on Rift with 75 FPS...
I use Supersampling with a resolution of 2560x1440 which improves the readability of text for me.
how do you do that ??
and anyone got the phenomenom with images are doubled when you move your head ??? tried with direct mode and extended mode, same thing.
Yes its pretty common if your system can't maintain 75fps or above at all times. Even my Xeon workstation with GTX 980 gets this randomly in certain spots but no where near as bad as I had it with the GTX 580. Use Fraps or MSI Afterburner to log your FPS and see if it dips.
Still lots of optimization to come as well I assume.
Still lots of optimization to come as well I assume.
Had an interesting discovery last night.
Went for a little fly around and the frame rate seemed terrible with judders and general low framerate issues.
After a bit of digging, I noticed my CPU overclock had failed and the bios had defaulted back to some fail safe setting which had the CPU running at 3.2ghz instead of it's normal 4.2ghz.
Rebooted and got the CPU clock speed back to up to normal and all smooth as silk again. I don't know exactly how CPU bound this game is but when running a GTX980 card...that extra 1ghz on the CPU made a hell of a difference.
Went for a little fly around and the frame rate seemed terrible with judders and general low framerate issues.
After a bit of digging, I noticed my CPU overclock had failed and the bios had defaulted back to some fail safe setting which had the CPU running at 3.2ghz instead of it's normal 4.2ghz.
Rebooted and got the CPU clock speed back to up to normal and all smooth as silk again. I don't know exactly how CPU bound this game is but when running a GTX980 card...that extra 1ghz on the CPU made a hell of a difference.
thanks for the heads up! Looked at the changelog. Basically... nothing super exciting. Bugfixes are always nice! Kinda wonder what they're working on over there. If only they released patches like FD did! Every month: 5,000 CHANGES XD
Betting most of their internal dev is going toward 5.0, which will support CV1, and generally be a much different beast.
Betting most of their internal dev is going toward 5.0, which will support CV1, and generally be a much different beast.