Nothing in between 45 to 90 fps? And Rift debug too = bettter FPS

[kiario]

Hi,

Testing out the hardware a Little to understand its effects when changing options and trying to squeeze maximum fps from my rig.

I noticed that when disabling ASW and with All settings to ULTRA and HMD quality to 1 I get 90 fps when using the ctrl f command. It shows the fps on screen not in the rift.

1. However it never goes above 90 even if I lower settings?
2. If I raise HMD quality to 1.5 or above it is still smooth in game but on screen it shows 45 fps. Never 46-90. Always 45 and under? How come?

Third, is a tip. I have tested quite a lot with debug tool pixel density at 2 and HMD quality at 0.85 in game and it certainly gives both better image and more stable 90 fps than setting HMD quality to 1.75 and SS to 1.25.

 

[Tepescovir]

it will never go above 90 as it is the refresh rate of the vive and rift , Also vr uses vsync which syncs your framerate to your monitors refresh rate for smoothness, so ie, 90 hz screen = 90fps with vsync.

steamvr has "allow interleaved reproduction" it will half your framerate to 45 if it cant maintain 90 fps for a moment or so,I think the rift also has an equivalent now , but dont know what it's called on the rift

 

[Alec Turner]

If you're seeing it at either 45 or 90 then it really sounds like ASW is still on. You're turning it off by pressing Ctrl + NumPad 1 right? (and I think NumLock has to be on too). With ASW off you really should start to see values in between.

 

[kiario]

If you're seeing it at either 45 or 90 then it really sounds like ASW is still on. You're turning it off by pressing Ctrl + NumPad 1 right? (and I think NumLock has to be on too). With ASW off you really should start to see values in between.

Hi. I was turning it off in the debug tool. It was off because the hud lines had no jitter.

 

[dogbite]

Hi,

Testing out the hardware a Little to understand its effects when changing options and trying to squeeze maximum fps from my rig

I noticed that when disabling ASW and with All settings to ULTRA and HMD quality to 1 I get 90 fps when using the ctrl f command. It shows the fps on screen not in the rift.

1. However it never goes above 90 even if I lower settings?

R:90 is max and ideal in VR

2. If I raise HMD quality to 1.5 or above it is still smooth in game but on screen it shows 45 fps. Never 46-90. Always 45 and under? How come?

R:ASW is still on as Alec points out use Ctrl/NP1 to turn off after Home is running and make sure Numlock is on.

Third, is a tip. I have tested quite a lot with debug tool pixel density at 2 and HMD quality at 0.85 in game and it certainly gives both better image and more stable 90 fps than setting HMD quality to 1.75 and SS to 1.25.

R: here's a tip -debug tool pixel density and in game HMD quality setting are the same thing. Just set it in game. try leaving SS at 1 -not a lot of value higher in VR, especially while cranking pd. Leave AA off, if you haven't, as no real value at these pd enhanced res' either.

 

[X-Terminator]

Disabling ASW (CTRL+Numpad1) does not stop ASW from capping to 45fps. It simply removes the extra added frames.
I see mine wander about 80 to 90 in menus but in the game it is capped down to 45fps and wanders down to 30fps in RES and Stations.
ASW is to make the frames more smoother and regular so it can then add the frames between. If it was jumping always between 45-90 then it would need to calculate each different half-frame and would be more process. When this figure is a known number it applies the added frame efficiently.

Unfortunately, it was intended to cater for slower systems but on most other than i7 it simply does not work with fast action 360 movement games (ED and Project Cars).

It therefore should have a Disable function in Oculus Home and also NOT cap all the fps to either just 45 or 90. We are being robbed our full potential. Although 45 is very good indeed. If only it was 45 for RES & Stations also!

 

[TorTorden_VR]

I disagree.

Elite has enough places that anything but monster machines gets low fps, especially res's and busy surface instances, with asw enabled and yoy look at the fps counter, you either get back 85-90.
Or it throttles to 45.
Turning it off doesnt mean you wont get low fps, but you will see fps between 45 and 80.

For many systems though elite either give you full fps, or it completely clogs it.
For instance he transition between cruise and a RES isn't exactly gradual.
I get 90 easy in cruise, but in res i would be lucky to see anything above 60, and i would then pick ASW above that everytime.
In fact before ASW I would literally avoid resource sites, because it just wasn't playable.

ASW is brilliant when you have enough headroom. But in these places that are busy enough you dont have enough regardless and It looks horrible, but the same situation without would be as bad or worse without ASW.

This is where i would notice my old i5 was holding me back, having upgraded to an i7 gives me a little more headroom, but far from being enough to turn asw off.

But with vr, looking at fps is very myopic and clinging to an old concept of gaming performance.
For vr its more misleading than anything.
What people should be concerned with is rendering times if you want a simplified metric.

So install fcat and start doing captures.

 

[X-Terminator]

Disagree with me? If so your state concurs with my findings. ASW is best suited to i7 and the commercial business model push they have towards forcing us to think we must get new Systems. I proved them wrong. Now if they did as suggested they would have to remove their recommended System down to a 10yr cpu. Doesn't sound like good business that way now does it.

 

[TorTorden_VR]

No ASW doesnt push for i7's.

What ASW does is simply make sub 75fps playable at all and vr optimised games certainly doesnt need an i7 to make use of it.

ED isnt a vr optimised game at the same time as doing more than any vr only game. So we end up having to brute force it.

ASW might seem like an issue, but regardless of it being disabled or not, these places would force your fps below 45 anyways, and when the game cant maintain 45 with headroom to generate the false frames it looks horrible.

But playing without is still as bad.

In short there is no point to disable ASW, of you get into the situation where it can't keep up you need to decrease settings.

And if you are of the misconception there hasn't been real development in cpus the last decade, or even just the last few years you are just being grossly naive.

VR regardless of plattform is cutting edge.
Its not going to be mainstream for another decade.
Being an early adoptor is as a consumer a very bad idea, equipment cost is nearly astronomical and will need to be top end and cutting edge.
And the next generarion of thst equipmemt will make the previous generation nearly worthless.

If you expect to be able to play with a 10 year old rig, well do so at your own risk but dont if you can't.

 

[dogbite]

Disabling ASW (CTRL+Numpad1 does not stop ASW from capping to 45fps.

Sure it does. With ASW off the only cap is 90 fps.

 

[X-Terminator]

Sure it does. With ASW off the only cap is 90 fps.

LOL you are wrong. Since ASW was introduced last November it has always took over and capped at 45 if 90 is not maintained. Disabling simply removes the added frames.

I do know because I can never get ED at 90fps in the game due to using a 10yr cpu which can manage quite fine. Those extra fps from 45 to 85 (my peak in game) could have been used to let drift instead of capped down to 45.

 

[dogbite]

LOL you are wrong. Since ASW was introduced last November it has always took over and capped at 45 if 90 is not maintained. Disabling simply removes the added frames.
QUOTE]

Read your words and my response again. You said
"Disabling ASW (CTRL+Numpad1 does not stop ASW from capping to 45fps".

"Disabling" ASW "stops" it period-it is OFF. In what world does turning something off not stop it? If it is off, it's off -and does nothing. This would including capping to anything-it's off. How am I wrong?

edit
Oh and your above statement "Disabling simply removes the added frames"- When ASW is disabled and 90 fps can't be maintained ATW (not the now disabled ASW) takes over to fill in the missing frames to try and maintain 90 fps by duplicating a previous frame. There is no drop to 45 fps with ATW, That is a function of ASW (when it is enabled).

 

[X-Terminator]

If only. However daft it sounds, Disabling ASW via the hotkey (CTRL+Numpad1) does NOT disable capping to 45fps. You see, your system may handle 90fps yet when it can not it will also cap to 45. Ask OP too as you assume he hasn't already Disabled it.

If so many Oculus Users get better results, especially for ED the very best VR game so far yet not "VR optimized", with ASW Disabled via the hotkey then it really should be in Oculus Home as an Option. I have requested this so many times already. They have at least looked into the Jumps/Grey outs/Flashes issue whereby setting separate Affinity cores resolves this. I bet you they are in denial as they'll claim it's ED's fault for not being optimized whilst it was fine in 1.12

We have here the exact same problem of 2 Sides at head to head and neither will give way just like the Pvp Bounty Hunting/Piracy can not become viable whilst the majority are running away into PvE groups. There is a solution here but neither will kiss!

 

[dogbite]

If only. However daft it sounds, Disabling ASW via the hotkey (CTRL+Numpad1) does NOT disable capping to 45fps. You see, your system may handle 90fps yet when it can not it will also cap to 45. Ask OP too as you assume he hasn't already Disabled it. /QUOTE]

I am not assuming anything. Only saying ATW does not , never has cut the fps to 45. It only fills in missing frames as far as it can keep up.That is how Oculus designed it. When it can't you get JUDDER. The more it misses the 90 fps by, the worse the judder.
Dropping to 45 is only a function of ASW and as pointed out by above Steam's interleave. So if 90 drops to 45 when 90 is not achieved either ASW is still on despite any attempt to turn it off or Steam is involved.

When I turn off ASW on my CV1, ATW takes over. When a fps goes to 80 it reports 80, when it goes to 63 it reports 63 not 45. No 45 cap EVER in this scenario and that is the way Oculus intended. This is also how the vast majority experience that. Op is using game framerate counter. Perhaps using the debug performance hud for framerate, etc will enlighten him more. Those that find these features working as designed are not the one's that are wrong or making assumptions. On the contrary.

 

[X-Terminator]

When I turn OFF ASW it caps to 45fps both in Oculus Debug Tool 1.13 plus the monitor's frame rate CTRL+F.
It will only ever drift between 45 to 90 whilst in System Map. Not in GalMap and not even on VR Low Setting.
My install of Oculus is from pre-SSE4.2 (Runtime1.7) but updated to 1.14 so all I can say is ED likes Hyperthreading although many games do not require this. Oculus push for this however but a steady 45fps is totally acceptable. If only it was steady in RES & Stations here.

 

[kiario]

I run the game with ASW on. All settings on max in graph options except AO which is off and shadows at high.
I have the pixel density set to 2 and ingame hmd set to 0.85. Since there is no 1.85 only 1.75 in game.

With this I get 90 fps and super smooth movements all the time even on planet surfaces. So I am happy with that.
Picture quality is really good actually. All text readable at standard hud settings. I have a I7 4930K at 4.5 Ghz which sits around 45% CPU usage in game.
And also a MSI 1080 slightly OC'ed.

Disabling ASW with these settings naturally gets quite stuttery and fps on monitor reports to 45 all the time.
But if I change the pixel density to 1 then fps is still reported to 45 but game is super smooth again as 90 fps exactly.

 

[Alec Turner]

LOL you are wrong. Since ASW was introduced last November it has always took over and capped at 45 if 90 is not maintained. Disabling simply removes the added frames.

I do know because I can never get ED at 90fps in the game due to using a 10yr cpu which can manage quite fine. Those extra fps from 45 to 85 (my peak in game) could have been used to let drift instead of capped down to 45.

Not for me. With ASW on I get either 45 or 90. When I press Ctrl + NumPad 1 I start to see 90, 85, 87, 70 ... all sorts of different numbers.

 

[kiario]

1. However it never goes above 90 even if I lower settings?

R:90 is max and ideal in VR

2. If I raise HMD quality to 1.5 or above it is still smooth in game but on screen it shows 45 fps. Never 46-90. Always 45 and under? How come?

R:ASW is still on as Alec points out use Ctrl/NP1 to turn off after Home is running and make sure Numlock is on.

Third, is a tip. I have tested quite a lot with debug tool pixel density at 2 and HMD quality at 0.85 in game and it certainly gives both better image and more stable 90 fps than setting HMD quality to 1.75 and SS to 1.25.

R: here's a tip -debug tool pixel density and in game HMD quality setting are the same thing. Just set it in game. try leaving SS at 1 -not a lot of value higher in VR, especially while cranking pd. Leave AA off, if you haven't, as no real value at these pd enhanced res' either.

I have AA at SMAA or what it is called and makes a big difference in wandering jaggies lines.

 

[CylonSurfer]

When I turn OFF ASW it caps to 45fps both in Oculus Debug Tool 1.13 plus the monitor's frame rate CTRL+F.
It will only ever drift between 45 to 90 whilst in System Map. Not in GalMap and not even on VR Low Setting.
My install of Oculus is from pre-SSE4.2 (Runtime1.7) but updated to 1.14 so all I can say is ED likes Hyperthreading although many games do not require this. Oculus push for this however but a steady 45fps is totally acceptable. If only it was steady in RES & Stations here.

CTRL+1 turns off ASW for me - I see my frame go from 45 to 70 - 90fps as soon as I disable it in a station and then return to 45 when I enable it again.

 

[dape]

Not for me. With ASW on I get either 45 or 90. When I press Ctrl + NumPad 1 I start to see 90, 85, 87, 70 ... all sorts of different numbers.

+1 ...