Leaderboard

Hi fighters! Today we will look at optimization. The team is working on improvements to the map, but the more detail and uniqueness we add, the more effort it takes to optimize. Hard work has been done on all areas of the map: models have been optimized, textures have been reassembled, vector data rendering on clipmaps has been updated - all this has had a positive effect! We conducted tests on two systems: AMD Ryzen 7 3700x / RTX 2080Ti and i9-10850K / RTX 4080 When flying over a city, FPS increased by an incredible 20%, and while on a system with a 2080ti the average FPS was at 85, now it confidently remains around 110. When flying over a forest, FPS increased from 5% to 20% compared to the previous build. When testing the 2080ti system, the fps was always above 105. One does not simply release an update with optimization. We have added 4 airfields: Amman Civil Airport Herzliya Airport (NOTAM: RWY LENGTH 1500M) King Abdullah II Air Base Prince Hussein Air Base This will increase your flight geography and diversify your missions. Explore new airfields and get ready to take off Prince Hassan Airbase King Abdullah II Airbase

LD-3000 C-RAM (China) version 1.1.0 released! Changelog Version 1.1.0 Fixed LD-3000 destroyed models size issue Fixed LD-3000 mobile size issue Fixed LD-3000 stationary size issue

M1A2 MBT (USA) version 1.1.0 released! Changelog Version 1.1.0 Fixed log errors introduced in DCS 2.9 Fixed size issue

M10 LT (USA) version 1.1.0 released! Changelog Version 1.1.0 Added laser targeting Fixed cannon elevation restrictions while rotating Fixed cannon muzzle flash position Fixed log errors introduced in DCS 2.9

Excellent! Begs the question though: When you are going to expand further into Iraq and Kuwait?

Love it ! Thanks CH!

PCL-181 SPG (China) version 1.1.0 released! Changelog Version 1.1.0 Changed 155mm unguided HE maximum range to 40 km Changed max engagement azimuth from 30/30 to 45/45 degrees

DCS: AJS 37 Viggen Red Flag Campaign 16-2 Patch Notes * Mission Dates now adjusted to reflect the time span of the real 16-2 Red Flag Exercise. Weather has also been adjusted to be accurate for the season. * All AJS 37 Viggen Aircraft have been given the correct squadron livery and correct serial numbers for aircraft stationed at F 7 Såtenäs. * All F-16C Aircraft have been updated to module status and given correct liveries and serial numbers for 77th Fighter Squadron “Gamblers” who attended Red Flag 16-2 * All F/A-18C Aircraft have been updated to module status and given correct liveries and numbers for VFA-314 “Black Knights” who attended Red Flag Alaska 16-2 * Radio Bug Fixed in all missions * AI Flights Orders and loadouts adjusted to make them more efficient in their respective roles across multiple missions. Their performance should now be far more consistent. * Minor changes to mission 7, 9 and 10 to reduce frustration over issues the player had no control over. I am still waiting for word if this is something Heatblur wants to put into the next patch on their end or if I will just publish it to ED User Files. However, anybody who want to test the updates early or came here looking for a bug fix, poke me in DM and I will send you the files.

When I play ping-pong ("table tennis" as we call it here) with my godson, there is a strangely creative quirk to observe. Whenever he loses, he comes up with an explanation: the wind, a distracting insect, a glint that blinded him, the table was tilted, his paddle's padding, ... - no matter what, the entire world seemed to have conspired against him to deprive him of victory, and it was never his fault. Sometimes, he even accused me of cheating (I was unfairly levering my longer arms, was trying to distract him with talking to him, or by humming, or by not answering his questions). Although I love my godson, I find that particular streak in him unattractive. Maybe you take winning at this game much too seriously. My experience is that I gain other people's respect not by how often I win, but how enjoyable the entire experience was. Now, granted, I usually don't play PvP, I usually play with others, seldom against them - unless it's a team effort. We all play to enjoy ourselves. That way we don't have to imagine what may have conspired to make us lose. Seeing a conspiracy behind every thing that goes wrong, a potential exploit behind every surprise and being a victim every time you lose is the way to flat earth society and frustration. Don't use your imagination to make yourself a victim. You are playing DCS, and that should always be a win.

Excellent, thanks CH !

Ask why that is. A perception of widespread cheating and the belief that you need to lower your graphic settings in order to not be at a disadvantage doesn’t help. I would love to see any facts backing up that assertion. Until then please excuse me for dismissing above as some self-serving tidbit manufactured out of thin air. Again, apologies. I do not have your name in my book of go-to people for questions when I'm developing VR titles (and I do earn some money that way), so please point me to the source of your information, so I can educate myself. Please explain to me the 'focal length effect' I see IRL, and how it pertains to reflections on the cockpit that can't be duplicated in VR. Then please explain why that makes it ok to apply crappy lo-res bitmaps at high opacity instead. It is exacerbated with shadows off or set to 1 (one) (i.e. not off). Again, please educate me how that in any way justifies not providing a better method, like for example allowing a frigging multiplicator to lessen the impact without unduly giving a performance boost (that was one of the shader fixes that I wrote myself for the glass material shader, so I do know what is involved, how simple it is to fix and what the performance impact is).

Thank you for everything you do as always. We salute you.

Maestro Syria Map update.

Су-25 гораздо корректнее сравнивать с А-10. Ранние были примерно + - равны по возможностям, но амеры пошли дальше в сторону модернизации, 25-й же остановился в своем развитии в силу ряда причин. Мне А-7 тоже интересен. З.Ы. Кстати, от твоих политических домыслов уже тошнит, ей-богу. Заканчивай.

The free instant action missions that are provided for some (most) aircraft and maps should be considered a bonus. DCS is a sandbox game and you get the most out of it if you use the mission editor. However, there are tons of free missions (sometimes even campaigns) created from users in the download section of the homepage. A lot of them are easily en par or better than the free missions provided with the modules.

Yes, we are almost finished with it.

I didn't really have the A-7 on my radar. But yesterday I saw news about the A-7 through HIP by Andrei Celeste. It already looked pretty good and I'm hooked. Now add some decent sound and a VR pilot body and I'm in. Until then, I wish you every success.

DCS Borders between Egypt & Israel is not accurate as Taba city is Egyptian territory

MiG-29MU2 Fighter (Ukraine) version 1.4.0 released! Changelog Version 1.4.0 Fixed JDAM-ER missing its target

Der WSO hat kein MFD wie man es aus der Hornet etc kennt, bekommen. Wie MAD-MM schon sagt, der Bildschirm der mit dem DSCG Upgrade kam, bot die Möglichkeit zwischen Videosignalen umzuschalten. U.A. deswegen wurde die F-4 somit Maverick und Pod fähig. Die Maschine mit dem DMAS Upgrade wird insofern interessant, weil bei der nur noch der dicke Pave Tack Pod verwendet werden kann und der Pave Spike nichtmehr. Der Pave Tack auch nur an der Center Station unterm Jet und mit entsprechend schlechter Aero weil das Teil ein Monstrum ist. Dafür eben dann auch Nachtkampffähig. Hat die DMAS das ARN-101 Navigationssystem wo der Nav Computer dann auch mehr als 2 Wegpunkte speichern kann. Die TISEO am linken Flügel was gleich quasi funktioniert wie die Kamera bei der F-14. Außerdem können mit den DMAS Upgrade dann auch die Datenlink-Pods verwendet werden um Walleyes als MITM Waffe steuern zu können und mit dem DMAS Upgrade gab es wohl auch eine Konsole im WSO Pit was die Verbindung zur GBU-8/15 hielt um diese Steuern zu können wenn ich es jetzt nicht komplett falsch im Kopf habe. Die 80iger waren da insofern interessant, da damals noch nicht final entschieden war, dass man zu den Laser Targeting Pods übergeht und hier bei der USAF viel mit optisch gelenkten Bomben (GBU-8/15, Walleye, ...) experimentiert wurde.

Since that whole shader folder was unlocked just imagine the possibilities… your aircraft probably looked like a giant orange dot to someone else. That’s why it was added to the IC. You asserted that so few people play multiplayer because of rampant cheating. I wanted to know what facts you have to base that assertion on. Your "answer" does not provide any facts and tries to divert instead. That's fine. I merely had hoped that you had matured more in the past few years.

Of course it can: the simple way is that you don't render the scratches — done. The pointlessly complex way is to tie it to sight line and apply DoF smearing on anything that is not in focus. DCS already supports this. So nothing that actually supports your assertion, then? Just some personal paranoia that is nonsensically generalised to the entire population of DCS players. No, because it is there with or without shadows. Note the word “exacerbated” because it tells you everything you need to know, and also demonstrates why your simple and misaimed suggestion does not justify not creating a better solution to the actual problem.

Can't say I'm desperately impressed with the UK airfields, Biggin and Manston. The runway layouts are about right but otherwise there's too much "this will look cool" regards the placement and types of buildings and not enough research. Also hangar types are again wrong. Manston in 1944: The layout as shown in the development screenshot looks good, however there is one major error: Please refer to this site: https://www.manstonhistory.org.uk/manston-layout-history/ Biggin Hill in 1946: Notes: 1. No large hangars - they were all destroyed during the Battle of Britain, i.e in 1940. They weren't replaced till ~1947/48. The only covered aircraft servicing provision available were the many blister hangars. For a map that supposedly represents the summer of 1944, they should not be there. 2. No large buildings to the East side of the airfield. 3. The many blast pen positions. 4. Notice that most of the buildings on the South Camp are single floor buildings and manly consists of workshops and sheds. For example this image: ...which was taken from this location here: Compare this to: You can see the large building clusters that aren't in evidence on the period map and the too large industrial buildings. This is a problem systematic across the UK airfields already on the map. It stems from 2 issues. 1. Little actual effort has been made to research and model ACTUAL RAF airfield buildings, 2. Someone is using some generic industrial assets and a heap of "this will look cool" instead of (a) asking those of us in the community who would happily assist and provide as much info as possible to get things right (or at least close), and (b) actually listening to them when it is provided. This latter part I have a particular bone of contention with, as plenty of information has been provided by the community in the past but seemingly paid lip service to in the interim, with very few requests for our assistance from the developers that, in hindsight, seem more like a tick box exercise in 'community engagement' than any meaningful attempt to actually garner information to correct issues on the map. For example, information was provided by the community to correct issues at Kenley, Tangmere, Ford, Farnborough, West Malling, Gravesend (and others) before the map was even released in the spring, but little apparent sign of any of that having been taken on board or actioned has been in evidence. It feels like there is an opportunity to faithfully recreate historical fact but it is being dismissed for the sake of convenience and superficiality.

you will need to be patient, we are working on a fix for lag in the servers for the November patch. thanks

So an update to the progress of the Nimrod, It has progressed decently although I have hit a brick wall in my abilities. The aircraft is in and full scale this time, animations are complete, extra details such as engine exhaust and such has been added and weapons have been added. Weapons: 2x AIM-9M AGM-84 Harpoon BL755 BOZ Pod Torpedo MK-82 (Stand in for Iron Bombs) Here is the limit of my knowledge, I do not currently know how to UV unwrap and texture so currently that area of the Nimrod still needs work however for an AI, it is near complete. Here are a few images of the latest progress

"Easiest" way to make channel map relevant would be to expand it into low countries and parts of Western Germany. Give us market garden and Bodenplatte map for late 44 and early 45. This is actually were the Dora and Kurfyrst was seen. It would also be useful for 41-43 raids on Nederlands and Germany with A20, Spitfire, B17s and P47s.

Let's be generous and say that 10% of the DCS population play online. Do you seriously suggest that 90%of the people should have a s*!##y experience playing every day so that you can sleep easier not having to obsess about the things other people might do to cheat you out of your oh-so-deserved win? If so, I think that says a lot more about you than anything else. A solution, perhaps. There are many, and I'm hopeful that the kind people at ED will look at this some time. The visuals right now (in VR) look cartoonishly 1990s, distract, and break immersion. It's a long-standing issue that was fixed by the community and now has re-surfaced - IMHO quite needlessly.

I agree, this sounds more logical. I'll soon report these issues.

This is actually a recent correction of an old bug. TACAN channels will now show distance to DME stations on their paired frequency. It just so happens that channel 107X is paired with the VOR frequency 116.00MHz, which just so happens to also be the VOR/DME frequency at Damascus.

@Spino The Admiral has a donation link on his new download site. Anyone who likes his work should consider a donation. Any size is appreciated. One dollar to twenty. He uses all for buying new models. Your hard earned money, Hard at work, Making what you love! A win, win!

Just adding a closure, did get it on Steam, took only 1 hour flying the CE to get hooked on the module. Everything on the module is great, sounds and flightmodel, it does need a lot more rudder input to fly, would not recommend for someone without rudder pedals. but other than that, flawless quality, Above C-101 level of details, just amazing work. The fact that we algo get 3 more variants for the module is just more icing on the cake. Thanks Aerges for this outstanding module.

Сравнивать разные ЛА можно и нужно. Желательно это делать фактологически, что есть у одного, что есть у другого, чтобы плюсы и минусы были аргументированными.

Ты пишешь в каком-то низком стиле, мягко говоря, приплетая Су-25. Про A-7 здесь знают не меньше тебя. По нему литература даже на русском языке существует. Просто он не так интересен. Пиши по модулю: создай тему и размещай новости разработчиков, а не вот это вот всё.

Где Вы увидели "официальное заявление ED" о чём-либо? Вас просят успокоиться и не более того. А то дискуссия явно начинает сворачивать в ту сторону, где будет ай-яй-яй. Считайте это официальным заявлением модератора.

Next product from Total Controls has been revealed: The Total Controls Eject Handle! It will fit every module with an ejection seat in DCS and BMS. It is plug and play and will give three pulses in one pull. Base will be slightly larger on production unit. It will be 40x130 mm. Designed to fit an aluminum T-profile 80x40 mm. Base height 85 mm. Total height about 300 mm. Handle is adjustable. Preorders will go live soon.

I started DCS in VR earlier in the year and was able to snag a G2 new on Amazon for under $400. I was generally pretty pleased with the G2's clarity but soon found myself wanting more. G2 Likes: Great clarity Inside-out tracking, at least for me, was flawless 99% of the time Light and comfortable IMO Value for the money ... IMO still the best value for sims and a good gateway drug G2 Disliked: The FOV was not great, like looking through a tube The colors, even with tinkering via OXRTK post-processing, always seemed a little washed out WMR just leaves a lot to be desired. I frequently had issues where the framerate on the headset after starting DCS would be like .5 to 1 FPS. I could restart DCS (sometimes several times) and then it would be fine and work all day. I built a new system from scratch a few months ago, and it did the same on the new system as well. Not sure if it's the headset of WMR. DCS would often crash on start as well. It was comfortable, but a little more adjustability would be nice I ran the G2 for a few months and was already on the prowl for "better" once I knew I was hooked. I teetered back and forth between the Pimax Crystal and the Aero. The Areo's $2000+ investment was a real turn-off. And, I was apprehensive about the base station requirements, drilling holes in walls to mount, etc. It all just seemed like an expensive PITA. However, when the price of the Aero was basically cut in half, the equation changed. The Pimax seemed like it had some things going for it, but it still just looks HUGE and the battery requirement, IMO is just frankly stupid and ultimately landed the Crystal in the "no thanks column". I ordered the Aero and two base stations and in about 3 weeks I had everything. Varjo charges your card ~5 days before shipment, and they charged me a few days after I ordered. It shipped and arrived exactly when they said it would. The base stations shipped separately and arrived about a week later. This could have been made clearer during the ordering process but at the end of the not a big deal. I uninstalled the WMR OXR apps first but left OXRTK installed. For the base stations, I saw someone suggest using adjustable shower curtain rods and cheap Amazon clamp-on camera mounts. IMO this is the perfect solution - the rods clamp between the floor and ceiling, I can wrap the power wire around the black rods, and I can move it around wherever I want. Highly recommend this solution if you don't want to wall-mount or want the flexibility to re-arrange in the future. I also bought a cheap 4-pack of smart plugs and use them to power the two base stations and the headset. I have an Alexa routine "VR On" and "VR Off" to control their power. The setup of the base stations was pretty straightforward. You just plug them in and Steam VR just seems to pick them up and they just work. From the Varjo website, you'll create a simple account and verify it. You can then download the Varjo Base software. I installed the Varjo Base software. The hookup instructions for the Aero was basically a picture where everything hooks up - basically exactly the same as the G2 aside from the fact that it's a USB A connector instead of C. If you know anything about setting up a PC, it's easy. The setup process was very simple, and farms you out to Steam VR for base station calibration with the headset. In about 10 minutes I was up and running. I started DCS and voila ... it worked! I immediately wanted to jump in with DFR and proceeded to install the software (see the great "First time setup" thread on this forum for the Aero, great stuff on there!). I started DCS and CRASH! Tried several times, rebooted, and crashed every time. C:\Windows\System32\KERNELBASE.dll # E06D7363 (Unknown exception code) at 00007ffc80e0cf19 00:00000000 SymInit: Symbol-SearchPath: 'D:\DCSWorld\bin-mt;', symOptions: 532, UserName: 'mwrig' OS-Version: 10.0.19045 () 0x100-0x1 0x000000000002cf19 (KERNELBASE): RaiseException + 0x69 0x0000000000006720 (VCRUNTIME140): _CxxThrowException + 0x90 0x000000000003b522 (MSVCP140): std::_Xlength_error + 0x22 0x0000000000004880 (Effects2): Effects::Rain::operator= + 0x8F0 0x00000000000a226c (Effects2): Effects::releaseParticleSetCB + 0x670CC 0x0000000000036a58 (Effects2): Effects::OParticleSystem::isStatic + 0x12E8 0x000000000003632b (Effects2): Effects::OParticleSystem::isStatic + 0xBBB 0x0000000000035e1f (Effects2): Effects::OParticleSystem::isStatic + 0x6AF 0x0000000000033cd1 (Effects2): Effects::OParticleSystem::operator= + 0x581 0x000000000003452f (edCore): ed::this_thread::yield + 0x54F 0x000000000002460a (edCore): ed::make_render_thread_tasks + 0x1A 0x000000000013c736 (Visualizer): smCamera_Implement::getClipRegion + 0x193B6 0x0000000000128736 (Visualizer): smCamera_Implement::getClipRegion + 0x53B6 0x000000000013fbd2 (Visualizer): smSceneManager::DestroySceneManager + 0x13D2 0x00000000000335b1 (edCore): ed::thread::_get_current_thread_id + 0x71 0x0000000000021bb2 (ucrtbase): _configthreadlocale + 0x92 0x0000000000017344 (KERNEL32): BaseThreadInitThunk + 0x14 I backed out all mods, but still crashed. I uninstalled the Varjo-Foveated package and everything worked. I then reset all my graphics settings back to default, including settings in the Nvidia control panel and profile inspector. I re-installed the DFR software and everything worked great. I re-applied my graphics settings incrementally, and everything still works great. In fact - it's not crashed on start (or at all) for two days. With WMR/G2 this happened at least once on startup with nearly every session. So far, flawless. So, first what I like about the Aero: The image clarity is superior to the G2. And, even without DFR the edge-to-edge clarity it MUCH better. The G2's sweet spot was tiny. You can look around the cockpit with your eyes and read everything. It's pretty amazing, frankly. The colors are much better IMO The outside-in tracking works great, but to be fair I had no issues with the G2's inside-out tracking. The adjustability - the knobs to adjust the headset in three directions are fantastic. I also like the temple adjustment as it really helps position the headset on the face. This is something I struggled with a bit on the G2. And, the G2 adjustability mechanisms are much cheaper, quality-wise. The FOV seems better suited for me. It just seems less like I am looking through a tube. The auto IPD adjustment is nice, but I'm the only user so I would likely set it and forget it anyway. Dynamic Foveated Rendering is AWESOME with the eye-tracking. The FPS boost combined with the superior lenses compared to the G2 just makes this an entirely different experience. So far, ZERO crashes with the Open Beta MT DCS client once I had it fully set up. Performance - running DLSS Quality and pretty high settings across the board, performance is much better than the G2 (see below). Ease of setup - IMO it is pretty simple to setup, and if you're already into PCs, VR and flight sims you'll be fine. What could be better: I miss the G2's integrated audio. I am using the Conquest VR clamp-on solution, and it sounds just as nice, but it's an additional expense and is much bulkier. You can always use more FOV The outside-in tracking works great, but IMO inside-out is the future and is much more convenient. This setup just has more moving parts, but so far everything has worked well and as designed. The performance of this headset, even before enabling DFR is superior to the G2 even with the same DCS settings and the highest quality setting (39 PPD) in Varjo Base. Using DLSS "Quality" I run 90 FPS most of the time. I have the motion smoothing enabled in Varjo Base and synchronization OFF. I can see in DCS when smoothing kicks in as the FPS drops from 90 to 45. Visually, I can notice the transition slightly IF I am looking for it. In combat, I never notice it. Microstutters no longer occur like they did with the G2. I have not noticed ANY. With DFR enabled, I stay at 90 even more. Am I happy? You bet. I wouldn't have been as happy at $1900, but at $990 this headset is 100% worth it for me. It's a worthy upgrade from my G2, which I will keep on hand as a backup should I need one in the future. Overall, when compared to what I know and have read for other units, if you're looking for a sim-focused headset ... 8.5 / 10

Yes, we'll have an assortment of liveries from different nations and F4U versions.

The things we have to do for immersion

Have you tried reading the OP?

Interesting, does this mean the map is being expanded slightly to the South given the new Airports listed, i mean Amman is right at the bottom, would seem odd to have a line of no terrain so close - Dead sea to be included?

@silverdevil I think the whole idea behind that switch is to act as the radar elevation controller for the F/A-18 since the functionality is modelled differently on the F-16 vs F/A-18. As someone already stated, TM had also implemented such a switch on the F/A-18 grip artificially. Remember, that the Warthog throttle does not provide such a switch….

Personally, the whole issue of Liveries gives me the willies. And for me, it's not the storage space, bandwidth or unexpected life advice one seemingly gets when engaging discussing them. To me the very concept of liveries is strange. The point being: I can't see the livery that my plane has - it's painted on the outside. So the point of a livery apparently is that people wear it to pose to others -- it is IMHO entirely narcissistic. And yet, I see that not only is it important to some people, and some 60-80 percent of all uploads to ED's user files are liveries, so there certainly appears to be demand; I'm not denying that. There's also incredible artwork being done, yes. Other games monetize this affliction, and - outside of modules - thankfully DCS is free of (micro-)transactions. To me, the livery I fly in is irrelevant - out here and in-game. I don't care how my plane looks like to others, I care that I enjoy myself flying that damn thing. It's not the livery, it's the plane. If people enjoy liveries, we should let them. If some of us are inconvenienced by their size and proliferation, I say that we should also try and be considerate. And a good compromise seems to me to make them optional (which, I believe, many are). So a compromise of less mandatory and more optional content could indeed be a good way to go.

A complete changelog of all versions and there versionnumbers can be found here (OpenBeta first in the list, Stable more down). https://www.digitalcombatsimulator.com/en/news/changelog/ PS: SkateZilla's app is a must imo, makes DCS life very easy, even so if the new version still contains quite a few bugs.

Hi @Stackup. Many thanks for your detailed report. I rephrased it below. Please make sure that I got it right and didn't forget anything. Issue 1 - The green light should be on top and the amber light below it. Issue 2 - The lights sequencing is wrong. This is how it should be: Hose is in "ready" state and fuel is not flowing (from ready state to "you're taking fuel") : amber light steady on - green light off Aircraft is connected and fuel is flowing (from "you're taking fuel" to "transfer complete") : amber light off - green light steady on Drogue being pushed too far forward causing fuel flow to stop : amber light flashing - green light off Hydraulic malfunction (in case ED implement it someday) : red light steady on - amber light steady on Hose retracted: all lights are off

Good stuff, thanks for sharing!

Happy to try to help out with specific testing if required Fully appreciate that it will not be as easy to implement as it is to type, if this can be looked at though I reckon that it will potentially solve one of the longest running issues in DCS VR - it's been in existence for at least 3 years to the best of my knowledge. Can anyone replicate this issue with WMR in 2.9? I suspect that the fix instigated by mbucchia that locked the compositor VRAM will also negate the problems experienced here; if that's the case then it's a very quick and easy elimination. edit: @Special K a few people have tested this in WMR without suffering from the performance tanking but still running at 75-90% of VRAM budget. This just reinforces my theory about the overallocation of VRAM as the WMR openxr runtime has had a portion of the VRAM locked exclusively for the VR compositor.

Guys, as I commented below that video already, what you are doing here is black magic. You are misusing the Windows scheduler to "magically solve" an issue that DCS has, namely not freeing used memory properly. Whenever you unfocus an application (ALT+TAB), you tell Windows that it is not the #1 priority application anymore. Now the Windows memory management will mark all your nice memory pages that you have used a second ago as candidates for swapping. As DCS is the main user of your RAM and VRAM at that time and Windows is eager to free some of that up, it is very happy about your move. It's doing what you ask it to do - freeing up memory, in this case either for the application that you swapped to (youtube, notepad++, your file explorer, whatnot, something that was used before you started DCS) or your DWM. It now loads that into memory. Now you switch back to DCS. What happens? Well, it depends. If you have lots of RAM, in first place nothing. It will mark the memory pages from your DWM, Notepad, whatnot as disposable. Whenever you now need RAM for DCS, you'll get it much easier. Until the point where you need that stuff again, that you just swapped out earlier. Doing it with a lot of RAM might not even get you to the point that you see what you are doing. It's the same "black magic" trick that someone put out about a year ago where he said, giving the DCS process less memory solves issues. You just give DCS less memory to play with. On the other hand, if you **don't** have enough RAM, you're doing something really really bad to your system. The amount of swapping with DCS is already ridiculously high and you force your system to do even more of it. This will result in lots of swapping, even more wearing of your disks, etc. Don't get me wrong, I appreciate the ideas you guys develop to get rid of long standing issues and I fully second that we need a better memory management INSIDE of DCS. But this is not the right way of doing it. There is no magic key that frees up memory inside of DCS. This magic key only asks Windows to move it out of sight for a while.

Well not a single person working on the Normandy map, which is a 3rd party map, worked on Voice Chat. So that wouldn't have helped at all.