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

Ok thanks for confirming. Too bad, this is why I liked the original quick mission builder as you could define more parameters prior to generating the mission.

I’ve only used the QAG a few times, but noticed if you choose a SEAD mission type, if you click on the ADD button under Targets you can only add more Air Defense sites. So if you wanted some enemy aircraft guarding the SAM sites you can’t do it (unless you save the mission and edit in the ME). Edit: After submitting I saw this same request was made in another QAG feedback thread, so apologies for duplicating.

When starting the QAG, for me it’s always initially loading the CWG map (even if I opened a Caucasus mission in the ME prior), and thus it takes a long time to load. Then, you have the option to choose the map you want. The better option is to not load a map at all, but if you HAVE to load a map, use a smaller map like the Caucasus or Marianas map, so we can relatively quickly get to the UI. Thanks

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.

I've made updates to one kneeboard that has expanded it to two pages: F-4E - AGM-45-1.png F-4E - AGM-45-2.png In addition to some slight procedural updates, I've updated the table showing the SAM/RADAR/RF Guidance Unit types with expanded entries, and fixes. I only show the SAM/Radar/RF guidance type combinations that the AGM-45 was actively tracking, based on my testing. Please delete/replace the following kneeboard with the two replacement kneeboards above: F-4E - AGM-45.png

I noticed that now when I open the kneeboard in a module, in most (all?) cases there is automatically a pre-set pinned page, namely the first page after the default maps. This is cool, as well as our ability to pin any page we want once we spawn into a module. My request is to also automatically pin the first page of a user supplied kneeboard. For example, in the F4E module, HB has put in a bunch of pre-loaded kneeboards (e.g. for me, located in "D:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F-4E\Cockpit\KNEEBOARD\pages"), so when I open the kneeboard and click the pin to get just past the default maps, I then have to navigate through the dozens of HB kneeboards before I get to any user created kneeboards I've (or others have) created. It would be nice if when spawning in a module, DCS would automatically detect user added kneeboards and pin the first one (alphabetically by kneeboard file name I would suspect) for us (located in the Saved Games folder, e.g. "C:\Users\xxxxx\Saved Games\DCS.openbeta\Kneeboard\F-4E-45MC"). Thanks for your consideration. AKA_Relent

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.

Adding a reply to support this wish list item, to have the AI fighters fly more realistically (meaning tone down their BFM abilities a bit).

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.

Thanks SD - yeah I’ve got a couple scripts that I need to clean up/fix that nil value issue. Also for the additional tips.

I attempted to save a mission using the Cold War Germany map, and while in the past I've had issues where DCS would crash, this was the first time I got a blue screen which caused a reboot. Interestingly, the last thing noted in the log (attached) was "not enough memory" issues: 2025-05-08 16:05:36.263 INFO APP (Main): try to write track file 2025-05-08 16:05:36.280 ERROR EDCORE (Main): More out of memory in ed_malloc for 2852520 bytes. 2025-05-08 16:05:36.280 ERROR EDCORE (Main): More out of memory in SharedBuffer for 2852488 bytes. 2025-05-08 16:05:36.280 ERROR EDCORE (Main): Not enough memory to decompress: mission This seems odd as I've got 64GB of RAM, and due to playability issues (i.e. huge reduction of FPS) on CWG map, my paging/swap file is also 64GB (a large swap file seems to be needed for playability on this map, for now). dcs.log

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)

Hey SD - I sent you a message in the forum here.

I was back flying the A-10C II recently, and thought I'd add a few more kneeboards as I had forgotten some of the relatively simple procedures and needed reminders. I added the following kneeboards for using the 30mm and AIM-9 Sidewinder, and using countermeasures and ECM: A-10C II - 30MM GUN AIM-9.png A-10C II - USING COUNTERMEASURES AND ECM-1.png A-10C II - USING COUNTERMEASURES AND ECM-2.png