Rift Judder and FPS discussion thread.

Heavy judder in RES sites - yes or no


  • Total voters
    35
  • Poll closed .
I had two 970s in SLI. It ran smooth but I couldn't stand the extra latency that came with SLI. So I sold them both and bought a 980. Happy now :)

Interesting. The extra latency is really noticeable ? Because I saw some post from users how say that SLI is "smooth" too...
Do you have a steady 75 fps in station and ressource extraction zone now ?
 
Last edited:
ok Im putting on my smugface.

Im running Elite on ultra settings @ 1920x1080.
I get 60-70fps in station and resource extraction zones, and way more than that every where else.

I have an aging:
i7-950
3gig Gainward Geforce GTX580 (Driver version 344.48)
24gig Ram

No rift but i do use TrackIR
 
Last edited:
I get judder in SOME stations, and I'd guess it has to do with traffic. The worst I had was a busy station orbiting a ring system, and it was still playable. I also get BAD judder sometimes when I switch from 2D to 3D in elite. That goes away with a reboot. Talking rift here of course... I get none of that in 2d mode.
 
Interesting. The extra latency is really noticeable ? Because I saw some post from users how say that SLI is "smooth" too...
Do you have a steady 75 fps in station and ressource extraction zone now ?

It's not about framerate. Because of the way SLI works, it creates an extra frame of latency. Nvidia is trying to fix this by making each card render each view individually.

ok Im putting on my smugface.

Im running Elite on ultra settings @ 1920x1080.
I get 60-70fps in station and resource extraction zones, and way more than that every where else.

I have an aging:
i7-950
3gig Gainward Geforce GTX580 (Driver version 344.48)
24gig Ram

No rift but i do use TrackIR

The Rift basically doubles PC requirements. The TrackIR changes nothing performance wise.
Also we need to run at 75 FPS constantly, no exceptions, to get a smooth experience.
 
Last edited:
I get judder in SOME stations, and I'd guess it has to do with traffic. The worst I had was a busy station orbiting a ring system, and it was still playable. I also get BAD judder sometimes when I switch from 2D to 3D in elite. That goes away with a reboot. Talking rift here of course... I get none of that in 2d mode.

I'm sure everything is related to the number of NPC in the instance. It explain judder in stations, resource extraction zones and supercruise.
Try disconnect and reconnect in a resource extraction zones for exemple, you will slowly see FPS slowing down related to the number of NPC spawning. And my graphic card is at 50% at this time.
NPC are not handled correctly and slow down the game. I hope this is a bug and FD will fix it. May be someone need to create a ticket ? (I don't know how to do it)
 
Last edited:
I have been heavily monitoring the system performance during use with the Rift and made some interesting observations.

For my system:
i5 3570k, 16GB RAM, R9 280X, core parking disabled (well, threshold is 95%... whatever)

I observed choppyness in big stations, but it would be sporadic, and seem to coincide with spikes in graphics usage up to 95%. More reliably reproducible with the starport menu up (note that this is bare minimum settings for testing, literally low/off everything). Outside the station there don't seem to be any problems.

Outposts there were no problems, butter smooth. Normal space is butter smooth. Don't recall problems at resource collection sites but haven't really visited any since beginning to pay attention to this issue.

Supercruise is butter smooth... UNTIL approaching my destination. As I near my target and begin to slow down, so too does the FPS. Oddly I notice a steady, smooth decline in GPU usage as this happens. It will stay low as long as I loiter near my destination. Soon as I drop out of Supercruise, butter smooth again.

CPU usage does not change appreciably, but worth noting it tips upwards a teeny bit during times when FPS is sagging.

I observed WORSE stutter if I set AMD's powertune envelope from 0% to +20%. In fact it performed much like it did at -20%. It did NOT appear to be thermal throttling. Clock speeds, however, do seem to improve stutter in stations, but I'm already pushing the card on stock voltages (around 1140MHz GPU, left mem at 1600MHz stock as it seems to make no difference).

I observed WORSE stutter with my CPU overclocked. At 4.1GHz it stuttered worse (no turbo, direct clock). At 4.3GHz (turbo clock) it stuttered worse. At stock 3.4GHz with NO TURBO... seems generally a lot smoother, even in stations. CPU usage does not seem to have changed appreciably between the stock and OC'ed environments. I find this particularly confusing. Might try artificially dropping clocks and see what that does.
 
I read on one of these forums to put your hand in front of your Rift Cam and the jitter stops. It does for about 10Sec and then starts again. I Do not run the latest Nvidia drivers as I have Pcars and those new drivers stop it from working. I get jitter all the time now. it is really a annoyance but I have to live with it until they figure out what is causing it. I am just curious as to why it stops once I put my hand in front of the Rift Cam. Baffling to me. System Specs below in Sig.

Cheers
RJ
 
Putting your hand in front of the Cam is only fixing it for about 10Sec.. I will give the onboard USB on the DK2 a try to see if that helps...

Thanks for the help.

Cheers
RJ
 
Also it appears bright light sources might cause this vertical jitter. Just turned off light in room (there are reflective picture frames behind me) and no jitter for last 20 minutes in asseto corsa, normally at least every 3 mins.
 
I read on one of these forums to put your hand in front of your Rift Cam and the jitter stops. It does for about 10Sec and then starts again. I Do not run the latest Nvidia drivers as I have Pcars and those new drivers stop it from working. I get jitter all the time now. it is really a annoyance but I have to live with it until they figure out what is causing it. I am just curious as to why it stops once I put my hand in front of the Rift Cam. Baffling to me. System Specs below in Sig.

Cheers
RJ

Interesting. I find the judder does not stop when I do that. I guess my judder is simply a drop in FPS rather than an inherent problem with the Rift. Is there a difference or is that what you're observing too? I.e. if you run MSI Afterburner or something can you observe a drop in FPS during the juddery moments?
 
Ok, so I turned antialiasing - transparency on the nvidia control panel to 8 x and it's reduced my judder and improved my picture at the same time... i thought the demand on resources would increase the judder, but I was wrong... stations are almost judder free now.
 
Lag at station display

Hi there, i often experience a lag when docked in station and navigating through the display to buy commodities and pay fines and such.
Sometimes its just a smaller lag, other times its pretty big, you sit staring at the orange "please wait"-ball and sometimes there isn't even that ball. I have a pretty good connection, can make 2.5 mb/sec-downloads from the net so i don't think the problem is on my side.
Actually i cannot load the bulletin page at all.

In space flying no problems, all flawless.

EDIT: wrote wrong, commodities are ok, but bulletin page seems down.
 
Last edited:
Help! Need some serious help here with my DK2...

I'm getting massive aliasing or screen tearing or whatever it's called but you can see it here:

https://www.youtube.com/watch?v=ZXhOhUzpOQg

This was taken by my phone of the actual OR display.
As you can see the station and everything else is super aliased or whateer, and I can't seem to fix it no matter what the settings. I love the OR but I can't seem to sustain wearing it because of the horrible graphical issues.

Here are my settings, and again, I've tried changing them but no luck so far. Any help would be greatly appreciated!



GeForce GTX 680MX
Driver: 344.75
Dedicated video memory: 2048 MB GDDR 5




Global Settings:


Ambient Occulusion: Off
Anisotropic Filtering: Application-controlled
Antialiasing - FXAA: Off
Antialiasing - Gamma Correction: On
Antialiasing - Mode: Application controlled
Antialiasing - Transparency: Off
CUDA - GPU's - All
DSR Factors - Off
Maximum pre-rendered frames - Use the 3d application setting
Multi-Display/mixed-GPU acceleration: Multiple display performance mode
Power management mode: Adaptive
Shader Cache: On
Texture filtering - Anisotropic sample optimization: off
Texture filtering - Negative LOD bias: Allow
Texture filtering - Quality: Quality
Texture filtering - Trilinear optimization: On
Threaded optimization: Auto
Triple buffering: Off
Vertical sync: Use 3d application setting
Virtual Reality pre-rendered frames: 1


Oculus Rift Configuration Utility: Extended Mode


Elite Dangerous Graphic Options:


Display: Secondary
Resolution: 1920x1080
Refresh Rate: 75mhz
Vsync: On
Frame Rate Limit: Off
Field of View: Max
3D(Experimental): Oculus Rift (Headphones)
Model Draw Distance: Max
Gamma: 60% or so
Texture Quality: High
Shadow Quality: High
Bloom: High
Blur: On
AntiAliasing: Off



Thanks,
Scan
 
Hey Scan,
.
You're running on a laptop, right?
Its a 680MX? (mobile)
Your 680MX gets good benchmark scores. I'm surprised you don't have somewhat better performance.
.
I have a tower PC, but I had very similar video before I upgraded my video card.
I bought the Rift when I still had a GTX550 Ti, and before I invested in a new card I wanted to see what it would look like... it was unacceptable.
I invested in a 970, and even with the 970 it is still not 100% fluid all the time, but it is certainly awesome.
.
Your setting all look correct, nothing stands out as being far off.
What is your Oculus Quality set to? <- This will have a large effect on frame rate in my experience, but lowering it too much defeats the purpose because things quickly degrade.
.
The other thing you could try is disabling the tracking camera (camera with the blue LED).
Simply unplug both the power and usb connections to the camera and the Oculus will still work (mostly) in ED.
You will have to deal with somewhat washed out colors and you'll lose the ability to lean in, but I do recall that it helped with overall performance when I experimented with it a while back.
.
.
Good luck.
.
.
Edit: Oh yeah, and turn your Shadows to Low. It should provide a small boost.
 
Last edited:
Start by turning everything to the lowest settings and then see how it looks. If everything looks okay then start turning on/up your settings one at a time until you find the problem.
If you are still seeing the same thing well I have to think about that more. So let me know how it works out. Isn't the 680MX the card made for apple?
 
Thought of something else.
.
Some users have observed that if their primary monitor isn't capable of running at 75Hz then NVidia will throttle back the Rift and prevent it from achieving 75fps.
If possible, open up your NVidia Control Panel and disable your primary monitor before launching ED.
The whole process can make you a little cross-eyed and definitely requires some careful pre-placement of windows in order to execute properly, but it may be worth a try.
.
Good luck again!
 
Thought of something else.
.
Some users have observed that if their primary monitor isn't capable of running at 75Hz then NVidia will throttle back the Rift and prevent it from achieving 75fps.
If possible, open up your NVidia Control Panel and disable your primary monitor before launching ED.
The whole process can make you a little cross-eyed and definitely requires some careful pre-placement of windows in order to execute properly, but it may be worth a try.
.
Good luck again!

This will not help I tested it while making my dk2 setup guide and it absolutely made no difference I actually got worse performance from that (not sure why though). It may be that it was a bug from the beta or gamma version where that did make a difference but now its not true anymore.
You can read my post at the top of the forum (Detailed DK2 Setup) if you want to know my testing method there is also some useful links and information that you might find helpful.
 

This will not help I tested it while making my dk2 setup guide and it absolutely made no difference I actually got worse performance from that (not sure why though). It may be that it was a bug from the beta or gamma version where that did make a difference but now its not true anymore.
You can read my post at the top of the forum (Detailed DK2 Setup) if you want to know my testing method there is also some useful links and information that you might find helpful.

Strange since it worked for me. I've mentioned this several times now, but I used to play E:D on the Rift using my main monitor that was capable of 75Hz at 1280x1024 ( native is 2560x1440 @ 60 Hz ) using extended mode. Sadly this monitor broke a few weeks ago and i've had to switch to my back up. My back up monitor is only capable of 60Hz at any resolution and it definitely caused problems and loss of low persistence. After setting up my nvidia gpu to disable the monitor whilst running the DK2, performance was far better and low persistence mode worked fine.

It should of course be stated that doing this does not 'increase overall performance' simply that it enables the rift to run at 75Hz (if your gpu can manage it) instead of being forced to 60Hz.
 
Last edited:
Strange since it worked for me. I've mentioned this several times now, but I used to play E:D on the Rift using my main monitor that was capable of 75Hz at 1280x1024 ( native is 2560x1440 @ 60 Hz ) using extended mode. Sadly this monitor broke a few weeks ago and i've had to switch to my back up. My back up monitor is only capable of 60Hz at any resolution and it definitely caused problems and loss of low persistence. After setting up my nvidia gpu to disable the monitor whilst running the DK2, performance was far better and low persistence mode worked fine.

It should of course be stated that doing this does not 'increase overall performance' simply that it enables the rift to run at 75Hz (if your gpu can manage it) instead of being forced to 60Hz.

​That is really interesting im not saying your wrong so please dont get that in your head that im attacking you. I am just really wondering why I cant reproduce that result any ideas?
Because if that's true and certain monitors will cause that issue I need to update my setup post to reflect it. I just don't want to put any misinformation out there and have ppl going through steps they don't need to. Maybe I can find another monitor to test on or maybe it is a Nvidia thing if so i'm switching to a nvidia card soon anyway so ill be able to check that out.
 
Last edited:
Back
Top Bottom