As a test try disabling hyperthreading. I had problems with hitching with my i7 in the latest build. Disabled hyperthreading and it went away.
Everyone seems impressed with 1.3 performance but...
- Thread starter gapper4
- Start date
As a test try disabling hyperthreading. I had problems with hitching with my i7 in the latest build. Disabled hyperthreading and it went away.
Never tried to be honest. I just disabled HT in the BIOS. Once disabled you should only see the 4 physical cores active in Windows.
Sorry for the noob question, but how do you disable HT?
It will be in the advanced CPU settings/features in your BIOS labelled something along the lines of :
Intel Hyperthreading Technology
Just disable it, save your BIOS settings and boot to windows.
Thanks HeravyGroovez, disabling HT it didn't help in my case.
Perhaps it depends on a lot of hardware factors.
I continue to get the least issues with VRHigh and SS2.0.
It's shaping up to look like external Stammer/Hitching (regardless of graphic settings), might be confined to the DK2 75Hz.
We need to hear from more CV1 users who have that 'specific' issue in order to make a case to the devs.
If the stammer totally goes away when you drop the graphic settings, then that is not the issue I'm talking about.
Perhaps it depends on a lot of hardware factors.
I continue to get the least issues with VRHigh and SS2.0.
It's shaping up to look like external Stammer/Hitching (regardless of graphic settings), might be confined to the DK2 75Hz.
We need to hear from more CV1 users who have that 'specific' issue in order to make a case to the devs.
If the stammer totally goes away when you drop the graphic settings, then that is not the issue I'm talking about.
Last edited:
I find the training missions free from stammer, would that rule out the hardware?
One would think so, but until we have a whole lot of CV1 owners complaining, it looks like QA have washed their hands of the issue.
QA imply that the DK2 is no longer supported (and user support requests regarding VR issues seem to be dismissed if they are using DK2s), but I'm confused, as I cannot find an official statement from frontier declaring that.
QA imply that the DK2 is no longer supported (and user support requests regarding VR issues seem to be dismissed if they are using DK2s), but I'm confused, as I cannot find an official statement from frontier declaring that.
Last edited:
You shouldn't touch that setting at all. It might, in fact, contribute to your issues. Reset it to default.
The refresh rate has nothing to do with it either. I'd do a check on your CPU & GPU frequencies (not usage) when you're in-game to see if components are running as they should be.
Also, in ED's settings make sure you disable any bluring & DoF (can't remember if we had it) and make sure not to select FXAA as it's a technique that involves bluring all iased pixels. In fact - if you're running supersampling, don't choose antialising at all as its effect on performance will scale in a way you don't want.
You can also lower shadows to the settings before Ultra.
I'm running drivers 364.51 with no problems whatsoever ... if that helps you.
Last edited:
Hello ghcannon,
I am a bit bewildered by the support team who seem to be dismissing the subject of this thread as a DK2 issue.
I am wondering if you can help me confirm something.
Several of us DK2 users in this thread are experiencing external stammer/hitching in asteroids and around ships etc. It comes and goes and doesn't seem related to the graphic settings as it can still appear when you adjust things way down.
Do you experience any of this with your CV1?
This is not about having settings too high which affects the framerate, this is a smoothness problem with settings that shouldn't have issues on high spec hardware.
I'd really appreciate your feedback.
thanks
As a side note, I currently find VRHigh with SS2.0 to have the least of these issues when flying in asteroid fields, but the problem still appears now and then.
I am using the latest nVidia drivers. Should I think about rolling back to 364.51?
I am a bit bewildered by the support team who seem to be dismissing the subject of this thread as a DK2 issue.
I am wondering if you can help me confirm something.
Several of us DK2 users in this thread are experiencing external stammer/hitching in asteroids and around ships etc. It comes and goes and doesn't seem related to the graphic settings as it can still appear when you adjust things way down.
Do you experience any of this with your CV1?
This is not about having settings too high which affects the framerate, this is a smoothness problem with settings that shouldn't have issues on high spec hardware.
I'd really appreciate your feedback.
thanks
As a side note, I currently find VRHigh with SS2.0 to have the least of these issues when flying in asteroid fields, but the problem still appears now and then.
I am using the latest nVidia drivers. Should I think about rolling back to 364.51?
Last edited:
I'm going nuts trying to get QA to help us with this issue. You don't have to be a lawyer to understand that Frontier have NOT announced that they no longer support users with DK2s. Only the use of DK2 via SteamVR.
https://forums.frontier.co.uk/showthread.php?t=240707&p=3751852&viewfull=1#post3751852
https://forums.frontier.co.uk/showthread.php?t=240707&p=3751852&viewfull=1#post3751852
Last edited:
Have you tried disabling Super Sampling as it alreadys has SS of 1.4 automatically. By setting it 2.0, it may cause performance issues.
My performace with 0.5 was good, nice and smooth with just the occasional stutter in sc but with 1.3 it's even better, lovely and smooth even in sc and the warp tunnels are flawless now
Hi mate
I've spend a fair amount of time in a High-RES site with the CV1 and can definitely confirm I get no noticeable stutters or abnormal frame latency. Definitely nothing of the likes that ppl on the past couple pages of this thread have described.
It's really hard to diagnose the problem you're having. If it's happening only in ED and with the DK2, then I'd suspect an integration issue on ED's side. This means there's likely a bug in the way ED is using Oculus' compositor interface. It would also be nice to know all you guys' hardware to see if we can find some commonality.
However I would have imagined ED to be fairly device agnostic and letting the SDK handle the complexity of different HMDs .. with the exception of render target size.
You could try playing around with some settings in the driver, like # of pre-rendered frames. Also force-stop any extra 'goodies' like AA and AF. And, ofcourse, revert to an older driver.
I'll give this a closer look too, but my DK2 experience has so far been butter smooth. I'll do some more testing in an asteroid field, Res site etc and report back.
One thing @Gamer101, you say you're running VR High and SS2.0?! That's pretty taxing on the GPU dude and i'm sure we've had reports of SS not exactly working as it previously did anyways.
I'd drop that back for starters and see how you go.
One thing @Gamer101, you say you're running VR High and SS2.0?! That's pretty taxing on the GPU dude and i'm sure we've had reports of SS not exactly working as it previously did anyways.
I'd drop that back for starters and see how you go.
I've tried and I'm sure @Gamer101 has as well, turning all the graphic options to Off or Low and disabling whatever other options we can. It really looks vomit inducing at that level but the stammering is still there and @Gamer101 is right in that the higher the settings are the less the stammer is.
If it really is just a DK2 issue then I can live with that until my CV1 arrives but it seems other DK2 owners are doing just dandy???
As ghcannon has said, could do with a hardware comparison to try and narrow it down.
I assume you have ambiant occlusion disabled in graphics settings? it's the only feature that seems to cause any slowdown for me
Ah, yes, sorry dudes, i see that now. Ok, i'll still give this a proper test myself and report back so that we can see if it is some kind of hardware thing or the DK2 itself having problems with this current build.
Why are people unimpressed with 1.3SDK? The SDK isn't the problem, it's Frontiers Ugly oculus support that is literally preventing hundreds of rift owners from playing in VR.
All other Games/Apps appear to run and render absolutely fine, no smearing etc.
I gotta say, I went out if my way to ensure most if my VR playtime is in Elite, now I've literally stopped playing Elite because of its rubbish oculus support, I'm so unhappy with Frontier.
All other Games/Apps appear to run and render absolutely fine, no smearing etc.
I gotta say, I went out if my way to ensure most if my VR playtime is in Elite, now I've literally stopped playing Elite because of its rubbish oculus support, I'm so unhappy with Frontier.
Last edited:
Citation needed. Working fantastically here, apart from the smearing.