CPU; # of threads matter much?

Arguendo

Volunteer Moderator
Keep in mind, if you're not hitting 90 fps, seeing <100% GPU usage is normal.
Not sure what you're saying here tbh. Are you saying my CPU could be bottoming out, but my GPU running at 60-70% could still be the bottleneck?
 
Not sure what you're saying here tbh. Are you saying my CPU could be bottoming out, but my GPU running at 60-70% could still be the bottleneck?

If you can't hit 90 fps, the game drops to 45, with ASW or ATW generating the rest. Since your GPU only has to run half the framerate, it doesn't have to work nearly as hard, and so usage will be low. Maybe your CPU is a bottleneck too, but I can tell you a 1060 is still a relatively weak card for ED in VR as well. You'd see a huge benefit in upgrading both.
 
Last edited:

Arguendo

Volunteer Moderator
If you can't hit 90 fps, the game drops to 45, with ASW or ATW generating the rest. Since your GPU only has to run half the framerate, it doesn't have to work nearly as hard, and so usage will be low. Maybe your CPU is a bottleneck too, but I can tell you a 1060 is still a relatively weak card for ED in VR as well. You'd see a huge benefit in upgrading both.
Yeah, I'm aware that my 1060 isn't ideal for VR. Upgrading that would mean upgrading pretty much everything else as well though, and like I said, I am not at that point quite yet :D

I get 90 with my current settings pretty much everywhere except at stations and some heavy instances during wing fights. At stations sometimes it hovers around 60FPS and in heavier instances down to 44-45FPS. Looking at Afterburner the limiting factor is still my CPU though, which is why I want to upgrade that. When I get to the point where my GPU is fully loaded, I'll be happy for now as I know then I have enough CPU power to run other stuff at the same time as ED.
 
I'm bottlenecking currently on a 1080ti.

I don't think you are out of ASW at all with that gpu and what you consider to be ASW is actually fallung under the 45fps barrier.

ASW is so good at maintaining the illusion of high fps that you can almost not tell the difference at all until you go even further down.
 
Last edited:

Arguendo

Volunteer Moderator
I'm bottlenecking currently on a 1080ti.

I don't think you are out of ASW at all with that gpu and what you consider to be ASW is actually fallung under the 45fps barrier.

ASW is so good at maintaining the illusion of high fps that you can almost not tell the difference at all until you go even further down.
I am fully aware that my GPU will be a bottleneck, but that's acceptable to me. Having the CPU bottleneck as it does now is worse for me though, as it interferes with other programs running in the background (like macros run by VA). That's why I am considering upgrading my CPU, not to have 90 FPS everywhere ;)

Also, not too into the ASW other than turning it off (CTRL+NUMPAD 1) every time I start the game. What else am I missing here?
 
Also, not too into the ASW other than turning it off (CTRL+NUMPAD 1) every time I start the game. What else am I missing here?

If your frame rate dips below 90fps, the game will drop to 45 fps, and Rift's ASW algorithm will generate interpolated frames based on previous frame/motion data to generate every second frame so the headset still ultimately displays a 90fps image. Half are from the game, the other half are generated by ASW. This should be smoother and result in less stuttering than having ASW off (provided you can hit at least 45fps of course). This stuff is somewhat subjective though. Some people think ASW is smoother, some think ASW off is smoother. Personally, I find either one too stuttery in Elite, but ASW in DCS is smooth as hell for me. No idea what's happening there.

I'd at least give ASW a shot, since I do find it's better to have it on in Elite, even though it doesn't completely eliminate stutter when <90fps.
 
If your frame rate dips below 90fps, the game will drop to 45 fps, and Rift's ASW algorithm will generate interpolated frames based on previous frame/motion data to generate every second frame so the headset still ultimately displays a 90fps image. Half are from the game, the other half are generated by ASW. This should be smoother and result in less stuttering than having ASW off (provided you can hit at least 45fps of course). This stuff is somewhat subjective though. Some people think ASW is smoother, some think ASW off is smoother. Personally, I find either one too stuttery in Elite, but ASW in DCS is smooth as hell for me. No idea what's happening there.

I'd at least give ASW a shot, since I do find it's better to have it on in Elite, even though it doesn't completely eliminate stutter when <90fps.

Yeah pretty much but ASW actually extrapolates. Interpolation fills gaps. Spacewarp is future frame rendering based on the predicted motion offset from the buffer content of the last v-sync to the present v-sync.
 
If your frame rate dips below 90fps, the game will drop to 45 fps, and Rift's ASW algorithm will generate interpolated frames based on previous frame/motion data to generate every second frame so the headset still ultimately displays a 90fps image. Half are from the game, the other half are generated by ASW. This should be smoother and result in less stuttering than having ASW off (provided you can hit at least 45fps of course). This stuff is somewhat subjective though. Some people think ASW is smoother, some think ASW off is smoother. Personally, I find either one too stuttery in Elite, but ASW in DCS is smooth as hell for me. No idea what's happening there.

I'd at least give ASW a shot, since I do find it's better to have it on in Elite, even though it doesn't completely eliminate stutter when <90fps.

And even if you use the keyboard command to disable it, if performance, or frame times get high enough it will still trigger.
Trust me, you want that too happen.
With a 1060 I would honestly force ASW to on, and leave it there.
 

Arguendo

Volunteer Moderator
If your frame rate dips below 90fps, the game will drop to 45 fps, and Rift's ASW algorithm will generate interpolated frames based on previous frame/motion data to generate every second frame so the headset still ultimately displays a 90fps image. Half are from the game, the other half are generated by ASW. This should be smoother and result in less stuttering than having ASW off (provided you can hit at least 45fps of course). This stuff is somewhat subjective though. Some people think ASW is smoother, some think ASW off is smoother. Personally, I find either one too stuttery in Elite, but ASW in DCS is smooth as hell for me. No idea what's happening there.

I'd at least give ASW a shot, since I do find it's better to have it on in Elite, even though it doesn't completely eliminate stutter when <90fps.

And even if you use the keyboard command to disable it, if performance, or frame times get high enough it will still trigger.
Trust me, you want that too happen.
With a 1060 I would honestly force ASW to on, and leave it there.

Thanks to both of you. I didn't know that it triggered even if manually turned off.

My game stuttered badly with it turned on, especially in and around stations, which is why I always turn it off. As soon as I did that the stuttering quit and even if I only hit 44-45fps at stations it's smooth as butter. With ASW on it does my head in :eek:
 
Thanks to both of you. I didn't know that it triggered even if manually turned off.

My game stuttered badly with it turned on, especially in and around stations, which is why I always turn it off. As soon as I did that the stuttering quit and even if I only hit 44-45fps at stations it's smooth as butter. With ASW on it does my head in :eek:

Smooth as butter at 44 FPS no asw?
What is this witchcraft ? 😂

It's a no from me
 
there's a difference between auto and force on...have you tried force on? I actually really like it on, lets you pump up settings and keep some headroom instead of worrying about 90fps everywhere
 
there's a difference between auto and force on...have you tried force on? I actually really like it on, lets you pump up settings and keep some headroom instead of worrying about 90fps everywhere

Yeah, i used force on with my Rift for ages with the pixel per display pixel set to 1.8

ASW is alright, you get artifacts and its no substitute for proper 90fps rendering but its a lot better than the Valve and Pimax equivalents.
 
Yeah, i used force on with my Rift for ages with the pixel per display pixel set to 1.8

ASW is alright, you get artifacts and its no substitute for proper 90fps rendering but its a lot better than the Valve and Pimax equivalents.

Yes I agree 90 fps is where it's at. It's also worth noting that at 90 FPS the motion to photon latency will be around 20 milliseconds less which greatly adds to the feeling of presence in game
 
Crap, I thought I had a handle on all of this...think I still do, but I do see my frames drop to 45 more and more. I thought it was related to the 3.3 update, which is when it happened more, but I also have been doing much more combat.
So the implication here might be that my CPU (a humble Ryzen 5 2600) is not enough? It never chugs beyond 60% (and rarely that high) so I cant imagine its hitting some wall and telling the game to throttle down to 45FPS. Even though I have a 1080TI its more likely my graphical configuration of my GPU I would assume, since my GPU always runs high in utilization. And lately I am having so much fun the game I have been ignoring configuration and just playing.

In either case we don't make CPU choices in isolation usually. As much as my machine is dedicated to ED and I believe my Ryzen is more than adequate, I recently was asked to edit 4K video. Suddenly my CPU was a wimp!
ED is not CPU hungry - video editing software is!

Navigating the black happily on a low-mid range Ryzen :)
 
I mean...for me, I just logged cpu/gpu usage for a while and saw which one was getting pegged, and upgraded that. Seems unlikely if your cpu is at 60% usage and your gpu is "high", that it would be a cpu problem. ymmv
 
Back
Top Bottom