ED and the Oculus Rift Developers Kit 2 (DK2) Discussion Thread
Are you sure positional tracking is working. If the camera goes out for some reason the colors get this faded/missing look. It happened in the last beta as well.
Green text on black would present the clearest text resolution for ED cockpit menus.
As John Carmack recently stated at Oculus Connect
. Green text on a black background would produce the clearest readable text in the rift. This is because the Samsung Super AMOLED screens produce 2x the amount of Green organic material over the Red and Blue organic material.I am seeing this orange blur right from the start on the main menu text, not sure if turning off bloom would help (it might have been already off since I was playing on low setting).
But.. I can't check anything at the moment since the game crashes right after the main menu loads since 2.02.
If you have a spare HMDI cable lying around, you might try swapping out the one that came with the rift. There were some quality issues with the rift cables. I actually had to send my first dk2 back because the cable was bad.
You should also check and make sure that you don't have any useless services or programs running in the back ground. People often forget to stop their virus software while running demanding games.
Last edited:
Got beta 2 working after a round of fiddling with my monitor options.
Framerate has improved a bit and there's loads of new content, but one graphical issue is driving me nuts! It's like the brightness and gamma have got a HUGE boost and now everything looks artifacted like low bitrate video. Tried adjusting the gamma, but it does nothing for me. Any suggestions?
Framerate has improved a bit and there's loads of new content, but one graphical issue is driving me nuts! It's like the brightness and gamma have got a HUGE boost and now everything looks artifacted like low bitrate video. Tried adjusting the gamma, but it does nothing for me. Any suggestions?
Since the game is largely unplayable at the moment, I did some messing around with graphical settings in the docking tutorial.
Enabling SLI and forcing AFR2 per this thread seems to work (edit: I have 2 EVGA 780 GTX SC 6Gb cards):
https://forums.frontier.co.uk/showthread.php?t=44375
MSAA x2/x4 worked at a decent speed, but there was something hinky about it, which apparently is a known issue, I preferred the game with it off. I was even able to turn on SMAA and maintain a solid frame rate (in the tutorial anyway) - but it took a few seconds after startup for the frame rate to settle down.
That said, when I finally managed to get into Open Play, the frame rate was terrible, there was unplayable ghosting, like there was a second frame about a quarter second behind the first and it didn't seem to go away if I left it.
In Solo Play, for some reason, I started out in space, even though I was docked at Freeport when I last logged out of Open Play. The planetary textures were completely corrupted, all stripes. I tried jumping to Eranin, but got stuck in hyperspace which appeared to only have the tunnel geometry present, none of the additional texture layers showed up.
After that, I gave up.
Enabling SLI and forcing AFR2 per this thread seems to work (edit: I have 2 EVGA 780 GTX SC 6Gb cards):
https://forums.frontier.co.uk/showthread.php?t=44375
MSAA x2/x4 worked at a decent speed, but there was something hinky about it, which apparently is a known issue, I preferred the game with it off. I was even able to turn on SMAA and maintain a solid frame rate (in the tutorial anyway) - but it took a few seconds after startup for the frame rate to settle down.
That said, when I finally managed to get into Open Play, the frame rate was terrible, there was unplayable ghosting, like there was a second frame about a quarter second behind the first and it didn't seem to go away if I left it.
In Solo Play, for some reason, I started out in space, even though I was docked at Freeport when I last logged out of Open Play. The planetary textures were completely corrupted, all stripes. I tried jumping to Eranin, but got stuck in hyperspace which appeared to only have the tunnel geometry present, none of the additional texture layers showed up.
After that, I gave up.
Last edited:
Got the DK2 working now but using that link, which is:
http://forums.frontier.co.uk/showthread.php?t=43779
Thanks Juniper (and others)
This!!!!!
Have you tried setting the following in the control panel for nVidia (not sure about ATI cards)
"I followed sepian78 tip from reddit and changed some settings in Nvidia Control Panel under 'Adjust desktop Colour Settings':
For All Channels: Brightness +55% Gamma +0.95 Digital Vibrance +55%"
Anyone else get it to work perfectly for half a second before the resolution gets crushed?
A few times while I was playing in the Graphics screen, I would get everything looking crystal clear, then suddenly during the "ok? yes/no" countdown the resolution goes bad and everything doesn't look so awesome anymore.
It's close, but there's judder, chromatic abberation, lots of the usual weirdness... But more than once it was looking great for half a second before deciding to not look awesome :/
for people having issues getting the display to detect, keep the Oculus service running.
A few times while I was playing in the Graphics screen, I would get everything looking crystal clear, then suddenly during the "ok? yes/no" countdown the resolution goes bad and everything doesn't look so awesome anymore.
It's close, but there's judder, chromatic abberation, lots of the usual weirdness... But more than once it was looking great for half a second before deciding to not look awesome :/
for people having issues getting the display to detect, keep the Oculus service running.
If anyone gets the issue when the first loading screen looks weird with a kind of green tint then there is something up and you close the game down and maybe restart your PC and try again. I had this at points last night and after a few attempts it seemed to go away.
I was getting this issue prior to Beta 2 as well when downscaling from 1440p so I assume it's related somehow.
I was getting this issue prior to Beta 2 as well when downscaling from 1440p so I assume it's related somehow.
I've been incredibly lucky, aside from not being able to play in multi-player, my DK2 has worked flawlessly in B2.
I have experienced the black screen of death (BSOD) which I believe is network related since a few times I've got the bsod followed by connection failure.
Otherwise, my personal experience has been wonderful so far. I was going to SLI my gtx 770's but, no need to. "Juttering" is totally performance related, IMO. If you're experiencing "jutter" either lower the graphics settings or get a better GPU because that's all that will fix it.
I have experienced the black screen of death (BSOD) which I believe is network related since a few times I've got the bsod followed by connection failure.
Otherwise, my personal experience has been wonderful so far. I was going to SLI my gtx 770's but, no need to. "Juttering" is totally performance related, IMO. If you're experiencing "jutter" either lower the graphics settings or get a better GPU because that's all that will fix it.
Last edited:
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
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
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.
Where is this setting?
Options--->Graphics menu
It was at the top of the graphics settings menu - or was, anyway, I dont know if its still in Beta 2.02, since I didnt get that working again until this morning, but didnt have time to try anything out :*(
Wow must have missed that somehow. Has it always been there??
Definitely new to Beta 2, I think.