VR only F4E problems

[Blackhawk163]

In VR and only on VR (using Pimax CL) any mission launched with the F4 results in a cpu limited 32fps cap. Exiting the module’s mission results in all of DCS to then be frame limited to 32fps regardless of module. 
 

All other modules are fine and run at a much higher FPS (I have it locked at 60). 

I posted this as a bug on the heatblur side twice, but it no avail so far. 

Either this is a DCS thing or Heatblur, either way im at a loss.

2d performance is perfect, no issues. 

[Qcumber]

5 hours ago, Blackhawk163 said:

In VR and only on VR (using Pimax CL) any mission launched with the F4 results in a cpu limited 32fps cap. Exiting the module’s mission results in all of DCS to then be frame limited to 32fps regardless of module. 
 

All other modules are fine and run at a much higher FPS (I have it locked at 60). 

I posted this as a bug on the heatblur side twice, but it no avail so far. 

Either this is a DCS thing or Heatblur, either way im at a loss.

2d performance is perfect, no issues. 

The F4 is very demanding in VR. What you describe has happened to me a few times. I am not quite sure what causes it but it is similar to what has been reported when entering and exiting the map view for some people. This has been attributed to VRAM overflow but I have not noticed any excessive VRAM use.

What are your DCS settings and headset resolution? Do you use QVFR? Does it happen on all maps? 

I would suggest 2 things if you have not already tried them. 1) submit your DCS log file to the Discord log checker. 2) reduce the headset resolution and DCS settings to see if it still happens.

[Blackhawk163]

54 minutes ago, Qcumber said:

The F4 is very demanding in VR. What you describe has happened to me a few times. I am not quite sure what causes it but it is similar to what has been reported when entering and exiting the map view for some people. This has been attributed to VRAM overflow but I have not noticed any excessive VRAM use.

What are your DCS settings and headset resolution? Do you use QVFR? Does it happen on all maps? 

I would suggest 2 things if you have not already tried them. 1) submit your DCS log file to the Discord log checker. 2) reduce the headset resolution and DCS settings to see if it still happens.

From .75 up to 1.0 in Pimax. OPxr tk and or QV, doesn’t matter. All maps. Mind you, a few months ago it worked just fine with the 4080s. There is something happening that’s specific to this module because after its use, DCS is hard locked at 32 fps for all other modules. After exiting the module, I have to restart DCS in order to get back my performance. That’s the part that has me scratching my head.

I’m going to have to check task manager to see what’s going on with CPU/GPU usage (why I haven’t done that before? lol)

Also I’ve been a poor troubleshooter as of late, because I have my system dialed in for the other modules perfectly for my needs that I have been hesitant in making changes to them. Later on I’ll disable OPXrtk and QV to see if that’s something, and even will try Pimax XR to see if there’s any improvement.

DLSS/DLAA is not implemented at all (not needed to get 60 FPS locked with our cards) so that’s not a factor. Even so I did test it with it on, just to check and the issue was still present. 

[Qcumber]

What do the CPU render times look like when this happens? With a 9800x3d they should be around 6-8 ms (my experience with the F4). Are the GPU render times OK? At 60 fps locked they should be below 16.6 ms.

[Blackhawk163]

11 hours ago, Qcumber said:

What do the CPU render times look like when this happens? With a 9800x3d they should be around 6-8 ms (my experience with the F4). Are the GPU render times OK? At 60 fps locked they should be below 16.6 ms.

I failed the troubleshooting 101 checklist, and will be flying crop dusters for a while lol

OpenXRtk is the culprit. Disabled that and everything was right as rain. f4 back to 60 fps, some minor performance spikes with other modules (not enough to reduce so much as a frame), but the f4 ran flawless. Now I know. 

 

Going to see what exactly is going on now with the toolkit.

[Jack Chief]

I got similar setup (a bit weaker CPU - 7900x3D), 4080 and Pimax CL. Since about a month, probably linked to last updates I have terrible screen tearing especially on the ground or when switich from F10 to normal view. It  happens in random intervals takes 30 s then stops, after a minute or so comebs back agai. What is intresting if I hit ESC in single player, the game is paused but tearig is still there, I tapped the headset to go to passthrough mode and lazy, chopped movement was also there!! very strange. I use PImaxXR, Quadview Companion, I am set on 1.1 res in Pimax Play, I don't use DLAA/DLSS at all. I dont have this issue in F-16 at all. Yesterday I turned off the special function of  F-4 phantom WIP reduced simulation and played for about and hour and didnt have any stutters. 

[Hempstead]

Man... in VR, I just look at F4, and my FPS tanks to like 10fps. Gives a new meaning to the phrase "What are you looking at?".