I too have this issue, I find moving out of the camera's range and back in sorts it out for a period of time then it returns. I'm sure it has started happening since the last patch.
Rift Judder and FPS discussion thread.
- Thread starter Viajero
- Start date
I too have this issue, I find moving out of the camera's range and back in sorts it out for a period of time then it returns. I'm sure it has started happening since the last patch.
Just what the heck do people mean by "judder"
I've used the term without really thinking but then asked myself this very obvious question. Is it the DK2 not moving completely smoothly when swinging your head ? Is it micro hangs around planets or in stations ? Is is random shaking of your view ?
I'm asking because, well, my system is pretty good but certainly not up to what some of you guys have. I run the game in Extended Mode, with an i7 870 stock and a pretty cheap MSI motherboard, along with an 850 watts power supply, an MSI GTX970 OC (not the Gaming version) which I've overclocked using MSI Afterburner, a 500G Samsung SSD, and 12 gigs of Kingston RAM. I also make use of SweetFX and green UID.
My in-game settings are maxed (other than ambient occlusion and bloom, which are off because I don't like the effect) and movements in the cockpit are silky-smooth, if a bit low-res, at 1080. I've tweaked the game in NVCP and in-game to run at the NVidia DSR 1.78 (essentially 2.5K), with max Oculus Rift settings and everything else at max. There is slight latency when swinging my head wildly in-station, and occasionaly micro hangs when approaching a planet but, other than that it runs like greased lightning. Yes, it's not *completely* smooth *all the time* but it's a trade-off between visuals and performance that doesn't bother me.
So, are you guys perhaps too demanding ? Not saying that you have no issues at all but I find it hard to believe that people with systems much, much better than mine find the game unplayable, or nearly so. This is, after all, still an experimental tech not optimized for commercial use.
I've used the term without really thinking but then asked myself this very obvious question. Is it the DK2 not moving completely smoothly when swinging your head ? Is it micro hangs around planets or in stations ? Is is random shaking of your view ?
I'm asking because, well, my system is pretty good but certainly not up to what some of you guys have. I run the game in Extended Mode, with an i7 870 stock and a pretty cheap MSI motherboard, along with an 850 watts power supply, an MSI GTX970 OC (not the Gaming version) which I've overclocked using MSI Afterburner, a 500G Samsung SSD, and 12 gigs of Kingston RAM. I also make use of SweetFX and green UID.
My in-game settings are maxed (other than ambient occlusion and bloom, which are off because I don't like the effect) and movements in the cockpit are silky-smooth, if a bit low-res, at 1080. I've tweaked the game in NVCP and in-game to run at the NVidia DSR 1.78 (essentially 2.5K), with max Oculus Rift settings and everything else at max. There is slight latency when swinging my head wildly in-station, and occasionaly micro hangs when approaching a planet but, other than that it runs like greased lightning. Yes, it's not *completely* smooth *all the time* but it's a trade-off between visuals and performance that doesn't bother me.
So, are you guys perhaps too demanding ? Not saying that you have no issues at all but I find it hard to believe that people with systems much, much better than mine find the game unplayable, or nearly so. This is, after all, still an experimental tech not optimized for commercial use.
Last edited:
What I call judder is the head movement test you describe, the image aren't following along fast enough.
After following the stickied VR setup by drkaii I'm at 2x DSR in Nvidia settings, in-game settings on max except a select few that I turn off. It's silky creamy butter smooth in space with this setting, it's like not having the Rift on. But in asteroid fields, near planets and in station, there's some tiny stuff. (Planets stutter heavily).
I think I'll try some micro tweaking and OC a bit. (i5 4670k, 32GB RAM, GTX 970 and SSD)
After following the stickied VR setup by drkaii I'm at 2x DSR in Nvidia settings, in-game settings on max except a select few that I turn off. It's silky creamy butter smooth in space with this setting, it's like not having the Rift on. But in asteroid fields, near planets and in station, there's some tiny stuff. (Planets stutter heavily).
I think I'll try some micro tweaking and OC a bit. (i5 4670k, 32GB RAM, GTX 970 and SSD)
Ya I think when Oculus is talking about judder the are talking about the blur effect that happens when you move your head left or right because the image doesn't update fast enough, and your brain blurs the images together. Which can cause nausea, but there is a lag where the 3d images jump because the game or image isn't update briefly, I find this effect much more nauseating than the blurring. In the DK2 the blurring is almost completely gone. I agree with Atlas playing in VR is a very personal experience.
I saw in another post an entry where someone said they took Dramamine before using the Rift, unfortunately I don't think that would work, since most real motion sickness occurs when your inner ear is telling you that you are moving but your eyes are telling you that you are standing still, in VR it's the opposite, Your eyes are telling you that you are moving but your inner ear is telling your brain that you are standing still. Dramamine numbs your inner ear so I don't think it will work for the nausea in VR. Of course you do have the placebo effect, since sometimes motion sickness occurs because the user expects it to occur, and since motion sickness is not really caused by anything physical thinking you will be sick can make you sick.
I am very prone to motion sickness, but using the Rift in ED doesn't trigger it.
I saw in another post an entry where someone said they took Dramamine before using the Rift, unfortunately I don't think that would work, since most real motion sickness occurs when your inner ear is telling you that you are moving but your eyes are telling you that you are standing still, in VR it's the opposite, Your eyes are telling you that you are moving but your inner ear is telling your brain that you are standing still. Dramamine numbs your inner ear so I don't think it will work for the nausea in VR. Of course you do have the placebo effect, since sometimes motion sickness occurs because the user expects it to occur, and since motion sickness is not really caused by anything physical thinking you will be sick can make you sick.
I am very prone to motion sickness, but using the Rift in ED doesn't trigger it.
I did some research on this issue, and a few people are reporting that they can fix the issue by not using the dvi to hdmi adapter but instead plugging the rift directly to the Hdmi port on their video cards.
Last edited:
Shaking/jitter like this: https://www.youtube.com/watch?v=xDDJZNvGfnc (Elite) or this https://www.youtube.com/watch?v=o1CaWsjax3I (Oculus Dek Demo)? Does the shaking temporarily go away when you cover the Rift's front with your hands (or move out of the tracking volume)?
If so then contact Oculus support. Took me several months to sort this issue out with Oculus and finally I'll get a replacement.
If so then contact Oculus support. Took me several months to sort this issue out with Oculus and finally I'll get a replacement.
judder is when the system cant maintain 75 fps vsync lock.
thus inducing the nausea feeling.
everyone's tolerance levels vary slightly.
but we all strive for 75 fps.
fine tuning these elements to work best performance/quality is the key
super sampling, in game SS, nvcp DSR SS, low settings medium settings, high settings, planet textures, physx to cpu, or overclocking your GPU
you need sli 980s to go top top notch, or a titan x.
but 1 - 780ti, 970 or 980 is more than enough for a very high quality and smooth experience.
thus inducing the nausea feeling.
everyone's tolerance levels vary slightly.
but we all strive for 75 fps.
fine tuning these elements to work best performance/quality is the key
super sampling, in game SS, nvcp DSR SS, low settings medium settings, high settings, planet textures, physx to cpu, or overclocking your GPU
you need sli 980s to go top top notch, or a titan x.
but 1 - 780ti, 970 or 980 is more than enough for a very high quality and smooth experience.
This.
And, you're very lucky to be able to play with those settings with your 980. My slightly over-clocked 970 can BARELY play the game on lowest settings now. It has slowly gotten worse over the last few weeks.. maybe since the last patch.
ill second that, right after patch i was forced to switch from in game 1.5 super sampling, to nvidia nvcp DSR of 1440p
and some adjustments to some settings
damn you FD!
Yes, exactly. Same issue myself. So glad at least ONE other person has this because maybe we can sort it out. Did you change any of the cables at all or just using stock/standard dk kit cables? I'm guessing you haven't but thought I'd ask.
Thanks!
it's a headtracking issue new to 1.2, it started with 1.2 and it's the worst problem I have with Elite, the single biggest bug and it's why I haven't been playing. The headtracking snaps back and forth between 2 points. The distance it snaps remains constant (same exact relative distance from focal point, same magnitude for the shaking, usually up and down) when you look around. It's like there's a conflict between the IMU and the camera or something. It's definitely an Elite bug and not a problem with your setup, I have reinstalled windows completely from scratch and tried to fix it for a whole weekend and I'm convinced it is a bug.
I don't know the best way to report it to the developers but what you report is definitely the same problem I'm having and there are other people who have reported it on this forum also.
You can mitigate the issue somewhat by using both hands in front of your headset to block the IR camera briefly and the problem will go away temporarily. It will still make you sick, though. I really would do anything to have Frontier comment on this issue and say there's a fix in progress
I can't overstate how horrible the bug is. It took VR from being completely amazing to completely awful instantly. I would go back to 1.0 even without the Wings update even though I play with friends if I could. It's awful.
I don't know the best way to report it to the developers but what you report is definitely the same problem I'm having and there are other people who have reported it on this forum also.
You can mitigate the issue somewhat by using both hands in front of your headset to block the IR camera briefly and the problem will go away temporarily. It will still make you sick, though. I really would do anything to have Frontier comment on this issue and say there's a fix in progress
I can't overstate how horrible the bug is. It took VR from being completely amazing to completely awful instantly. I would go back to 1.0 even without the Wings update even though I play with friends if I could. It's awful.
Last edited:
it's a headtracking issue new to 1.2, it started with 1.2 and it's the worst problem I have with Elite, the single biggest bug and it's why I haven't been playing. The headtracking snaps back and forth between 2 points. The distance it snaps remains constant (same exact relative distance from focal point, same magnitude for the shaking, usually up and down) when you look around. It's like there's a conflict between the IMU and the camera or something. It's definitely an Elite bug and not a problem with your setup, I have reinstalled windows completely from scratch and tried to fix it for a whole weekend and I'm convinced it is a bug.
I don't know the best way to report it to the developers but what you report is definitely the same problem I'm having and there are other people who have reported it on this forum also.
You can mitigate the issue somewhat by using both hands in front of your headset to block the IR camera briefly and the problem will go away temporarily. It will still make you sick, though. I really would do anything to have Frontier comment on this issue and say there's a fix in progress
I can't overstate how horrible the bug is. It took VR from being completely amazing to completely awful instantly. I would go back to 1.0 even without the Wings update even though I play with friends if I could. It's awful.
Ranix! Dude, I'm so with you bud and man, sorry to say, but I like that you are here with me cause I felt all alone and nobody seemed to respond or be having the same issue.
Tonight I made it a point to mess with my system and try and "repair" this and I too JUST DISCOVERED that, just like you, if I put both my hands in front of my headset the problem will go away temporarily. Ok, at LEAST I sort of know what is going on now and understand the situation better now.
I actually feel better and am hoping that this will get fixed. What's funny is, I am getting almost ZERO judder in stations and about half of what I used to in RES sites...but I get this new shaking for the last couple weeks and it BLOWS having to put my hands up constantly to the oculus or in front of the camera.
Why is this only happening to some of us?
it doesn't really seem like either of them Popopinsel but it would be more like the first one but the camera never goes pale and never seems to have problems following my head it just jitters back and forth constantly and will do it forever until I block the IR camera for a moment then unblock it
try this,
open task manager,
goto 'services' tab,
click 'open services' at bottom left. this opens the more advanced services msc on win 8.1,
scoll down to 'oculus vr runtime', open properties,
set startup type disabled,
OK
right click again and press stop,
now open the OVRServer_x86.exe directly in the folder C:\Program Files (x86)\Oculus\Service
this will show a cmd window and you can see some of the oculus data written to the screen.
this method of using the oculus is a bit more complicate than normal, since you will need to manually start the OVRServer_x86.exe each time you reboot before using the headset instead of relying on the service to detect the oculus being turned on and starting it automatically in the background.
hopefully, your issue may then be written in the console window. if not, then the issue is likely to be inside the ED code.
open task manager,
goto 'services' tab,
click 'open services' at bottom left. this opens the more advanced services msc on win 8.1,
scoll down to 'oculus vr runtime', open properties,
set startup type disabled,
OK
right click again and press stop,
now open the OVRServer_x86.exe directly in the folder C:\Program Files (x86)\Oculus\Service
this will show a cmd window and you can see some of the oculus data written to the screen.
this method of using the oculus is a bit more complicate than normal, since you will need to manually start the OVRServer_x86.exe each time you reboot before using the headset instead of relying on the service to detect the oculus being turned on and starting it automatically in the background.
hopefully, your issue may then be written in the console window. if not, then the issue is likely to be inside the ED code.
I find the in-game DSR terrible. Even when I tried setting all the options to low, at 1080p, 1.5 in-game DSR was crappy. I get much better results from using the NVCP DSR at 1440, and using that resolution in-game, without touching the in-game DSR. Still don't understand why my single GTX970 seems to handle the game very well at high levels of graphical fidelity when others with 980s are struggling...
the jitter i see in the youtube links, i was getting this long before update 1.2.
it comes and goes, it doesnt bother me recently though
it comes and goes, it doesnt bother me recently though