Quest 2 Frame Time jump

[[101VFS] WhiskeyCharlie]

I was flying about one day and had to go into the map. When I got back into cockpit view I had a lag spike that wouldn’t go away. So I quit the game and restarted my PC. I started to open the frame counter and saw my frame time went from 22 all the way up into the 90’s. My frames go down from 35-45 in each eye, down to 5-8 and you bet it makes it unplayable in VR. I noticed this about 6 months ago and it happens nearly every time I go into the F10 map, with few exceptions. I’m not sure what kind of track files you’d want to start with, but I sure could use some help squashing this bug.

[BIGNEWY]

Hi

welcome to the forum 

please let us know your system spec and dcs / vr settings

attach your dcs log my also help, it can be found in saved games dcs log folder. A text file just called DCS 

thanks

[[101VFS] WhiskeyCharlie]

6 hours ago, BIGNEWY said:

Hi

welcome to the forum 

please let us know your system spec and dcs / vr settings

attach your dcs log my also help, it can be found in saved games dcs log folder. A text file just called DCS 

thanks

Yes sir, I have a Ryzen 7 3800X, ASUS 2080 Super, 32gb 3200mhz, Samsung 870 Evo 1TB, Samsung 970 Evo 2TB,  EVGA 700 Watt Bronze. If there's anything else I'm able to provide, I will!

dcs.log

[BIGNEWY]

you are running above your native resolution on the headset so it will put some strain on the system. 

Can you also screenshot your vr tab in DCS 

thanks

[Maverick87Shaka]

From log I can see you have Tacview installed, try to disable the recording on your side and see if you have some benefits.

 

[[101VFS] WhiskeyCharlie]

3 hours ago, Maverick87Shaka said:

From log I can see you have Tacview installed, try to disable the recording on your side and see if you have some benefits.

 

I uninstalled tacview a while back, it’s in the files still though 

3 hours ago, BIGNEWY said:

you are running above your native resolution on the headset so it will put some strain on the system. 

Can you also screenshot your vr tab in DCS 

thanks

I’m able to pull 35-45 fps in each eye with my settings bummed up. The problem still occurs when I’m at native resolution. It happens only when I go back into the cockpit from the F10 map. So I’ve become scared to use it.

[BIGNEWY]

Please try this 

go to C:\Users\micha\Saved Games\DCS.openbeta

rename to C:\Users\micha\Saved Games\DCS.openbetabackup ( keep it as a backup )

run a slow repair of DCS

restart DCS once repair is finished

Login and redo graphics preferences 

Test and see if you notice different results 

[[101VFS] WhiskeyCharlie]

17 minutes ago, BIGNEWY said:

Please try this 

go to C:\Users\micha\Saved Games\DCS.openbeta

rename to C:\Users\micha\Saved Games\DCS.openbetabackup ( keep it as a backup )

run a slow repair of DCS

restart DCS once repair is finished

Login and redo graphics preferences 

Test and see if you notice different results 

Right on time... I've been working on transferring my chair rig to a new cockpit. I'm gonna be in touch with you about some settingsnull

[BIGNEWY]

Please also ensure 

hotplug is disabled in dcs controls page

HAGS is disabled in windows ( Hardware-accelerated GPU Scheduler )

 

 

[[101VFS] WhiskeyCharlie]

2 minutes ago, BIGNEWY said:

Please also ensure 

hotplug is disabled in dcs controls page

HAGS is disabled in windows ( Hardware-accelerated GPU Scheduler )

 

 

Already done.

[[101VFS] WhiskeyCharlie]

I was able to reproduce the issue again today. Even with the settings we went over last night. It seems the only temporary solution is Alt+Tabbing out and spamming it till it returns to normal. This doesn’t always work, in that case I restart DCS. I’ve found a post with a similar issue with the same temporary fix. 

 

[prianik]

 

I have the same problem, if you do not switch to the card at all, then the performance does not drop. And when switching, image breaks occur and the rendering delay jumps up to 80-100ms

[[101VFS] WhiskeyCharlie]

nullI hooked up my rig again, and redoing my settings did make me get 50 FPS in each eye. However, I had to go into the F10 map and happened the 6th time I opened it. Here is the first successful recording of it happening. I put the Track and Log file along with a screenshot of the frame counter.

101VFS_FOOTHOLD_EXPANDED_EDITION_V2.7.4-20230528-100743.trk dcs.log

[MadKreator]

I have quest 2 and quest pro, I get smoothest play with 90hz and 1.3 multiplier in oculus. In the  Oculus tray tool app, I run encode res at “38xx” and bitrate at 500( might need to play with those depending on system), ASW off…but the best settings I’ve done is change the FOV multiplier to .8.. the game is rendering more  than the actual fov that you can see through either the quest 2 or pro. Dropping the fov multiplier too low, you will start noticing the cropped image. Saw another post where someone was down at .7 or .75 and said it was still fine. But .8 seemed to really help smooth things out.. idk what it is about the OTT but I get much smoother performance using it. Startup sequence with the quest seems to make a difference too.. start oculus tray tool, then oculus app, then enable the link cable, then open dcs from the desktop ( not through oculus). If i run dcs without the tray tool in MT or ST it gets choppy and stuttery and very inconsistent fps. 

Edited May 28, 2023 by MadKreator

[[101VFS] WhiskeyCharlie]

27 minutes ago, MadKreator said:

I have quest 2 and quest pro, I get smoothest play with 90hz and 1.3 multiplier in oculus. In the  Oculus tray tool app, I run encode res at “38xx” and bitrate at 500( might need to play with those depending on system), ASW off…but the best settings I’ve done is change the FOV multiplier to .8.. the game is rendering more  than the actual fov that you can see through either the quest 2 or pro. Dropping the fov multiplier too low, you will start noticing the cropped image. Saw another post where someone was down at .7 or .75 and said it was still fine. But .8 seemed to really help smooth things out.. idk what it is about the OTT but I get much smoother performance using it. Startup sequence with the quest seems to make a difference too.. start oculus tray tool, then oculus app, then enable the link cable, then open dcs from the desktop ( not through oculus). If i run dcs without the tray tool in MT or ST it gets choppy and stuttery and very inconsistent fps. 

 

I just got my best FPS yet at 45-50 in each eye with 1.3 PD and 120Hz. I haven't touched tray tool but I use the debug tool and use 250 as the bitrate. I would love to go over the settings since I don't know what it's all about.null

[MadKreator]

I don’t mess with any of them too much lol Bitrate and encoding will probably be based on what your system can handle, mine just happens to work fine on what I set it at, although I’ve seen people say that anything over 350 has minuscule returns. I’ve never used the debug tool but if you can change settings in it, try punching in .8,.8 in the FOV multiplier box.. Thats the only “option” I have set in the oculus tray tool app and the only one I feel really made any difference. I got tired of tweaking settings all the time. In dcs I run the same graphic options I do on 2d screen, except I turn ground shadows off, and set cockpit shadows to med or low those  to me seems to be the biggest performance killer for me in vr. People have said as well setting terrain textures to low instead of high can get rid of the random hard fps drops and frame time spikes ( maybe a MT bug) The Oculus Tray Tool really does seem to help though, might install it if the debug tool doesn’t let you change settings. Its a 3rd party app, not an oculus product.. if you haven’t heard of it before.

VR can be a royal pain in the butt to get tuned right for each particular system, to say the least. 

Edited May 28, 2023 by MadKreator

[[101VFS] WhiskeyCharlie]

1 hour ago, MadKreator said:

I don’t mess with any of them too much lol Bitrate and encoding will probably be based on what your system can handle, mine just happens to work fine on what I set it at, although I’ve seen people say that anything over 350 has minuscule returns. I’ve never used the debug tool but if you can change settings in it, try punching in .8,.8 in the FOV multiplier box.. Thats the only “option” I have set in the oculus tray tool app and the only one I feel really made any difference. I got tired of tweaking settings all the time. In dcs I run the same graphic options I do on 2d screen, except I turn ground shadows off, and set cockpit shadows to med or low those  to me seems to be the biggest performance killer for me in vr. People have said as well setting terrain textures to low instead of high can get rid of the random hard fps drops and frame time spikes ( maybe a MT bug) The Oculus Tray Tool really does seem to help though, might install it if the debug tool doesn’t let you change settings. Its a 3rd party app, not an oculus product.. if you haven’t heard of it before.

VR can be a royal pain in the butt to get tuned right for each particular system, to say the least. 

 

There’s FOV tangent multiplier, is that the one?

[MadKreator]

1 hour ago, [101VFS] WhiskeyCharlie said:

There’s FOV tangent multiplier, is that the one?

Yes I believe so. OTT calls it something a little different. I will look in the debug tool  when running OTT and see how it is configured