Fps loss 50% near water/sea and drawing of fences

[609_Relentov]

I've been following this thread with interest, as I have been experiencing the massive FPS loss in the upper part of the map as well - mainly when looking northeast when piloting various jets and helo's.  For context, I have a mission where the play area is around Rostok (around 50-60 mi west of Peenemunde).

I have my FPS maxed at 60 as I use VSync, and after lowering various settings I was still seeing the FPS drop from 60 down to the mid-teens/twenties and (sometimes less than 10 for brief periods) when looking north east from that play area!

I tried @Spicysauced suggestion of lowering the precaching values for around_camera and around_objects, but didn't see much difference.  BTW, based on relatively recent DCS updates, it is suggested by ED to use an autoexec.cfg file in the saved games/config directory instead of the installed directory/config/graphics.lua (since any edits would be reset after every update).  Just be sure to precede settings with "options.graphics.", e.g.:

options.graphics.Precaching =
{
    around_camera = 10000;
    around_objects = 5000;
    around_types = {"world", "point"};
    preload_types = {"map", "world", "mission"};
}

So, I tried one more thing I had read from spicy that seems to have made a huge difference - namely he said he had a 50GB swap file.  I noticed mine was Windows managed (currently around 4.5GB), so I manually set it to min/max of 20GB and rebooted, and WOW!  My FPS on the CW Germany map in the north is pegged at 60 for the most part no matter where I look (including northeast)!

So, something to consider, check out your VM/Swap file size, and if it's Windows managed (which probably means smaller than ~10GB), try manually setting it to 20GB or higher, and see if that helps.

(EDIT:  One note, when I jumped in a new/different jet - an F4E - I noticed my FPS did drop from 60 down to the twenties when looking northeast, but after about 20 seconds, they stabilized and I was back at 60 when looking anywhere, so there seemed to be some loading of textures or something).

(EDIT #2:  Ok, so I jumped into an F-16C for the first time since loading the mission, and the FPS was 60 until I looked northeast and it dropped to the high twenties/low thirties, and it didn't go up after a while (minute+);  So, I exited and increased the VM/swap file from 20GB to 30GB and rebooted, and reloaded the mission.  This time, I was back to 60FPS looking northeast even after jumping in the F-16C, and a few other aircraft/helos, so for me at least 30GB was the magic swap file size.  I agree this still seems to be a bug with the map, but at least for now it's more playable for me.)

(EDIT #3: Last edit for now, continuing on the comments above, I reloaded the mission and things seem OK after jumping in a few aircraft, but when I tried the F4E for the first time, when looking northeast the FPS dropped from 60 to low thirties again, and stayed there (while looking northeast).  So, I jumped in another jet (FPS at 60, so all good), then back in the F-4E again, and this time it was at 60 even looking northeast.  It's unclear why after spawning in another aircraft and back to the F4E caused the FPS to be back to normal (i.e. no drop), but something to consider if you see the same pattern, until this is fixed.)

(EDIT #4: Final final edit lol  ;  After flying the mission in the F4E for about 20 minutes, I noticed that when looking northeast the FPS dropped again down to the thirties and sometimes twenties.  So while increasing the VM/Swap file size helped, it seemed to be a short-term solution.  I landed and jumped in two other jets and same FPS drop when looking northeast.  So maybe a memory leak or something, where things are good for a while with the increase in swap file size, but then this issue consumed much of the remaining memory or swap file, hard to say.)

My system is sort of an older setup:

Gigabyte Z390 AORUS PRO WIFI MB, i7-9700K 3.6GHz, 64GB RAM, GTX 3070 ( 8GB VRAM)

 

Edited May 6 by 609_Relentov

[Dangerzone]

Aaah - the operating system is doing the old "Make it look like it's fixed the issue... until solution posted the solution on the forum" trick. Been there too many times to count myself before too.  

[jnr4817]

So, have we found a fix for this, lol.

[609_Relentov]

1 hour ago, jnr4817 said:

So, have we found a fix for this, lol.

It's a slippery slope, which is why I had so many edits after a lot of trial and error :).  So far, with my VM/swap file (temporarily, until this issue is fixed) equaling my RAM (i.e. 65,536), I have found my FPS has for the most part been staying pegged at 60 (as I use VSync) when operating in north CWG map and looking east/north-east - plus I had toned down my settings a bit as well.   I'm hoping Ugra puts out a fix for this so I can lower my VM back to a more reasonable size.

[jnr4817]

21 hours ago, 609_Relentov said:

It's a slippery slope, which is why I had so many edits after a lot of trial and error :).  So far, with my VM/swap file (temporarily, until this issue is fixed) equaling my RAM (i.e. 65,536), I have found my FPS has for the most part been staying pegged at 60 (as I use VSync) when operating in north CWG map and looking east/north-east - plus I had toned down my settings a bit as well.   I'm hoping Ugra puts out a fix for this so I can lower my VM back to a more reasonable size.

Still using the precaching file edit?

 

[609_Relentov]

3 hours ago, jnr4817 said:

Still using the precaching file edit?

 

Yes, I left it after changing the values as Spicy had shown, in the autoexec.cfg in Saved Games/Config:

options.graphics.Precaching =
{
    around_camera = 10000;
    around_objects = 5000;
    around_types = {"world", "point"};
    preload_types = {"map", "world", "mission"};
}
 

It didn't seem to improve anything, after which I tried the increase in VM/swap file which seemed to have made the biggest impact.  I may switch the precaching back to the default and see how it performs.

Edit:  After using the default values for around_camera and around_objects (50000, 10000, respectively) by renaming the autoexec.cfg file, I flew in the CWG map again - the FPS dropped a couple times looking north east, after the first time it stabilized back to 60, but after a while it came back.  Hard to say, as it's not always consistent, but I think I will use the updated (i.e. 10000 and 5000) values again, as it seemed smoother to me before in combination with the larger swap file.

Edited May 11 by 609_Relentov

[Drangoll]

I have the same issue , while flying east to west from Dedelow
(basically empty mission , only a few static helicopters. Single player)

RTX 3080 , 32 gb ram

Edited May 15 by Drangoll

[YSIAD_RIP]

I have not spent as much time as I wanted to with DCS since purchasing this map.

• The interesting thing I did notice with the Upper Northern part of the map, when facing the ocean, was that the frame time stutter and FPS performance drop was extremely noticeable for me only with the excellent and free OH-6A helicopter.
• The Kiowa and Gazelle performed much better and with zero stutter on the same location. 
• Something strange is going on, and I am more curious to know what the solution will eventually be because it has not really stopped me from enjoying the map in its current state. 

 

Edited May 15 by YSIAD_RIP

[sokol0210]

I stil have that issue after update. 
Anyone else here has it too? 

[609_Relentov]

It seems better to me after the update.  While I have seen the FPS drop into the 30's (from 60 max), so far it has only been temporary and gone back to 60 after a short while, like something was loading, when looking northeast from the top 1/4 of the map.  Before the update I had FPS drop down into the teens and 20's, and sometimes they would stick for a while and/or not go back up to 60 FPS but continue to drop when looking northeast.

 

Edit:  As has been the case since I first flew on the CWG map, the FPS issue has been inconsistent.  Unlike my previous experience post-update, today it seemed worse, as the FPS was dropping to the high teens and low 20's when looking north east from the north 1/4 of the map.  So, once again I can't say it's consistently better after the update.  I really hope Ugra and team can look into this issue.

Edited May 26 by 609_Relentov

[MorgothNL]

On 5/22/2025 at 7:20 PM, sokol0210 said:

I stil have that issue after update. 
Anyone else here has it too? 

Issue is still very much there for me. Map is kind of unplayable. As soon as I look anywhere towards that bugged area, my FPS just tanks.

Any update from ED / Ugra on this? Any cause found?

Edited May 27 by MorgothNL

[609_Relentov]

@MAESTR0

@BIGNEWY

Can you give any thoughts on this issue?  As it’s persisting even with the last update, is this something Ugra has acknowledged and is actively working to fix/improve?

Any comments would be appreciated, as the northern part of the map is unplayable with the FPS drop as noted in this thread.

Thanks

Edited Friday at 02:56 PM by 609_Relentov
Added BigNewy

[Jeepyb]

Still no fix ? I actually had great performance when the map just came out but now its pretty much unplayable because of this.