Bouncing between 36fps and 72fps

[Mike_CK]

I run my Quest 3 at 72hz as I did my quest 2 so I get 36fps. Because the quest 3 has better processors, im finding that sometimes im at 72fps instead of 36. However, once i get lower to the ground or around other stuff it usually drops to 36fps; great.

problem is that it will sometimes jump around between 72 and 36 instead of just dropping and locking at 36. I will see 55, 63, 48, 39, 52, etc…I would have thought  that if it can maintain 72fps, it will. But if it cant maintain 72, it will drop to 36; but doesn’t seem to be the case.

So, how do I FORCE it to run at 36fps and NOT try to get to 72? I DON’T want to keep it from dropping BELOW 36 with ASW. This isn’t a case where im getting less FPS than I want. It’s the opposite. I’m often getting more but spastically.

what can I do to make it stay at 36 with either the quest software or OTT

[Glide]

Set max fps to 35 in game, or set max fps to 36 in options.lua.

[Mike_CK]

Thx. I set it to 40 and it created a “jerky” motion of speeding up and slowing down; just as a 40fps

set it back to 75 and it was relatively smoother; just bouncing around between 36 and 72

my next step is to increase some sliders to use some resources so it CANT get to 72

[-Sky-]

On 6/25/2024 at 3:47 PM, Mike_CK said:

Thx. I set it to 40 and it created a “jerky” motion of speeding up and slowing down; just as a 40fps

set it back to 75 and it was relatively smoother; just bouncing around between 36 and 72

my next step is to increase some sliders to use some resources so it CANT get to 72

Yeah this is annoying, i shouldnt have to increase sliders so it cant get to a certain number

ASW sucks and sometimes these methods to disable it dont work.

I'm gonna try again to properly get ASW disabled im probably doing something wrong, keep it at 72hz and lock ingame to like 60 or 75. then gonna try 120hz and lock to 60fps, no matter how far down i bring the settings, even if on paper it says im getting the full 90 fps with 90hz option, i still see a lot of the jerky motion as if it's 30fps, i dont get it

[Mike_CK]

Yep…that’s the wonderful world of DCS VR. A never ending cycle of turning up and turning down. But…I think it’s unavoidable inasmuch as we fly different modules requiring different levels of resources over different maps also with different requirements. I get a steady 36fps over Syria (now that I turned resolution up to 1.1 on my Quest 3 and left PD at 1.3) but the terrain seems to move a bit…jerky. Not too bad but noticeable when I roll quickly. But on the PG map, at 36fps, terrain is buttery smooth.

 

Edited June 27, 2024 by Mike_CK

[Tomcat388th]

You might already have these hot key commands and I dont know if they apply with the Quest3  but on my Q2 and QPro they worked. 

CTRL+KP1 - Disable ASW 
CTRL+KP2 - Force apps to 45hz, DISABLE ASW
CTRL+KP3 - Force apps to 45hz, ENABLE ASW
CTRL+KP4 - Enable ASW to operate automatically

Even though it says on the one option force 45 enable ASW with my headset set at 72hz it would go 36.

J

[Hippo]

You're probably not going to like this answer, but you might consider getting Virtual Desktop and giving that a try.  No, it's not necessary, and it's not free, but It's another option available to you for when you suddenly get new, unexplicable issues in DCS VR following an update (as I have had happen to me in the past) or a change in phase of the Moon.  And It has an option to lock ASW on.

[Wood]

On 8/2/2024 at 5:48 AM, Hippo said:

You're probably not going to like this answer, but you might consider getting Virtual Desktop and giving that a try.  No, it's not necessary, and it's not free, but It's another option available to you for when you suddenly get new, unexplicable issues in DCS VR following an update (as I have had happen to me in the past) or a change in phase of the Moon.  And It has an option to lock ASW on.

I tried tha virtual desktop and quite honestly the performance was worse on the initial trial. Very jerky.  Granted , haven’t I spent the time tweeting but it’s come down to the attitude “ here we go again with this BS dance” just to make it work properly. 
 

One thing that surprised me was. I was always a believer in running DSC as an admin. Why? I don’t know or can’t remember (it’s been that long) but I read that most users are not running DCS as an admin and so I ended up changing it. Results were must smoother experience. Granted the FPS is jumping 72 to 36-40.

When I was running DSC as an admin it gave more consistent FPS @ around 45-50 but with a lot of micro pauses and freezes with this last update.  
I rather have the smoothness than micro pauses. Saying that , it would be nice if Oculus users did not have to use the Gdamn tool tray every time to keep AWS off. 
 

[Wood]

So after some research and tweaking I found a happy medium for myself on this. I use to have my my FPS set to 75-90. Which would give me 70fps in the air on a good day and 99% of the time jumping between 70 to mid 30’s. My system is not good with an intel i7-6700 with 32 gigs on with 10 and 3080 RTX TI. Out dated to say the least. However, I have the mostly everything set to hi with the exception of  shadows off and traffic off and clouds/ water set on high and medium. 
the past couple of days I tried various this and found that dropping the FPS slider down to a more realistic setting such as 50fps showed a vast improvement on stability towards my fps not varying so much. 
I would still. See the range from staying at 50fps for 85-90% of the time until I would land at an airbase with a lot of objects and found that it would fluctuate between 45 and 36 FPS. where previously I would see a drop to mid 20’s. 
 

I went an additional step for the hell of it and after watching jabbers vram video. We all know that the i7-6700 has only 4 cores and 8 threads so for the hell of it I added the —infinity= thing to see what would happen. Not sure why I saw the results I did but huge change in looking right or left near the ground I would see mini micro pauses prior. After no micro pauses whatsoever ever and an even more stable fps now 95% of the time until it would render multiple objects on the taxi in where I would then see mid 30s until all object rendered completely. 
 

 

Hope this helps. 
 

Wood