Don't know what you're talking about. Game runs absolutely fabulously over here in all places.
Everyone seems impressed with 1.3 performance but...
- Thread starter gapper4
- Start date
Don't know what you're talking about. Game runs absolutely fabulously over here in all places.
Thanks for your contributions guys.
In a nutshell, I have raised a formal ticket on this. Mostly because I have been so frustrated with QA's attempts to wipe off DK2 users when Frontier have NOT officially announced a blanket withdrawal of support for the DK2 (not yet anyway). Sofar they have only withdrawn support for SteamVR as the 'interface' to the DK2 (something that we know already since moving to SDK1.3).
This unwelcome external Stammer/Hitching occurs now and then regardless of the graphic settings (whether or not SS is high or low). I have all the usual things disabled like AO, AA etc. There are several people in this thread who have the same issue, with high spec hardware, so I am not delusional.
Adding SS 2.0 actually does improve things so it is not the performance of my graphic card that is the issue. I am hoping that it's just because the dev team have optimised for 90hz, as opposed to 75hz.
Based on ghcannon's post, I look forward to my CV1 arrival and hope that the issue will be gone once I'm running at 90hz.
Thanks for everyone's input on this. My focus of disappointment has not been with ED, or SDK1.3 which otherwise, is brilliant, it's been the bloody mindedness of QA.
Anyway, I'm off to do some more bounty hunting. I'm giving up trying to work with QA to help ED improve their VR performance. Someone else will have to run with this now as I have probably pi**ed QA-Donny off.
I'm happy to help others on this thread tho, just don't want to deal with QA. My specs are in my sig if you want to compare notes.
Food for thought, I moved my DK2 to the actual HDMI port on my 980ti (I used to use a DP/HDMI adapter). Things seem to have improved slightly, but that could just be a placebo I reckon.
In a nutshell, I have raised a formal ticket on this. Mostly because I have been so frustrated with QA's attempts to wipe off DK2 users when Frontier have NOT officially announced a blanket withdrawal of support for the DK2 (not yet anyway). Sofar they have only withdrawn support for SteamVR as the 'interface' to the DK2 (something that we know already since moving to SDK1.3).
This unwelcome external Stammer/Hitching occurs now and then regardless of the graphic settings (whether or not SS is high or low). I have all the usual things disabled like AO, AA etc. There are several people in this thread who have the same issue, with high spec hardware, so I am not delusional.
Adding SS 2.0 actually does improve things so it is not the performance of my graphic card that is the issue. I am hoping that it's just because the dev team have optimised for 90hz, as opposed to 75hz.
Based on ghcannon's post, I look forward to my CV1 arrival and hope that the issue will be gone once I'm running at 90hz.
Thanks for everyone's input on this. My focus of disappointment has not been with ED, or SDK1.3 which otherwise, is brilliant, it's been the bloody mindedness of QA.
Anyway, I'm off to do some more bounty hunting. I'm giving up trying to work with QA to help ED improve their VR performance. Someone else will have to run with this now as I have probably pi**ed QA-Donny off.
I'm happy to help others on this thread tho, just don't want to deal with QA. My specs are in my sig if you want to compare notes.
Food for thought, I moved my DK2 to the actual HDMI port on my 980ti (I used to use a DP/HDMI adapter). Things seem to have improved slightly, but that could just be a placebo I reckon.
Last edited:
I know exactly what he is on about.
1.3 is smooth on the DK2 and that's all it is. The sky looks dreadful, it's broken.
I'm using 0.8 because 1.3 looks terrible
Just to clarify we are talking about the DK2, not the CV1. And yeah i know its unsupported now.
Last edited:
Yeah, you can still run Elite with 0.8 and SteamVR, get the odd bit of stutter around planets but it's worth enduring because Space actually looks awesome and shadows and lighting are properly immersive.
I've exhausted all possible tweaks trying to get it to look tolerable on 1.3 but I haven't even got close.
Play it on 0.8 and then switch to 1.3. The difference is astronomical. Pun intended.
This is exactly what I'm getting on runtime 0.8 and 1.3. Everything is smooth, except for the periodic stutter every second. Driving me mad and can't seem to find the cause. As soon as I get my CV1 I will reinstall all and try again.
Did you ever get this fixed by the way?
(on Win10, i7-3770K@4,5GHz, 2xGTX970)
Last edited:
Please report it as a bug here .... https://forums.frontier.co.uk/forumdisplay.php?f=105
and raise a ticket here ... https://support.frontier.co.uk/open.php?topic=82.
Be prepared for some pushback because you have a DK2 (even though Frontier have not officially announced the dropping of support for DK2 users)
The more times it gets raised, the harder it is for them to ignore it.
Last edited:
Gents, I found something that helped me, so here goes. I had been using 0.5 with all the hacks and recommendations in the pinned thread in this forum, and then forgot that I had changed a whole bunch of settings for Elite through the NVidia control panel. Well, by resetting all of them to default, I found that performance improved fairly dramatically in-game with 1.3. Not as butter smooth as some people report but close enough. I can now run SS 1.5, SMAA, with Bloom, AO, and Blur off, but everything else maxed out, and the game is about 99.5% smooth. I still find it hard to believe that some people experience absolutely no hitching at all but my experience is now pretty close to that. Hope it helps.
Last edited:
Changed the GUI color, running a sweetfx plug-in, screen protectors and lowered gamma and GUI brightness. Looks 100 times better now.
It seems Oculus Home downclocks my GPU from 1.2GHz to 450MHz (nice!). If I close Home and run a benchmark, clock speed goes up again. Anyone come across this before?
Another find: if I turn off the DK2 while in Home, and then on again, GPU clock speed is set back ... to default. So, it works but it ignores any overclocking set previously. Next problem is find out how to set clocks back to what the user wants...
The plot thickens....
But, if that's the case with Oculus Home, why doesn't everyone experience hitching and framerate drops ?
I've got an (unsupported) ATI 7850 and a DK2, maybe it's the hardware combination triggering this. I've read elsewhere that Home fiddles with powersaving features on the fly, so this might be one (buggy) aspect of this.
That's interesting. Would a temporary fix (uh, bodge) be to change all your system power profiles to be aggressive/high performance? I was thinking I haven't encountered any downclocking of my cards, but then also people on similar configurations have been reporting better performance than I think I'm seeing. Will run Afterburner or something next time and keep an eye on it.
Does sweetfx now work with direct mode? What screen protectors are you using?
Not actually sure if SweetFx runs properly as it errored the last time I fired it up. The screen protectors are 'Anker' for IPad Air.
I've read that Home changes the Windows power profile when you put on the CV1 (whose proximity sensor can tell if you are wearing it or not). There is no such capability on the DK2 and accordingly, I have not seen Home changing my Windows power profile (which is set to performance at all times).
As to GPU power profiles, I have no idea how to check or change those for my hardware. In any case, it looks like Home tries to be clever and reduce maximum clock frequencies for my card -- I can see why it might do that on a mobile device, but on a PC it just looks stupid.