FPS drop after F10 map

[MemphisBelle]

On 5/17/2024 at 10:40 AM, AhSoul said:

Quest3. I'm using VirtualDesktop. I wasn't talking about constant stutter there - I have none of that. I was talking about the FPS stutters/drops after coming out of F-10. I'm not sure why bitrate would affect that specific situation.

Oddly the stuttering was a lot worse last night - It would last for a good minute or two before going away. Only thing I can think of that was different to the last week's flying was that I was using the Viggen pretty much exclusively last night.

 

have you changed the Bitrate in your OculusDebugTool? Dont forget that the Quest 3 works differently than other native PC VR Headsets. The Quest Link is streaming the image which might be affected if some settings are not set. The only issue I have when returning back from the F10 map is, that the image is overall overblended for a few seconds (too bright). I have not yet been able to track down the reason for that issue.

[AhSoul]

18 hours ago, MemphisBelle said:

have you changed the Bitrate in your OculusDebugTool? Dont forget that the Quest 3 works differently than other native PC VR Headsets. The Quest Link is streaming the image which might be affected if some settings are not set. The only issue I have when returning back from the F10 map is, that the image is overall overblended for a few seconds (too bright). I have not yet been able to track down the reason for that issue.

I'm using Virtual Desktop so my bitrate etc. is set in that. OculusDebugTool only affects wired connections I believe.

The F-10 issue makes the whole framerate of the system chug - I don't think that's the same as a bitrate issue to the headset itself. Also not everyone experiencing this issue is on a Quest headset either.

Edited May 19, 2024 by AhSoul

[MemphisBelle]

19 hours ago, AhSoul said:

I'm using Virtual Desktop so my bitrate etc. is set in that. OculusDebugTool only affects wired connections I believe.

The F-10 issue makes the whole framerate of the system chug - I don't think that's the same as a bitrate issue to the headset itself. Also not everyone experiencing this issue is on a Quest headset either.

 

That is correct and the meta Quest 3 is wired via Link cable. You can of course also use Air Link via WLAN, but that is not recommended in DCS as its too instable...except you sit right next to the router.

The entire F-10 map is a strange concept as its a recreation of the entire map in just a different view, even trees are moving in the wind. 

[AhSoul]

1 hour ago, MemphisBelle said:

That is correct and the meta Quest 3 is wired via Link cable. You can of course also use Air Link via WLAN, but that is not recommended in DCS as its too instable...except you sit right next to the router.

The entire F-10 map is a strange concept as its a recreation of the entire map in just a different view, even trees are moving in the wind. 

I'm using Wifi6 right next to the router. As said, I don't think this is a bitrate issue as it's not just a Quest issue.

I had no idea it actually modelled the trees! I guess there's something about swapping from that view of the entire mission back to the normal cockpit view that is significantly intensive in some situations then....

[DeTesla]

I never press F10, at all.

Youre just asking to get a bad experience which lasts until you exit the game. It is simply not worth it!2

On 5/20/2024 at 9:32 AM, MemphisBelle said:

That is correct and the meta Quest 3 is wired via Link cable. You can of course also use Air Link via WLAN, but that is not recommended in DCS as its too instable...except you sit right next to the router.

The entire F-10 map is a strange concept as its a recreation of the entire map in just a different view, even trees are moving in the wind. 

Well.. Thats not good for VR performance at all. Who even came up with that concept?! Wouldnt it be easier to just use a large png image?

[Bullant]

May or may not be related.

I have been having terrible lag lately in the main menu screen, to the point of not even being able to start a mission. Only happens in VR, not on flat screen. Spent hours yesterday slowly changing options, until I switched DLAA back to MSAA and the problem is totally gone. Also haven't had the F10 problem since then, so might be related?

 

Edited May 24, 2024 by Bullant

[IronRaph]

The F10 map bug is an important issue with DCS and it is still not addressed!

The main issue comes from the texture manager that is doing a crappy job at loading/unloading textures from the GPU VRAM.

As a result, as soon as you open the F10 map, your VRAM is filled up with the map data.... once you get back to F1, the VRAM is not freed. Your GPU will not be used at 100% anymore as the VRAM is full.

The only working workaround I have found:

• use Virtual Desktop - it consumes 256 MB of VRAM instead of 2Go for Oculus!!
• once you have opened the map try to alt tab (chance focus) the application
  • ideally do it when you are in the briefing or settings menu
  • it seems to release the VRAM once you refocus to DCS
• it seems to work also well to go back to 2D and then VR using Quest double tap on the left home button and Virtual Desktop
   

It doesn't work all the time immediately but at some point it is... I am getting 80 FPS on Enigma using MSSx2 even if I open the F10 map...
But clearly ED must look at this issue as it is a real pain in the ass!

[GladiatorDPR]

This F10 map stutter fest is an absolute pain in the rear and vomit inducing trash. ED needs to fix this crap immediately. Trust me it's not the systems at play but something with EDs software and that map.

 

I'm on 7950x3d 4090 with 64gbs of ram. Otherwise no matter what module or map it runs smooth as silk but let me tell ya if I need to check that stupid map all hell breaks loose. 

 

FIX IT ED!!!! 

[Qcumber]

I have not experienced this issue for the last few updates. It only affected me when using the F-14 on the Syria and Marianas maps; occasionally rather than all the time.

I have a 4070 so is it a VRAM issue or something else? I am using DFR so this is less GPU demanding and perhaps helps manage VRAM more effectively!?

[tomeye]

Same here, it is much better now switching f1 - f10 - f1. Not sure if it was mentioned in any change log of the recent updates.

I think it was caused by significant unloading/loading of VRAM or process prioritization.

@Qcumber I am on 3080ti with 12GB vram and still this mod is extremely useful with memory load.

 

[KoN]

I don't think it's fixed I was online tonight and my memory was maxed out , and that's switching between cockpit and f10 map because you have to in competitive servers . Every time I switch back and forth more and more stutters began , became unpleasant in VR . MY Vram was at maximum. And that's 16GB of vram . I'm beginning to loose faith in this . Nothing gets fixed  Anymore . 

Still no fix from replay. The list goes on and on . 

The spotting is awful in VR . 

MT load times feel like it's on a hard drive not a SSD . 

Jee I'll be here all night . 

[tomeye]

Ι feel your pain with VRAM but the above mod I shared made all modules flyable.

[piolin23000]

Yes Tomeye it's very good, buuuuut you forget to say something very import, when you load that modules, the TAZ modules, your DCS load in the double or triple time, every time to load DCS  the load it's very very long to load, and finally works good but sooner or later the F10 map low your fps, i finally follow the recommendation from here and low all my settings from DCS and some times working, sometimes not Working and i back to my old method, use the LINK CABLE, my Virtual Desktop never never works for me and some times freeze my VR when i use f2 or f-10 map, my recommendation it's use the OTT with Open XR tools, Link Cable with Quest 3, i know the Virtual Desktop look very very good and fine but not working that all, i use i5 12th 12600, RTX 3060 Ti, 2 tb SSD only for DCS, 1 TB ssd for W11 and 64 GB RAM, if someone have the solution for the VD and the problem with the F10 map please show as how to fix it 

 

happy landings for everyone

Wolfpack  

[tomeye]

16 hours ago, piolin23000 said:

Yes Tomeye it's very good, buuuuut you forget to say something very import, when you load that modules, the TAZ modules, your DCS load in the double or triple time, every time to load DCS  the load it's very very long to load, and finally works good but sooner or later the F10 map low your fps, i finally follow the recommendation from here and low all my settings from DCS and some times working, sometimes not Working and i back to my old method, use the LINK CABLE, my Virtual Desktop never never works for me and some times freeze my VR when i use f2 or f-10 map, my recommendation it's use the OTT with Open XR tools, Link Cable with Quest 3, i know the Virtual Desktop look very very good and fine but not working that all, i use i5 12th 12600, RTX 3060 Ti, 2 tb SSD only for DCS, 1 TB ssd for W11 and 64 GB RAM, if someone have the solution for the VD and the problem with the F10 map please show as how to fix it 

 

happy landings for everyone

Wolfpack  

tbh I have been using the above mode for very long time which means I would not have noticed the difference in loading times. Even with additional load times, the VRAM stays below 100% which makes every module flyable with VR and my setup.

[Whisper]

Definitely NOT fixed for me.

13600K, 32G RAM, 3070, VR on Rift S with very low settings.

F10 means instant slideshow. How is that not fixed since February is beyond me.

Edited June 17, 2024 by Whisper

[Yoti]

Been happening for me for a few months now too. Extremely annoying. 

[Reflected]

It's happening to me on every mission, I can check the F10 map 2-3 times before my FPS drops to 5. It can be solved every time by alt tabbing out , opening something else, closing, alt tab back. Super annoying.

[MemphisBelle]

On 6/12/2024 at 9:33 AM, Whisper said:

Definitely NOT fixed for me.

13600K, 32G RAM, 3090, VR on Rift S with very low settings.

F10 means instant slideshow. How is that not fixed since February is beyond me.

sorry, what? Very low settings? Your setup is beyond mainstream and rather considered HighEnd. I used to have a Rift S using the same processor and a RTX 3080 with maxed Out settings and max FPS.

I wonder what storage you use, I have DCS installed on an M.2 NVME 2TB (Samsung 980 Pro) and I have 64Gb of DDR5 RAM and Win 11. May be these are the differences.

[Whisper]

2 hours ago, MemphisBelle said:

sorry, what? Very low settings? Your setup is beyond mainstream and rather considered HighEnd. I used to have a Rift S using the same processor and a RTX 3080 with maxed Out settings and max FPS.

I wonder what storage you use, I have DCS installed on an M.2 NVME 2TB (Samsung 980 Pro) and I have 64Gb of DDR5 RAM and Win 11. May be these are the differences.

Wow, my bad!!! I wrote the wrong type of GPU, I'm on a 3070! Lack of VRAM, I step down settings because of this

Edit : I edited my original post

Edited June 17, 2024 by Whisper

[Reflected]

Is there any official word on this? Apparently the February update made it very bad for a lot of people, it's not like our hardware became outdated from one day to another. Something is really wrong with how DCS uses VRAM. Any plans or solutions in the pipeline please?

[Heroman30]

I'm having a similar issue. My FPS is fine when during the flight but as soon as I check the f10 map (which is essential on a MP server), my FPS becomes really unstable, and my quest 3 headset becomes laggy in my right eye. Its like as if my headset or graphics card cant sustain going in and out of the F10 map view. Could it be a VRAM issue as I only have a 10GB card? I have set my textures to medium to help reduce VRAM load. 

[Loukuins]

This issue was fixed for a few month and came back, it's EXACTLY the same issue as before (aka 2021) and it's crazy they still can't understand and acknoledge stuff like that... I changed my PC completly and I have the same issue as back in 2021 when people told me it's my PC the issue.

[Dangerzone]

12 hours ago, Heroman30 said:

I'm having a similar issue. My FPS is fine when during the flight but as soon as I check the f10 map (which is essential on a MP server), my FPS becomes really unstable, and my quest 3 headset becomes laggy in my right eye. Its like as if my headset or graphics card cant sustain going in and out of the F10 map view. Could it be a VRAM issue as I only have a 10GB card? I have set my textures to medium to help reduce VRAM load. 

From what I can gather, it is a VRAM issue. I have personally noticed that since upgrading to a 24GB VRAM graphics card, I don't have the issues like I used to. 

Task-switching out of DCS to the desktop to another application, and then going back into DCS has reportedly fixed it in a number of users cases. Not sure exactly what the go is - but it seems as though windows must do a VRAM cleanup/release when applications change or something.  Hopefully this workaround works for you, because otherwise it may be until Vulcan before we see a resolution for this. 

[Reflected]

37 minutes ago, Dangerzone said:

From what I can gather, it is a VRAM issue. I have personally noticed that since upgrading to a 24GB VRAM graphics card, I don't have the issues like I used to. 

Task-switching out of DCS to the desktop to another application, and then going back into DCS has reportedly fixed it in a number of users cases. Not sure exactly what the go is - but it seems as though windows must do a VRAM cleanup/release when applications change or something.  Hopefully this workaround works for you, because otherwise it may be until Vulcan before we see a resolution for this. 

Yes this is a known workaround but still not OK having to do this on every mission. Also, yes, it's a VRAM issue, but if from one update to the next the game becomes nearly unplayable, yes of course it can be solved by buying even more and more VRAM and better gear, but it's not a real solution. The solution is to fix the code. Every time you mess it up you can't throw your hands up and tell everyone their PC is officially outdated from this day on.

[AhSoul]

I'm hoping that this will mean I need to use the F-10 map a lot less:

Coming out in a couple of days apparently