Possibly
0.6 absolutely would not work with Elite on my setup no matter what I tried. 0.5 works perfectly. Maybe my 7950 is to blame - who knows?
Important Notice Regarding Oculus 0.6 SDK
- Thread starter Frontier QA
- Start date
Possibly
0.6 absolutely would not work with Elite on my setup no matter what I tried. 0.5 works perfectly. Maybe my 7950 is to blame - who knows?
I was able to get direct to somewhat work with 0.6.0 but to much judder. extended just flashed, even powering off and on the DK2 wouldn't stop the flashing.
rolled back to 0.5.0 and it works fine. My choice seems to be ETS2 with judder or E with judder or many reboots everytime I want to switch games.
rolled back to 0.5.0 and it works fine. My choice seems to be ETS2 with judder or E
with judder or many reboots everytime I want to switch games.I was able to get direct to somewhat work with 0.6.0 but to much judder. extended just flashed, even powering off and on the DK2 wouldn't stop the flashing.
rolled back to 0.5.0 and it works fine. My choice seems to be ETS2 with judder or E
On my system the trick to getting 0.6 to work or direct mode for that matter is all about selecting the right display with EDDS launcher (I have to select tertiary in direct mode). As you correctly state, direct mode has a lot of judder. Im not sure if that can be sorted via forcing the GPU driver in certain ways but I think it's futile for now. Extended mode works a lot better and you can disable the main display in Windows.
- - - Updated - - -
You will probably have to ask that question in a thread where the developers are active. I don't think this thread is one of them.
![[VR] Mad Mike](https://forums-cdn.zaonce.net/data/avatars/m/27/27910.jpg?1553527108){kind=avatar}
I was able to get direct to somewhat work with 0.6.0 but to much judder. extended just flashed, even powering off and on the DK2 wouldn't stop the flashing.
rolled back to 0.5.0 and it works fine. My choice seems to be ETS2 with judder or E
I am in the same boat.
I am itching to try ETS2 now it supports 0.6, but given I play ED in 90% of my gaming when not with mates, it is not a sacrifice I am ready to make. I would love to hear if any headway is being made with elite and 0.6. Last I heard Frontier Devs ARE in touch with oculus about it.
forget about 0.6
all the cool kids play with 0.601 now
https://forums.oculus.com/viewtopic.php?f=26&t=24613
Oculus PC SDK 0.6.0.1 Beta
This release introduces queue ahead. Queue ahead improves CPU and GPU parallelism and increases the amount of time that the GPU has to process frames.
New Features
Added queue ahead. Queue ahead improves CPU and GPU parallelism and increases the amount of time that the GPU has to process frames. For more information, see Queue Ahead.
Added the Debug HUD, which provides useful information while using the HUD. For more information, see Performance Head-Up Display. To enable it in OculusWorldDemo, press F11.
Added two samples:
ORT (Direct Quad)—verifies and demonstrates direct quads.
ORT (Performance HUD)—demonstrates the performance HUD.
Added additional menu options to OculusWorldDemo.
Known Issues
Pre-Kepler NVidia GPUs might return "No display attached to compositor" or "SubmitLayers failed" errors, which can result in a black screen for some applications. NVidia GTX 600 GPUs and later use the Kepler or Maxwell architectures.
Some Intel GPUs might return "No display attached to compositor" or "SubmitLayers failed" errors, which can result in a black screen for some applications.
Standard RGB (sRGB) is not properly supported.
Timeout Detection Recovery (TDR) is not properly supported.
Windows 10 is not yet supported.
Extended mode does not currently work with AMD GPUs due to issues in the AMD drivers.
For NVidia GPUs, please use driver version 350.12. The latest NVidia driver is unstable with the runtime.
all the cool kids play with 0.601 now
https://forums.oculus.com/viewtopic.php?f=26&t=24613
Oculus PC SDK 0.6.0.1 Beta
This release introduces queue ahead. Queue ahead improves CPU and GPU parallelism and increases the amount of time that the GPU has to process frames.
New Features
Added queue ahead. Queue ahead improves CPU and GPU parallelism and increases the amount of time that the GPU has to process frames. For more information, see Queue Ahead.
Added the Debug HUD, which provides useful information while using the HUD. For more information, see Performance Head-Up Display. To enable it in OculusWorldDemo, press F11.
Added two samples:
ORT (Direct Quad)—verifies and demonstrates direct quads.
ORT (Performance HUD)—demonstrates the performance HUD.
Added additional menu options to OculusWorldDemo.
Known Issues
Pre-Kepler NVidia GPUs might return "No display attached to compositor" or "SubmitLayers failed" errors, which can result in a black screen for some applications. NVidia GTX 600 GPUs and later use the Kepler or Maxwell architectures.
Some Intel GPUs might return "No display attached to compositor" or "SubmitLayers failed" errors, which can result in a black screen for some applications.
Standard RGB (sRGB) is not properly supported.
Timeout Detection Recovery (TDR) is not properly supported.
Windows 10 is not yet supported.
Extended mode does not currently work with AMD GPUs due to issues in the AMD drivers.
For NVidia GPUs, please use driver version 350.12. The latest NVidia driver is unstable with the runtime.
Last edited:
Does that update with with ED?? Please say yes...
As I posted in another thread, I upgraded to 0.6.0.1 and downgraded my NVidia Drivers to recommended ones 350.12 and for me ED work perfectly extended mode. I don't see a differences with 0.5.0.1 (fps, quality, etc.) and all work fine
In any case, it took few minutes to downgrade to 0.5.0.1 if the last version don't work for you, so you can make a quick test.
I tested also lot of demos and all worked fine, the only problem I meet is with the Desktop scene in the Oculus configuration screen, this one have a regular lag, exactly once per second. All other games/demos I tested work perfectly!
In any case, it took few minutes to downgrade to 0.5.0.1 if the last version don't work for you, so you can make a quick test.
I tested also lot of demos and all worked fine, the only problem I meet is with the Desktop scene in the Oculus configuration screen, this one have a regular lag, exactly once per second. All other games/demos I tested work perfectly!
Demo worked fine but i only get a white screen in extended mode. Some process didn''t respond and when i killed it the oculus service stopped working. Direct works but choppy. Rolled back to specs in my sig. Works fine again.
Last edited:
finally could not wait any longer, I wanted to check out ETS2 since it was updated to 0.6 (its great btw) and DiRT rally is also now on it.
went to 6.0 as there are reports that 6.1 breaks ETS2, however that is for another thread.... elite however.....
seems perfectly playable in 6 in extended mode. Performance has certainly taken a turn for the worse in it, however in my fairly high end rig it is more than playable. I was planning to go back to 5 for elite, but i do not think i will bother, 6 will do me fine for now, though i do hope FD are still working on improving elite for the recent oculus drivers.
PS i too get a blank white screen in extended mode....
went to 6.0 as there are reports that 6.1 breaks ETS2, however that is for another thread.... elite however.....
seems perfectly playable in 6 in extended mode. Performance has certainly taken a turn for the worse in it, however in my fairly high end rig it is more than playable. I was planning to go back to 5 for elite, but i do not think i will bother, 6 will do me fine for now, though i do hope FD are still working on improving elite for the recent oculus drivers.
PS i too get a blank white screen in extended mode....
Last edited:
No word yet, but I'm playing it in 6.0.1 Dirct mode. I can't get it to work in Extended under that, but Direct works flawlessly*, so I'm happy.
*as flawlessly as anything with the DK2
*as flawlessly as anything with the DK2
Got a Fury X and installed Catalyst 15.7. Now everything is fine for me in extended mode for SDK 0.6.0.1. But I don't know whether it was the upgrade to the new card (from hd 9750) or the updated driver. Direct mode has no noticalbe headtracking latency for me now but I can rise the details higher in extended.
Last edited:
Everything works* with 6.0.1 and latest AMD Catalyst (either "Omega" or latest Beta driver) in Extended mode, except for Virtual Desktop. If you want to keep using that with AMD cards, don't upgrade from Oculus runtime 5.x. Whenever I tried loading E with DK2 set to Direct Mode, I got a crash to error report immediately. Extended works better with E from what I've read anyway though.
This is with a 290X and Windows 8.1, btw.
*I do get display freezes occasionally that either require force quitting Elite through Task Manager or (once) hard resetting my computer. I'm not sure if they're any more or less frequent than the sort of things I was getting before, however. I think they might be AMD display driver issues rather than E-specific problems.
with DK2 set to Direct Mode, I got a crash to error report immediately. Extended works better with E from what I've read anyway though.This is with a 290X and Windows 8.1, btw.
*I do get display freezes occasionally that either require force quitting Elite through Task Manager or (once) hard resetting my computer. I'm not sure if they're any more or less frequent than the sort of things I was getting before, however. I think they might be AMD display driver issues rather than E
-specific problems.
The framerate is way worse with 6.01 than with 5.01 for me, especially in or near stations, and like GuyVer_MS the fonts seem less readable. I only have a GTX660, but I was able to run the game at a solid 30FPS , going down to 18-30 near or in stations. With 6.01 the framerate has been <10 near stations, and barely reaches 30 while in open space.
In case you wonder, the game is actually very enjoyable in VR at 30fps, as long as there is no big fluctuation. Near stations I have to take care not to move my head too fast, but it is (or was) bearable.
This is all in Direct Mode, using the 350 nvidia drivers. Extended doesn't work at all with 6.01 :/
It seems like I also get more weird position tracking jumps and stuttering than I did with 5.0.1.
In case you wonder, the game is actually very enjoyable in VR at 30fps, as long as there is no big fluctuation. Near stations I have to take care not to move my head too fast, but it is (or was) bearable.
This is all in Direct Mode, using the 350 nvidia drivers. Extended doesn't work at all with 6.01 :/
It seems like I also get more weird position tracking jumps and stuttering than I did with 5.0.1.
FYI:
I'm finding everything unplayable with SDK 0.6.0.1 in Direct Mode, there's just way too much ghosting going on, I see two copies of the scene regardless of what settings I try, Extended Mode is non functional.
Downloading 0.5.0.1 Beta now and will revert to that.
Edit: Yep, 0.5.0.1 Beta in Extended Mode works perfectly.
I'm finding everything unplayable with SDK 0.6.0.1 in Direct Mode, there's just way too much ghosting going on, I see two copies of the scene regardless of what settings I try, Extended Mode is non functional.
Downloading 0.5.0.1 Beta now and will revert to that.
Edit: Yep, 0.5.0.1 Beta in Extended Mode works perfectly.
Last edited: