ED and the Oculus Rift Developers Kit 2 (DK2) Discussion Thread
Cool thanks.
Sorted itself out during a few boot cycles. I think it's related to new oculus runtime and new firmware. I had multiple problems like overexposure, low persistance not working, drifting headtracking and suddenly they were all gone and everything is almost back to normal. (game is a bit darker than it used to be, have to play with gamma a bit and see if i get it to work)
I had expected more performance boost with beta2 to enable me to use oversampling, but it's still juddery in stations with med settings and msaa.
I'm quite dissapointed that r290x doesn't have the oomph to play this with oversampling
The game itself is super crashy right now. You'd better stay in one system to avoid any crashes. Everytime I hyperjump it crashes so I'm stuck in i bootis.
Another surprise was the character wipe. I didn't have much, kitted cobra and 200k credits, but it really sucks to start all over again. I would have hoped to be reimbursed for my virtual belongins
Last edited:
My first thought was "oh God, station drawing bug"
My thoughts (only played 2.02, not 2.01 or B2.0) on the Rift:
- I love the dust on the canopy glass. I know it was overdone and turned down compared to 2.01 and 2, but for me, 2.02 is superb.
- System map is massively bugged for me, but awesome nevertheless. I can see the planets out to my right, looking stunning in 3D, but have weird orange swirls everywhere
- Galaxy map is hard to read and hard to select bodies as well. It also seems jerky as hell
- The new cockpit instruments seem harder to read for me. Sure the sharpness is up on 1.06, but the lack of contrast and the weird background colour they use on the instruments is a step back for me. It's almost like the Rift has to alias between 2 colours to achieve the colour they've chosen.
- I'm getting very poor FPS on 2.02. I have a feeling that for some reason I was vsync'd at 60hz (from my monitor) rather than 75 for the Rift. I was still enjoying myself so much that I didn't quit out to fix it. I'll have a play tonight to try and improve it.
- It's made me want a GTX980 regardless,
- EDIT - annoying that leaning in to the side menus for a clearer look makes them vanish.
Last edited:
Another surprise was the character wipe. I didn't have much, kitted cobra and 200k credits, but it really sucks to start all over again. I would have hoped to be reimbursed for my virtual belongins
It was a little shame, but hey ho.
What I noticed is that my kill count was NOT wiped - I started with 80 - but that I was still ranked as Harmless. Does anyone know the kill count needed to get to mostly harmless?
This does get annoying fast, hopefully they'll fix this and other issues
Idk, I have just shy of 750 kills but, still harmless.
Hmm, not a good sign. In the original game, you'd be "Competant" with that and almost at "Dangerous".
Unless there is a behind the scenes counter which is now counting since the start of B2. After all, you can progress through the ranks (apparently) with more than just killing in ED.
Mine had also carried over when I first played beta 2, but when I checked this morning it had reset..
Was quite disappointed when I tested beta 2 with the DK2 initially, as I was now getting judder where there was none previously (I only suffered teeny tiny bits of judder in stations - now was getting loads in and out of stations)
I went through settings switching things off>medium>low but nothing was making a difference to the visible framerate display - hovering between 60-68. Even switching on ambient occlusion made only a hit of 2-3 fps - whereas previously I'd had to switch it off (and set shadows to medium) to keep things judder free.
I noticed there were some new graphics options, played with them... no change.
Then I spotted "blur = on" Now, I know that blur is often used to soften the blow of lowish framerates... so I tried switching it off.
The framerate is now locked absolutely solid at 75fps
MUCH smoother than beta 1, and with my settings nudged that little bit higher than before too.
\o/
i5 45670K @ 4.2ghz R9 290 OC, 16gb ram.
Catalyst 14.9
..and then ofcourse I got the update to 2.02, and everything broke, lol
Thank you for this tip, now its super smooth in the stations, i never got this in Beta1
However on the astroid belts it choppy as hell, but that would be fixed i hope soon.
i5 4790
8GB Ram
R9 290
I have a second card for crossfire, but i am getting rid of it, it just does not work with VR, to many issues
PS: how did you get Catalyst 14.9 to work? its a well know problem with the DK2, black screen and BSOD
Cheers
Was quite disappointed when I tested beta 2 with the DK2 initially, as I was now getting judder where there was none previously (I only suffered teeny tiny bits of judder in stations - now was getting loads in and out of stations)
I went through settings switching things off>medium>low but nothing was making a difference to the visible framerate display - hovering between 60-68. Even switching on ambient occlusion made only a hit of 2-3 fps - whereas previously I'd had to switch it off (and set shadows to medium) to keep things judder free.
I noticed there were some new graphics options, played with them... no change.
Then I spotted "blur = on" Now, I know that blur is often used to soften the blow of lowish framerates... so I tried switching it off.
The framerate is now locked absolutely solid at 75fps
MUCH smoother than beta 1, and with my settings nudged that little bit higher than before too.
\o/
i5 45670K @ 4.2ghz R9 290 OC, 16gb ram.
Catalyst 14.9
..and then ofcourse I got the update to 2.02, and everything broke, lol
The few mins I managed to get in I had the same judder problem. I'll give it a try when I get the chance. Hopefully in the next fortnight.
When I start the game it loads in a window on my primary monitor in Oculus format (the image split and curved for each eye), which then goes to full screen. Once I accept the Oculus use warning the game menu loads and the application freezes, I have to kill the process in Task Manager.
Is there a way to delete or reset the games setting to see if it's an issue with the Oculus implementation or some issue the game is having on my system?
Is there a way to delete or reset the games setting to see if it's an issue with the Oculus implementation or some issue the game is having on my system?
Turn off the rift.
Thanks, it still locks up on the menu, I guess this is a known issue.
First post here. Im playing with the Oculus Rift DK2, my pc its i72600k, r9 280x, 16 gb of ram, good motherboard and a 600w PSU.
In beta 1 i played with the rift, everything on minimum, it worked fine everywhere but in stations. in beta 2 its much, MUCH smoother and looks better, but.
My PC turns off while playing.
After a while of playing, my PC just turns off, no alarm, no anything, it just turns off the same way if you just unplugged it. CPU temps are fine, and GPU seems fine too, its not hot, but it doesnt make the same inmense noise it made on Beta 1, where after 5 minutes of play the fans on the GPU would be maxed and the GPU temps at 80 celsius.
On beta 2 fans dont get as fast, but the PC just crashes.
Ive run both prime95 stress test and furmark for like half an hour and the PC its fine and not overheating, yet somehow ED on the rift turns off the PC randomly.
In beta 1 i played with the rift, everything on minimum, it worked fine everywhere but in stations. in beta 2 its much, MUCH smoother and looks better, but.
My PC turns off while playing.
After a while of playing, my PC just turns off, no alarm, no anything, it just turns off the same way if you just unplugged it. CPU temps are fine, and GPU seems fine too, its not hot, but it doesnt make the same inmense noise it made on Beta 1, where after 5 minutes of play the fans on the GPU would be maxed and the GPU temps at 80 celsius.
On beta 2 fans dont get as fast, but the PC just crashes.
Ive run both prime95 stress test and furmark for like half an hour and the PC its fine and not overheating, yet somehow ED on the rift turns off the PC randomly.
Welcome to the forums
I know nothing about this, but would imagine its a power supply problem and the maybe the rift is pulling too much off one of the bars.
I know nothing about this, but would imagine its a power supply problem and the maybe the rift is pulling too much off one of the bars.
Thermal paste not applied or power supply
I'm going home now, I really hope to play tonight
If you dive into the appdata directory that contains elite, there's a few xml files kicking around.
Under either graphics or the AppConfig.xml file you should see a section for display that contains the setting for which monitor to use.
Failing that, just try deleting the xml file and elite should revert to a standard monitor setup.
Freezing on the menu is a known bug in 2.02. Many people have it, including me.
Just have to wait for 2.03, unless you want to attempt a hacky fix, but I wouldn't bother myself.
Leave your files and network settings alone and wait for a fix.