The intention of D2R is a low-level hardware access to the Rift display bypassing Windows/drivers for lower latency. BUT it's bugged in ED which results in a) D2R not working at all (app crash) or b) being capped at 60 fps.
Oculus Rift General Discussion and OR Games to try out Thread
- Thread starter Sir.Tj
- Start date
The intention of D2R is a low-level hardware access to the Rift display bypassing Windows/drivers for lower latency. BUT it's bugged in ED which results in a) D2R not working at all (app crash) or b) being capped at 60 fps.
My experience with direct mode and elite is that it just doesn't work. I wasn't aware of the 60Hz cap with elite and direct mode because I and most others have never had it working in the first place.
What SDK version are you running? Try testing with the latest.
<edit>and what have you got connected to what output?
Last edited:
I'm running the latest runtime/SDK 0.4.3. When I say it doesn't work I mean it (elite) just crashes on startup when rift is set to direct mode. It works fine in extended.
Ok tried mine B2.06 SDK 0.4.3 direct mode + rift DVI +TV HDMI and I could not select rift mode above 60Hz, I can set my TV to 75Hz but the resolution drops and I don't want to do that and at 60Hz the Rift blur was unplayable just sitting in the hanger. (AMD card)
Last edited:
If you CTRL F you will get frame rate CTRL B for bandwidth
CTRL F you have to remove the left eye piece to see it. No idea for BW.
Starts off smooth
I can get mine to run in Direct mode (on 0.4.3) but I get a strange double image which looks like time-warp over compensating for movement. Extended mode looks and runs better but but head tracking seems laggy (on the outset.
So I uninstalled 0.4.3 <rebooted> and then re-installed 0.4.2.
Extended mode is now fantastic, sitting in the station it's silky, perfect tracking, 75Hz low persistence, the whole shebang and 3.02 is looking gorgeous. So happy. So I fly out, all looking great, jump, still good, SC to an space station, leave SC, still great, request to dock and pretty much as soon as I'm inside the space station things go awry, out of nowhere FPS dives to I'd say 0.5 fps and stays like that, docking becomes a nightmare, no matter what frame rate is obliterated even in the quit game menu :S
I've done this a few times and it's the same each time irrespective of the type of space station (although I haven't tried a titchy outpost). There clearly a bug somewhere, 2.06 was massively better performance-wise on my rig.
Spec's: i7 4790K @ 4.4Ghz, 16GB DDR3 @ 2133, Gigabyte Z97X-SLI Mb, Nvidia GTX 980 (reference design @ stock speed), main display @ 1280x1024 @75Hz, i7 cores un-parked, OVRServer_x64.exe elevated to high priority, Windows 7 SP1 Pro (fully patched to date). X52 Pro.
screen connected via Display Port, Rift connected via HMDI (and USB 2 for both the rift and it's camera), OS & ED installed on a 256GB Samsung 850 Pro.
I'm sad cos I need my elite fix, hell ED was the main reason I brought a DK2 (and then my PC...)
Gonna give it another go on Solo mode to see if it's some bizarre network issue. I'll report back.
I can get mine to run in Direct mode (on 0.4.3) but I get a strange double image which looks like time-warp over compensating for movement. Extended mode looks and runs better but but head tracking seems laggy (on the outset.
So I uninstalled 0.4.3 <rebooted> and then re-installed 0.4.2.
Extended mode is now fantastic, sitting in the station it's silky, perfect tracking, 75Hz low persistence, the whole shebang and 3.02 is looking gorgeous. So happy. So I fly out, all looking great, jump, still good, SC to an space station, leave SC, still great, request to dock and pretty much as soon as I'm inside the space station things go awry, out of nowhere FPS dives to I'd say 0.5 fps and stays like that, docking becomes a nightmare, no matter what frame rate is obliterated even in the quit game menu :S
I've done this a few times and it's the same each time irrespective of the type of space station (although I haven't tried a titchy outpost). There clearly a bug somewhere, 2.06 was massively better performance-wise on my rig.
Spec's: i7 4790K @ 4.4Ghz, 16GB DDR3 @ 2133, Gigabyte Z97X-SLI Mb, Nvidia GTX 980 (reference design @ stock speed), main display @ 1280x1024 @75Hz, i7 cores un-parked, OVRServer_x64.exe elevated to high priority, Windows 7 SP1 Pro (fully patched to date). X52 Pro.
screen connected via Display Port, Rift connected via HMDI (and USB 2 for both the rift and it's camera), OS & ED installed on a 256GB Samsung 850 Pro.
I'm sad cos I need my elite fix, hell ED was the main reason I brought a DK2 (and then my PC...)
Gonna give it another go on Solo mode to see if it's some bizarre network issue. I'll report back.
Exactly the same for me. I can fly out of a space station with everything silky smooth. Do a SC - and then fly back to the space station and suddenly it drops to about 3fps. Docking is nearly impossible and I've just given up after warping into the side of a launch pad.
Also when I stay away from space stations, performance just gradually seems to get worse and worse - as if there is a memory leak or something - until it becomes unplayable. It's usually after a couple of SC that it starts to jerk, judder and pause until it eventually just hangs or disconnects.
I've also downgraded back to 0.4.2 for the Oculus Runtimes as 0.4.3 seemed worse.
Last edited:
Net code issue?
Just done the whole process again, but in solo, starts off smooth like my original post, unlike my original post it stays smooth, went to Chango dock and er docked, just as great as when I set out from Styx, guess it's a netcode or serverside issue. Will be a shame to miss out on sharing the environment with others but until Frontier nail the problem it seems like my only option... still the game is playable again so that's a plus!
YMMV
Just done the whole process again, but in solo, starts off smooth like my original post, unlike my original post it stays smooth, went to Chango dock and er docked, just as great as when I set out from Styx, guess it's a netcode or serverside issue. Will be a shame to miss out on sharing the environment with others but until Frontier nail the problem it seems like my only option... still the game is playable again so that's a plus!
YMMV
Last edited:
Well I've got a modest PC and it handles pretty well... FX-6300, Radeon HD 7750 and 8 Gigs of RAM do the trick, most settings at the highest, except for reflections and AA (FXAA, if I supersample 1080p, lol i'd destroy the poor thing), and it goes at a smooth 60 fps most of the time, 45 at worst, except on big stations (the ones with trees on em), where it goes down to 15, almost unplayable
Rig:
i7 -4790k @4.00
8BG Ram (not OC)
AMD R9 290x (not OC).
DK2, Extended mode.
Settings: shadows low, blur off, ambient Oclution off, SMAA antialiasing On
with this new 3.02, stable 75 FPS everwhere, some times a few little stutters but that`s normal and im pretty sure is relate to network issues.
i7 -4790k @4.00
8BG Ram (not OC)
AMD R9 290x (not OC).
DK2, Extended mode.
Settings: shadows low, blur off, ambient Oclution off, SMAA antialiasing On
with this new 3.02, stable 75 FPS everwhere, some times a few little stutters but that`s normal and im pretty sure is relate to network issues.
You're right. I think people need to specify whether they are testing in Solo or Open play.
i7 4960 with dual 780's was getting 75 fps, but now dropping and stuttering near stations, minor before the patch, major since,
Sent in ticket
Sent in ticket