Rift Judder and FPS discussion thread.
- Thread starter Viajero
- Start date
People keep claiming Judder comes from insufficient power in a machine.
I don't understand that. It's clearly shown that even people with great rigs (like myself) have loads of judder and black smear, where as people with moderate rigs get great results.
Something is still dodgy. The latest Oculus Runtime seems to have worsened the Smear for me as well.
My rig:
i5 3350p @ 3.9 Ghz
16 GB Ram
Geforce GTX980 G1 (gigabyte) Gaming
3x SSD for OS and Gaming.
Oculus Rift DK2
Still I get massive Judder in Asteroid Fields + Smear all the time.
Tried everything to fix it.. nothing works.
I don't understand that. It's clearly shown that even people with great rigs (like myself) have loads of judder and black smear, where as people with moderate rigs get great results.
Something is still dodgy. The latest Oculus Runtime seems to have worsened the Smear for me as well.
My rig:
i5 3350p @ 3.9 Ghz
16 GB Ram
Geforce GTX980 G1 (gigabyte) Gaming
3x SSD for OS and Gaming.
Oculus Rift DK2
Still I get massive Judder in Asteroid Fields + Smear all the time.
Tried everything to fix it.. nothing works.
Cool. For me the trick was setting the FPS location to 300 x 300 - this should move it off your main monitor and onto the extended ie the Rift. Good luck.
Judder only occational - cannot reproduce why
Maybe you guys can help me.
My system: I7 3770K at 4.7 ghz, 16 gb RAM, Radeon R2 290 running at 1150/1450. All watercooled nothing is throttling. I am using SDK 0.4.4 and Catalyst 14.9 drivers.
Elite runs at 75 FPS usually. Even in stations. I got shadows on medium, AA,Blur and AO off.
Now here is the strange part: After a while of super fluid gameplay sometimes i jump into a system where i get horrible judder in supercruise. The FPS go to 37 wich leads me to the assumption that it is vsync related.
Once i approach a station and jump back into "normal" space it is at 75 FPS again.
The strange part: Once i undock and go into supercruise again it usually is fixed and at solid 75 FPS again - in the same system!
I did a clean driver sweep allready - i just can't find the problem.
Maybe you guys can help me.
My system: I7 3770K at 4.7 ghz, 16 gb RAM, Radeon R2 290 running at 1150/1450. All watercooled nothing is throttling. I am using SDK 0.4.4 and Catalyst 14.9 drivers.
Elite runs at 75 FPS usually. Even in stations. I got shadows on medium, AA,Blur and AO off.
Now here is the strange part: After a while of super fluid gameplay sometimes i jump into a system where i get horrible judder in supercruise. The FPS go to 37 wich leads me to the assumption that it is vsync related.
Once i approach a station and jump back into "normal" space it is at 75 FPS again.
The strange part: Once i undock and go into supercruise again it usually is fixed and at solid 75 FPS again - in the same system!
I did a clean driver sweep allready - i just can't find the problem.
next time it happens start a stopwatch, if it happens at 5 minute intervals its an upnp issue with the lease length and to cure it you may need to forward a port on your router.
I get this all the time, especially when exploring and looking to scan objects. Likewise running on a decent gpu (GTX 970) and can get 75hz or above (with tweaked quality settings like yourself), even in stations, running just on the rift (have to disable my monitor as it only supports 60hz at any resolution) and the only other time i've had problems previously was when trying to mine asteriods, though strangely no problem in the first tutorial in the asteroid belt.
Anyway SC issues I put down to predominantly happening the first time you enter a new star system and E
needs to generate the content/assets. Further more this would appear to happen when you get within a specific radius of objects, which makes it quite annoying when exploring and scanning. I suspect its made worse on the rift as if you are often moving your head around during the time it stalls so you can get quite a large visual jump, where as without the rift you are probably traveling straight and not looking around so the stalls are less noticeable. Something I should try yo confirm this is to completely explore a system, then doing another loop around it and see if the stutters/stalls remain, reduce or disappear. If they disappear I would take that as pretty convincing evidence that its content creation that is the problem.
The only alternative explanation I can think of is the creation or tracking or AI ships within the star system, maybe even something to do with net code, but object creation is my bet.
Anyway SC issues I put down to predominantly happening the first time you enter a new star system and E
needs to generate the content/assets. Further more this would appear to happen when you get within a specific radius of objects, which makes it quite annoying when exploring and scanning. I suspect its made worse on the rift as if you are often moving your head around during the time it stalls so you can get quite a large visual jump, where as without the rift you are probably traveling straight and not looking around so the stalls are less noticeable. Something I should try yo confirm this is to completely explore a system, then doing another loop around it and see if the stutters/stalls remain, reduce or disappear. If they disappear I would take that as pretty convincing evidence that its content creation that is the problem.The only alternative explanation I can think of is the creation or tracking or AI ships within the star system, maybe even something to do with net code, but object creation is my bet.
Last edited:
NoiseCrime: I think you nailed it. Now that you mentioned it i am pretty sure it only happenes in new systems i jumped into the very first time.
I recently traveled to the center of empire space wich means i entered a lot of new systems.
I do have a firewall running - elite is on the allowed list but i will also try if disabling it helps. Will look into port forwarding as well.
I recently traveled to the center of empire space wich means i entered a lot of new systems.
I do have a firewall running - elite is on the allowed list but i will also try if disabling it helps. Will look into port forwarding as well.
I have a similar setup - i5 haswell R9 290 8GB Ram Asus sabertooth mk2 - and i have the exact same issues since the Gamma release.
Super smooth in stations, only in SC it happens usually when i approach a planet after a minute or 2. When leaving SC its butter smooth again.
Would be nice if it will be fixed in the RC of today, its a bit of a immersion breaker for me now. But then again, in the stations its always 75fps. ;-)
DK2 & Elite was pretty smooth in early Beta... now it's judder city!
Am I missing something?
I've been using the DK2 since it was released and found that Beta 1 was pretty smooth - in fact the only issue I had was reading the orange text (which of course can now be worked around).
I gave the Beta a break and jumped back in just before launch. Wow. The head movement judders terribly. I ensured I had 75Hz, reduced graphics settings to low (with AO off) and still it's unplayable - even in deep space.
I've had this issue for months now with the latest Nvidia drivers (up to and including the latest dodgy Beta), DK2 Runtime 0.4.2 & 0.4.4. I had already unparked cores and I haven't made any substantial changes to my setup.
Now my system is at the low end (I'm upgrading soon) but as I said I *was* able to play E without noticeable judder in the early Beta when I first got the DK2.
Has anyone else found this? Any ideas?
Jim
Am I missing something?
I've been using the DK2 since it was released and found that Beta 1 was pretty smooth - in fact the only issue I had was reading the orange text (which of course can now be worked around).
I gave the Beta a break and jumped back in just before launch. Wow. The head movement judders terribly. I ensured I had 75Hz, reduced graphics settings to low (with AO off) and still it's unplayable - even in deep space.
I've had this issue for months now with the latest Nvidia drivers (up to and including the latest dodgy Beta), DK2 Runtime 0.4.2 & 0.4.4. I had already unparked cores and I haven't made any substantial changes to my setup.
Now my system is at the low end (I'm upgrading soon) but as I said I *was* able to play E
without noticeable judder in the early Beta when I first got the DK2. Has anyone else found this? Any ideas?
Jim
Am I missing something?
I've been using the DK2 since it was released and found that Beta 1 was pretty smooth - in fact the only issue I had was reading the orange text (which of course can now be worked around).
I gave the Beta a break and jumped back in just before launch. Wow. The head movement judders terribly. I ensured I had 75Hz, reduced graphics settings to low (with AO off) and still it's unplayable - even in deep space.
I've had this issue for months now with the latest Nvidia drivers (up to and including the latest dodgy Beta), DK2 Runtime 0.4.2 & 0.4.4. I had already unparked cores and I haven't made any substantial changes to my setup.
Now my system is at the low end (I'm upgrading soon) but as I said I *was* able to play E
Has anyone else found this? Any ideas?
Jim
Yes. I have also noticed a degradation in performance ever since 1.01.
.
Gamma was smooth for me, and I was happy.
1.00 was amazingly smooth, and I was ecstatic.
1.01-1.03 is playable, but it is much less fluid.
.
I have seen just how awesome this game can play (in Version 1.00), and am hoping that they'll tune it back to that sweet spot sooner or later.
.
My System: AMD 8350, GTX 970, 16GB RAM, Win7 64bit, etc, etc, etc
When ypou speak of "disabling your monitor", are you talking about:
1) Not echoing your gaming display to a flat display
2) Disconnecting any other displays, so as to concentrate all display cycles solely to the Rift.
Thanks for clarifying!
Yep, almost exactly the same for me. Although I only noticed the judder on version 1.03, and it mostly seems to be during jump speeds. Disabling the orbiting lines (likely a bug with this causing the issue?) seems to help a bit, but tracked my framerate and can see drops to 48 FPS at times. It was incredibly fluid to start with, would have liked the option to supersample but wasn't too bothered. Kind of limits the playing time, probably a good thing but taking breaks more often.
Tried a few other things to help it out but mostly just made things worse, so leaving it for a future update to fix hopefully.
Intel Core i5 4690, GTX 970, 16GB RAM, Win 7 64x
Judder in ring system even when GPU isn't maxed
Hi guys! I just got a GTX 980 all set up, and OH MAN. SO GOOD. Being able to run shadows on high and still get super smooth 75hz is amazing!
That said, I've noticed something interesting. With everything cranked, I now get completely smooth performance in station hangars. However, when I'm doing some bounty hunting in a ring system, I still get that infamous choppiness. Previously, with my 970, my GPU utilization would be pretty much peaked, and I figured that was the source of the trouble. however, with the GTX980, my GPU was only running at about 70% utilization, lower than it was even in stations.
My CPU was only running at about 50%
Could this be some sort of memory leak causing unwanted garbage collection or something of the sort? This is one situation where there are constantly huge amounts of ships coming and going. It seemed to get worse the longer I was there. I was wondering if anyone else saw similar stuff, before I just go ahead and ticket it as a bug, rather than as my computer simply being slow.
They're SO CLOSE to having this thing totally smooth. Some planets still cause SC chop, a little bit of chop in hyperspace, and some issues with the transitions between SC/normal/hyperspace where the camers blips around at odd angles for a single frame here and there. Get those smoothed out (and this asteroid thing) and it's going to be like BUTTER.
Hi guys! I just got a GTX 980 all set up, and OH MAN. SO GOOD. Being able to run shadows on high and still get super smooth 75hz is amazing!
That said, I've noticed something interesting. With everything cranked, I now get completely smooth performance in station hangars. However, when I'm doing some bounty hunting in a ring system, I still get that infamous choppiness. Previously, with my 970, my GPU utilization would be pretty much peaked, and I figured that was the source of the trouble. however, with the GTX980, my GPU was only running at about 70% utilization, lower than it was even in stations.
My CPU was only running at about 50%
Could this be some sort of memory leak causing unwanted garbage collection or something of the sort? This is one situation where there are constantly huge amounts of ships coming and going. It seemed to get worse the longer I was there. I was wondering if anyone else saw similar stuff, before I just go ahead and ticket it as a bug, rather than as my computer simply being slow.
They're SO CLOSE to having this thing totally smooth. Some planets still cause SC chop, a little bit of chop in hyperspace, and some issues with the transitions between SC/normal/hyperspace where the camers blips around at odd angles for a single frame here and there. Get those smoothed out (and this asteroid thing) and it's going to be like BUTTER.
I set my view-distance slider to halfway and also use core parking. No problems in asteroid fields or ring systems.