FPS drop after F10 map

[Morat]

This is back, please fix it or I'll have to send dry cleaning bills.

 

F10 is a lottery, the first few times you dare to you use it you'll probably be OK. The first time you use it and get the FPS drop (from rock steady 60FPS to 17FPS in my case) it will often clear up after a few seconds. If you dare use F10 any more, you risk being stuck in 17FPS for the rest of your session which really sucks if you're in an MP mission.

Edited December 30, 2024 by Morat

[Dangerzone]

2 hours ago, Morat said:

This is back, please fix it or I'll have to send dry cleaning bills.

 

F10 is a lottery, the first few times you dare to you use it you'll probably be OK. The first time you use it and get the FPS drop (from rock steady 60FPS to 17FPS in my case) it will often clear up after a few seconds. If you dare use F10 any more, you risk being stuck in 17FPS for the rest of your session which really sucks if you're in an MP mission.

It's back? I didn't know it had left. 

My suggestion is to adjust expectations with this one. Considering the F10 / VRAM / Memory leak issues have been around for years without being resolved, my guess is that it's not a simple issue to fix with the current engine (or it would have been solved already). Add to this, given that the graphics are being actively reworked with Vulkan, it's plausible that the plan is for the fix will most likely be with Vulkan when it's out. Personally, I don't expect to see a solution before then, outside of what each user can change to work around this with their particular setup. 

[Morat]

On 12/30/2024 at 10:11 PM, Dangerzone said:

It's back? I didn't know it had left. 

My suggestion is to adjust expectations with this one. Considering the F10 / VRAM / Memory leak issues have been around for years without being resolved, my guess is that it's not a simple issue to fix with the current engine (or it would have been solved already). Add to this, given that the graphics are being actively reworked with Vulkan, it's plausible that the plan is for the fix will most likely be with Vulkan when it's out. Personally, I don't expect to see a solution before then, outside of what each user can change to work around this with their particular setup. 

That's a lot of copium to minimise a game destroying bug.

This needs to be fixed or ED will lose players. I know they don't actually care about that financially since this is a vanity project but if they want it to be credible they need to fix stuff.

[Dangerzone]

5 hours ago, Morat said:

That's a lot of copium to minimise a game destroying bug.

This needs to be fixed or ED will lose players. I know they don't actually care about that financially since this is a vanity project but if they want it to be credible they need to fix stuff.

I'm not excusing it's existence- I'm simply suggesting for your own sanity that you have a look at how long this bug has existed without any official acknowledgement - and whether your expectations of what ED 'need to do' fit within the reality of ED's history and trend over the past few years. (It's existed far longer than this individual thread has been going), and plan accordingly.

You may have taken my post as being pessimistic, but I'm actually being optimistic - in that I'm hoping for this to be eventually resolved (albeit by Vulkan). Optimistic because there's hope / light at the end of a tunnel - even if it's a long tunnel... as I have little expectations that it will be resolved otherwise.

This doesn't mean I agree with it, but my personal opinion on whether that's right, wrong, unacceptable, etc, is irrelevant as ED are going to do DCS their way regardless of what I say or do. So for my own peace of mind, I'll base my decisions on how much time, effort, development, cash and passion I invest into DCS on ED's history and actions... not my expectations on what I think they should or hope they will do. It helps me to manage DCS and be able to enjoy it for what it can currently give. So I look to alternative solutions and workarounds as it's far more likely for me to succeed with these than holding out for ED to fix this in the mean time.

I guess I've been greatly influenced by the advise I heard recently of "We don't get to make the world we live in, only choose how we live in it".

Edited January 1 by Dangerzone

[Morat]

On 1/1/2025 at 11:22 PM, Dangerzone said:

I'm not excusing it's existence- I'm simply suggesting for your own sanity that you have a look at how long this bug has existed without any official acknowledgement - and whether your expectations of what ED 'need to do' fit within the reality of ED's history and trend over the past few years. (It's existed far longer than this individual thread has been going), and plan accordingly.

You may have taken my post as being pessimistic, but I'm actually being optimistic - in that I'm hoping for this to be eventually resolved (albeit by Vulkan). Optimistic because there's hope / light at the end of a tunnel - even if it's a long tunnel... as I have little expectations that it will be resolved otherwise.

This doesn't mean I agree with it, but my personal opinion on whether that's right, wrong, unacceptable, etc, is irrelevant as ED are going to do DCS their way regardless of what I say or do. So for my own peace of mind, I'll base my decisions on how much time, effort, development, cash and passion I invest into DCS on ED's history and actions... not my expectations on what I think they should or hope they will do. It helps me to manage DCS and be able to enjoy it for what it can currently give. So I look to alternative solutions and workarounds as it's far more likely for me to succeed with these than holding out for ED to fix this in the mean time.

I guess I've been greatly influenced by the advise I heard recently of "We don't get to make the world we live in, only choose how we live in it".

Fair enough. I shall ask for the grace to accept that which I cannot change

 

In the meantime, I do feel that bugs capable of inducing genuine nausea should get some priority. Maybe I'm a dreamer!

[Reflected]

Can we please get an official word on this after nearly a year now?

[S D]

+1

You have an official campaign creator asking this question for a long time now.  The F10 map, remains a huge issue for performance loss and game crashes, primarily when pressing F1 and going back into the pit after using F10. Its obviously a memory issue, whether its loading textures back in or map assets, but its reproducible.  It can be somewhat negated by keeping the map zoomed in and centred on your aircraft, zooming out and panning to a different area of the map before going back into the pit exacerbates the problem.  It is more apparent in bigger MP servers, with a lot of units.

In certain situations, i can regain performance by taking the headset off and letting it go into stand by mode, or restarting Virtual Desktop software, but there is no reproducible fix.  The strange thing is, when i do loose the performance, it effectively cuts my fps in half pretty reliably.  

Edited February 7 by S D

[OldFlyer]

It's such an annoying bug, absolutely destroys my FPS in VR. I've found that if I quickly Alt-TAB out and then back again it seems to help.

[Mrgone]

This has been a problem for me as well, for as long as it has been reported by others.

Instead of (Alt-Tab) to fix it,  I found that if I hold my head still before pressing (F-10) and again hold my head still while returning, I do not have the issue.

In other words, moving my head when entering the map or, moving my head when returning back to the cockpit the screen and FPS go haywire.

This might help at least a few of you?

[Chapa]

Same issue here with Quest 3. Occurs at least on the Kola and Afghanistan map at high altitude with F5E and F1CE.

@BIGNEWY Some words from ED would be welcome for sure

[winghunter]

Just a quick update

* The moving map ( F10 map alternative ) now also has a map rotation mode.

* The performance impact on large missions can be changed by changing the update rate.

* OpenKneeboard support is enhanced, for VR.

Free version https://dcs-web-editor.github.io/dcs-web-viewer-deploy/live/

Edited March 3 by winghunter

[Kirula]

Друзья, проблема с падением фпс при смене вида f10 полностью решилась после перехода с windows 10 на windows 11 и редактор больше не тормозит

Edited March 13 by Kirula

[MemphisBelle]

Это не так, у меня Windows 11 и проблема продолжает возникать. Конечно, в основном в виртуальной реальности, но она все же появляется.

[plott1964]

On 1/16/2025 at 3:42 AM, Reflected said:

Can we please get an official word on this after nearly a year now?

@BIGNEWY.... Can you respond to this? Many of us have had to hang up the VR headset. I have read all the forums (very time consuming) very little has improved after utilizing all the advise. Has anyone done anything regarding this specific issue?

[Mr_sukebe]

26 minutes ago, plott1964 said:

@BIGNEWY.... Can you respond to this? Many of us have had to hang up the VR headset. I have read all the forums (very time consuming) very little has improved after utilizing all the advise. Has anyone done anything regarding this specific issue?

Have you tried checking your VRAM usage when opening and closing the F10 map?  Last time I checked, opening F10 required circa 1GB of VRAM.  

Do you have enough spare VRAM to allow that?

BTW, when you say that many have hung up their VR headsets, who are you talking about?

[Darcaem]

3 minutes ago, Mr_sukebe said:

BTW, when you say that many have hung up their VR headsets, who are you talking about?

I've not actually hung up my good old headset yet, but I haven't dare open the F10 in a VR session in months. We are all aware of the problem, what we need is a solution (preferably other than "buy a 5090")

[Qcumber]

I had this issue sometimes, a while ago but not for about 18 months, even with my old setup (5800x3d, rtx4070). It might be worth just going back to basics with no mods etc. As Mr_sukebe says. Check VRAM and RAM usage. 

[Mr_sukebe]

11 hours ago, Darcaem said:

I've not actually hung up my good old headset yet, but I haven't dare open the F10 in a VR session in months. We are all aware of the problem, what we need is a solution (preferably other than "buy a 5090")

 

Do you know anyone who's hung up their VR headset as a result?

[Mr_sukebe]

A key point for me is that I've tried to pull together what feels like a fairly comprehensive set of recommendations on optimisation within DCS. 

When I see people complaining about performance, the way they post often gives me little confidence that they've actually used the search engine before making a noise, and even when provided with guidance, tried to follow it.

For reference, I'm talking about this post:

 

Please, take a scan, it might help.

Edited May 20 by Mr_sukebe

[plott1964]

On 5/19/2025 at 2:19 PM, Mr_sukebe said:

Have you tried checking your VRAM usage when opening and closing the F10 map?  Last time I checked, opening F10 required circa 1GB of VRAM.  

Do you have enough spare VRAM to allow that?

BTW, when you say that many have hung up their VR headsets, who are you talking about?

I believe I fixed it based on the info you provided and by limiting the max FPS to 60. So far so good. Thanks!

Edited May 22 by plott1964

[Morat]

On 5/19/2025 at 9:03 PM, Qcumber said:

I had this issue sometimes, a while ago but not for about 18 months, even with my old setup (5800x3d, rtx4070). It might be worth just going back to basics with no mods etc. As Mr_sukebe says. Check VRAM and RAM usage. 

I, for one, don't use mods. I do get the issue.

[Dragonmaster]

If anyone can't afford a new graphics card with more VRAM like me, I use a workaround with Virtual Desktop since I no longer have F10 problems. I've bound a macro that activates desktop mode (2D Cinema view) in Virtual Desktop and then opens the F10 map. I do the same thing with a different button in reverse. When the map is opened in 2D, the VRAM is barely used and there are no more peaks. You do get a black screen for 0.5 seconds when switching to desktop/VR, but it's better than longer frame drops. I know it's not a real solution, but I'm extremely happy that I no longer have F10 problems since 4 days and wanted to share it. I can push now my grafics to the limit and dont need care about for a buffer for the f10 map

Edited June 8 by Dragonmaster

[cw4ogden]

Still a problem year and a half later.