CV1 Stutter RES Sites

Hi all,

I've recently started to notice huge amounts of stuttering in Resource Extraction Sites when there is another player in the same instance, making it unplayable in VR.

It's unique to Res sites, only occurring whilst another player is present and it doesn't occur anywhere else.

I usually run at 2x Pixels per display but reducing this doesn't make a difference. Also, the problem is unique to the headset as the mirrored display doesn't show the stutter.

I'm going to submit a ticket but was wondering if anyone else has noticed this?

CV1
1080 FTW
 
Yes, the game stutters in RESites only. I run full ultra at 1.0 supersampling and 1.5 HMD quality. I am running a 1080ti and Oculus Rift CV1 with latest drivers for both Oculus and GeForce.
 
is this not just areas of higher strain on your machine and you are just running at too high a detail?

have you tried lowering settings? i find in a RES, esp ice ones, ASW is working overtime on my rig, and ASW is not great in ED.

edit... hmm op says reducing settings does not fix.

sorry i got nothin else :(
 
Yup, reducing setting does not work for me. I tried lot of settings combinations and nothing had some visible effect.
My case with big traffic is not with other players only, but with NPCs only as well...
 
It seems (hopefully) that the issue has stopped. I'm really not sure what was happening, frame rates are back up to a solid 90fps again and the only stuttering I receive is for a few seconds after I jump into a station whilst it loads everything.

Windows had a pending update to install whilst I was playing so maybe something to do with that.

I still use the Oculus Debug Tool and set it to 2x and force ASW off.
 
It seems (hopefully) that the issue has stopped. I'm really not sure what was happening, frame rates are back up to a solid 90fps again and the only stuttering I receive is for a few seconds after I jump into a station whilst it loads everything.

Windows had a pending update to install whilst I was playing so maybe something to do with that.

I still use the Oculus Debug Tool and set it to 2x and force ASW off.

lol - No wonder you have issues - 2x SS is way to high for any rig to provide you with a solid 90FPS!! Besides, it has been said by Oculus that anything over about 1.5 is not noticable any way (unless the app runs below 1.0 to begin with). I'd honestly tone that down, you are dropping your performance for no gain what so ever.
 
I force ASW ON for Elite and set 1.5 x pixel density (1080 @ stock clocks + i5 6600k @ 4.4GHz) in the debug tool.

This will eliminate juddering but you do get some ASW ghosting.

The compositor frequently drops frames when transitioning from non ASW to ASW which causes judder.
 
Stuttering on a monitor? I have 144fps (limited to monitor framerate) in open play rez and stations?!?
I only use a GTX 980 ti with an i5 6600K...
 
Last edited:
I noticed the same when playing in wings in the hazres during the last CG and turned the HMI Quality setting down to 1.25 (IIRC that setting does the same as the debug tool now). Frame rates seem go down whenever a lot of complex objects (ships) have to be rendered, lots of plain asteroids seem not to be the culprit. Lowering the settings, in particular ambient occlusion and shadows and turning down supersampling to 1.0 seemed to help for me (i7-7700K, Asus Strix 1070GTX OC to 1850 Mhz).

O7,
[noob]
 
I noticed the same when playing in wings in the hazres during the last CG and turned the HMI Quality setting down to 1.25 (IIRC that setting does the same as the debug tool now). Frame rates seem go down whenever a lot of complex objects (ships) have to be rendered, lots of plain asteroids seem not to be the culprit. Lowering the settings, in particular ambient occlusion and shadows and turning down supersampling to 1.0 seemed to help for me (i7-7700K, Asus Strix 1070GTX OC to 1850 Mhz).

O7,
[noob]

Is there any gain using either the debug tool or in game settings?
 
lol - No wonder you have issues - 2x SS is way to high for any rig to provide you with a solid 90FPS!! Besides, it has been said by Oculus that anything over about 1.5 is not noticable any way (unless the app runs below 1.0 to begin with). I'd honestly tone that down, you are dropping your performance for no gain what so ever.

I'm not sure what's funny? Occasionally my frames drop to 45 when entering a station but they soon pick up to 90 again. Personally I DO see a difference between 1.5x and 2.0x so I am more than happy with these settings. I don't even notice when ASW kicks in.
 
I'm not sure what's funny?

What is funny is that you are using settings way over what any GPU / CPU combo can manage and come asking about stutter in RES sites.

I DO see a difference between 1.5x and 2.0x,

Yeah its called a placebo. Oculus even state this themselves.

Occasionally my frames drop to 45 when entering a station but they soon pick up to 90 again.

How odd as you said this earlier:

I still use the Oculus Debug Tool and set it to 2x and force ASW off.

If ASW was off, you wouldn't see dips to 45FPS, you would just see dips to any number. ASW is still on mate.

Not trying to be nasty - just stating the obvious. That being you have your SS set way too high and for no gain at all.
 
Last edited:
Is there any gain using either the debug tool or in game settings?

Who knows exactly? https://forums.frontier.co.uk/showthread.php/300934-HMD-Image-Quality :)

From what I get, the HMD Quality setting is said to use the same Oculus API function as the debug tool. Beyond that, the experts are divided.

Basically, I use CTRL+F on the control window to get a rough estimate about the render performance. 99% it's either 90fps or 45fps, ASW kicking in I guess. Then, in-station, I just check some screens etc. and see if I feel the slightest bit uneasy (way before getting headaches or sth) after some time. Same with BH zones, planet ports or Thargoid wreckage sites (fps drops big time near the center of the central edifice). If I do, I turn something down and try again. And I monitor the GPU load over time via ASUS's tool. If it's not 99% at some point, there's still headroom.

O7,
[noob]
 
Last edited:
Back
Top Bottom