Search the Community

Hi, It seems the magic 1 performance needs to be re-evaluated, as the missile's aspect limitations seems much too restrictive compared to it's real life performance. Seemingly it's a single value that has been put in a bit pessimistically. See @IvanK and @DSplayer

I recently switched from Meta Link to Virtual Desktop but haven't been entirely happy with the performance until now. My PC is no slouch of a machine: Intel i9-13900k @ 5GHz Asus Nvidia 4090 64GB RAM @ XMP setting NVMe drive for Windows NVMe drive for DCS Windows 11 Pro Quest Pro headset Meta Link and DCS Configuration: Meta Link x1.0 @ 72Hz. DCS PD 1.5 Most, if not all, settings in DCS are maxed out (the configuration can be seen in the attached screenshots). DLSS enabled. Performance Test: I judged performance by flying the instant action, Persian Gulf, ready on-ramp mission with an F-16. It's not a scientific test, but it was a rough guide to see if a patch or driver update had broken something. The goal of the test is to remain out of ASW. Take off, climb to 1200ft. Turn right to the coast, maintaining speed at 450-500kts. When the Burj Khalifa building is almost at my 3 o'clock, pull hard right towards it. Then, I took another hard right again as I passed the building. A well-performing system would make both turns and maintain 72 fps, staying out of ASW. On the switch to VD, my settings were: Godlike resoluton @ 72Hz. DCS settings are the same except for PD. Any PD over 1.0 would cause a drop to ASW with the above test flight on the hard turns. The image quality was identical/similar, but I was unhappy with the performance. I realised that with the Meta Link, I had been using Oculus Tool Tray and had set the FOV to 90%, as some of us found that this gave a performance boost without affecting image quality. Effectively, it reduced the image size that was drawn but just about within the FOV, which was limited by the frame of the lenses. Any more than 90%, and you could start to see the edge of the image as a black rectangle. When I turned off the 90% FOV in Meta Link, the performance was similar to Virtual Desktop. So, to get the performance in VD that I had with Meta Link, I started making some adjustments using the OpenXR Toolkit. OpenXR Toolkit has a FOV setting in the System tab. I set that to 90% but still had lower performance. Then, I looked at the render resolution in the dcs.log and found that it hadn't changed despite a reduced FOV. To change this, I adjusted the display resolution, which was also in the System tab of OpenXR Toolkit. I lowered it to match the resolution created with Meta Link at a FOV of 90% and PD of 1.5. For me, that was 2904x3041. With that change, the performance was back, and I am now fully converted to Virtual Desktop. Yes, Virtual Desktop is more expensive because it requires a dedicated gaming router. You can get cheap ones and expensive ones. Either appears to work. Be sure to pick one from the list of tested routers. Yes, the bit rate is lower with VD. However, that's not an issue if you use one of the newer, more efficient encoders. I am using the HEVC 10-bit encoder, and I can't see a difference compared to H.264 @ 500 Mbps. Yes, Meta Link can run up to 960Mbps (not without distorting the audio via the link). Some say they notice a difference, but I don't. For me, Virtual Desktop offers the peace of mind that Meta won't break DCS by changing their implementation of OpenXR on the Meta Link. It also allows you to see and interact with the Windows desktop, unlike Meta Link, where you have to peek under the headset to launch DCS. All in all, it is a better experience. To top it off, I am now wireless, which makes a huge difference. No more cable tethered to the PC! To maintain the charge of the headset, I use a power bank battery attached to a belt or in my pocket. Yes, there is a cable. I barely notice it. In summary, if you want to get the boost you had with 90% FOV using Meta Link: Find your DCS render resolution for your setup with Meta Link from the dcs.log file. If you are running DLSS, look for "DLSS successfully initialised". Mine is now: "DLSS successfully initialised, 1936x2032 -> 2904x3044". Set the FOV to 90% in OpenXR Toolkit. Adjust the "Display resolution (per eye)" in OpenXR ToolKit to match your old render resolution. Enjoy the performance boost. If you want a sharper image, you must sacrifice high CPU options such as shadows for higher resolution/increased PD.

So I'm hopefully getting ready to build a new pc. I'm not trying to break the bank or build a super computer. I just want something that will let me play DCS fairly smoothly, for a little while without having to low ball all of the graphics settings. Could someone with pc hardware knowledge take a look at the components I picked out for my build? And, give input on whether or not, I would get pretty reasonable performance in, DCS? Or on what you would suggest changing? I budgeted myself on between $3-$4k, so a 5090 is not in my wheelhouse. This build puts me around $3,400 before I start price comparing and deal shopping. Thanks

I started this topic to track and discuss challenges with getting the best performance out of the system. I usually test each setting a couple of times. 27-1-2025 Nvidia 571.96 DLSS 4.0 Installed the new drivers. 25-1-2025 Adjusted GPU Overclock Increased CPU PBO Scalar and reduced some of the GPU overclock to further increase fps and frametimes. Time will tell if it also stays stable on the MP-servers. 18-1-2025 Clean W10 Complete reinstall of W10 returned another 5fps and better frametimes. Over the years the system got bloated with all sorts of traces from old hardware that I upgraded (2x GPU and CPU) and software that I tried and not fully removed. The system is snappy and clean again! I considered W11, but there are too many bad stories out there, no clear advantage for AMD and GUI modifications with taskbar etc W10 is easier. The only thing I still notice is that it seems that when I hit the FPS limit some sort of trouble in FPS and frametimes appears. When I stay a bit below 90, like 88fps, it is more stable. 27-12-2024 Current Overclock settings 64GB ----- EXPO: ON (timings default as stated on the DIMMS) 9800X3D ----- Turbo Game Mode: ON PBO: +200 Curve Optimizer: -20, FCLK Infinity Fabric: 2200 UCLK DIV1 Mode: UCLK=MEMCLK, SCALAR 10X 4090 ----- Core Voltage: +100 Core Clock: +120Mhz Memory Clock: +900Mhz, Fan: Power Limit 133%, Temp Limit 84. This GPU overclock is stable and gives me 4-5 extra FPS, even when i am CPU bound. My setup Windows 10 - latest version - Windows 11 will not happen until I will get serious latency advantages. Motherboard: ROG STRIX X870E-E Gaming WIFI Systemboard VR Headset: Varjo Aero SSD for DCS and Windows, separated DCS Settings Most are set to the max. SSS, Secondary Shadows, SSAO, SSLR are disabled; they do not bring much visually. Visibility Range Extreme. I have Visible Range set to High. Increasing this further is not bringing much visual improvement and really takes away performance. MSAA Mask Size 0.42 is my sweetspot. Testing Setup and approach My Windows has been heavily tweaked and optimized and I am currently still running the same Windows I started with 5 years ago. I upgraded my systemboard, CPU and GPU a couple of times but did not reinstall Windows. I think at certain moments in the past I even went too far with tweaking and should have dialed back and better register what I was doing. So a clean install will be somewhere in the near future because I am certain I have left quite some performance on the table. For the basic quick test of setting adjustments or hardware/software updates I start a the default A-10C mission Runway Startup on the Marianas Map. I use Marianas because this mission is quite demanding and quite stable almost from the start with AI not doing much. I let it run a couple of times for 20 seconds and track the performance with CapFrameX to calculate the average FPS, 1% and 0.2% lows of the runs. Many other missions give me 90FPS, so adjusting settings with such missions will not give me noticeable visible differences. If I want to visually see the performance I open up the the FPS overlay inside DCS. I sometimes also open up the new XRFrameTools application to visualize my frametimes. Once a setting looks pretty okay I log into our Wing's Multiplayer server, startup OBS recording and give it a spin to see how it goes. I usually get 90FPS flat in this setup, while running OBS recording. Testing log From now on I will start adding my complete testing logs to this main posting. Where relevant I will add charts to visualize the difference between certain options. Certain tests were eye-openers. It was/is a dreadful process going through all the settings and quite a few settings were insignificant in my case. Frame Times, average FPS, 1% and 0.2% Lows My main goal is to find the ones that will bring more stability (reduction of intrusive stutters) and performance (increase of FPS/frametimes). Sometimes it is like searching for a needle in a haystack. Seeing the settings that made a difference might bring quick wins to others as well. Overall the average FPS is not improving that much by all the tweaking, it is easy though to screw up your system and reduce FPS. But once the FPS are pretty decent it is hard to get substantial improvements. My biggest wins are with the 1% and 0.2% lows, reducing these give a much better overall experience than to have 1-2 more average FPS. The overall FPS can be high, but when you have a few microstutters here and there it is very annoying and for me breaks the immersion in VR. Caution Please be careful, not all what works for me might work for you. Do everything at your own risk. I had some crashes, especially with the overclocking, so always make backups and restore points. I also don't have my overclock software start automatically anymore when tweaking, because that also caused an issue once causing me to keep rebooting into a crashing configuration. null null null

Hi all, I've been having a blast flying this module but the magic 1 performance seems very off. Looking at tacview files it seems the missile only pulls around 8Gs, which is about the same as a GAR8. Public information available says the missile should be able to do in the neighborhood of 35Gs, which seems believable since the Magic II is known as a very very maneuverable missile, and the two share the same body and fins, the later missile simply having a different seeker and 10% more powerfull motor. Would an aerges dev care to comment on this ? Is the low maneuverability of the missile intended on your end or is it an oversight ?

I did some performance tests on each option. With everything on low, as shown in the screenshot. My machine hits a constant 150 FPS in the mission available with Apache on the Iraq map. Of course, inside the cockpit, which is my objective. When testing an option, I only modify it and the rest remains as in the screenshot. Example: When I set the water to high, the DCS hits 140 FPS and the rest of the options are the same as in the screenshot (Low or off). I activated Shadows from top to bottom because the options in yellow depend on the shadows to work, the same for Motion Blur, which is in Blue. Terrain Objects Shadows was tested with all shadow options activated at maximum. The options that are not described in the spreadsheet were not tested because they do not affect performance. I made it to help me see which settings consume the most resources. I hope this helps in some way. Thanks! DCS 2.9.14.8394 FPS Options Teste.ods Teste.miz

Hey there, today I tried the new Somnium VR-1 in DCS using their OpenXR runtime. i got extreme bad performance and heavy spiking frametimes. Also the Ingrame FPS overlay was totally off to the DCS FPS limiter or the VR-1 build in FPS counter. in steamVR everything is just fine. maybe some OpenXR experts can have a look at the log file. dcslogfile.log

Hi , Based on the hotfix of 2.9.8.1214, I found my FPS has been dropped into around 20 in the airfield and around 70 FPS in air. With @BIGNEWY's suggestion, I attached my dcs and dxdiag logs and hope that there is a suggestion for me. Prior to 2.9.8.1107, my DCS was running okay and no complain... Thanks. dcs.log DxDiag.txt

Hey ED team, Any chance we could get occlusion culling in DCS? I feel like the game’s rendering way too much stuff that’s hidden (like terrain behind mountains or stuff under the cockpit). Pretty sure this could be fixed with client-side occlusion culling since the server doesn’t care what we can see, just sends all the data. If the client handled culling and skipped rendering stuff we can’t see, it’d probably help a ton with FPS, especially in big missions or multiplayer. Not sure how hard it’d be to add, but seems like it’d be a huge win for performance. Would this be possible with the current engine?

TL;DR: when a mission spawns or clones a unit, memory is allocated. This memory is never deallocated, even on group/unit destroy, explode or removeJunk. Thus over time any mission that creates units will crash either from memory starvation or from hitting the RegMapStorage cap of 4094 groups. This investigation started after we noticed the excellent Pretense mission was dying after a few hours on our hosted server. By profiling the memory usage of the DCS_Server process using Process Lasso logging, we noticed that the VM (private bytes memory) continued to increase regardless of unit destruction, client join/leave or any other factor. The control was performed with a basic ME mission with a single client helo and no AI. VM usage was flat. The logical next step was then to write a script that spawned new units at a constant rate, and destroyed them on a cadence. If VM was deallocated, we would expect to see a sawtooth pattern. If it wasn't, we would expect to see a relatively straight incline up. The mission starts with 2 minutes of no spawning to establish a baseline with all scripts loaded. It is virtually flat. Once spawning starts (1 group of 5 vehicles every 3 seconds), VM rises steadily and does not reduce with destroy() being called on all ground objects every 60 seconds. When the spawn rate was increased to 1 group of 10 units every second, as expected the rate of VM accrual increased and VM was never deallocated. With a mission (not server) restart, no (effective) deallocation was performed as the VM restarts higher than when the mission was restarted. The next step was to also removeJunk around the spawn Zone to clean up as much as is permitted in the scripting environment. The same spawn parameters were used, with an additional step of calling removeJunk on a sphere 2x the size of the spawn zone every 5 minutes. In this test, VM continued the trend of accruing with no reduction due to destroy() or removeJunk(). It continued to accrue VM until the server crashed with the following error: 2024-04-11 03:15:28.743 WARNING EDOBJECTS (Main): RegMapStorage start cycle to find empty space in <viColumn> 2024-04-11 03:15:28.743 ERROR EDOBJECTS (Main): RegMapStorage has no more IDs (4094 max) in <viColumn> 2024-04-11 03:15:28.743 ERROR EDOBJECTS (Main): Failed assert `false` at Projects\edObjects\Source\Registry\RegMapStorage.cpp:124 This effectively caps the life of any mission that creates units on the fly based on the server RAM and the RegMapStorage cap of 4094. At 1 group per second being created, we'd expect to hit this cap at ~4094 seconds, or about 1.1 hours. This is basically exactly what we saw, despite all units in those groups being both destroyed and junk removed. A working theory is that this behaviour was introduced with the Apache FCR in order to allow destroyed vehicles to still be seen by the FCR. That said, others have said anecdotally that this predates the Apache. The effect is that dynamic missions require a regular server (not mission) restart to prevent this VM saturation, on a cadence that depends on the rate at which new units are spawned by the mission, and the total server RAM. Request that ED advise or investigate a solution that allows mission editors to purge the VM allocation of "dead but still there objects" in areas that are no longer relevant to the mission to prolong the life of the mission/server. While this may have other effects e.g. rendering them invisible to FCR, the alternative (a server crash or restart) is surely not better. Log data and charts: https://docs.google.com/spreadsheets/d/1p0tKoeipHJOaChhKnzNKjLD30maU3xKCvJH5o4quBY0/edit?usp=sharing (edit: if anyone wants to help me replace the MOOSE functions with stock to eliminate that potential source of error, please do!) edit2 another data point using trigger.action.explosion rather than destroy(). Same issue. RnR_Memtest_Syria.miz update: tested a different miz with no MOOSE (thanks cfrag), which creates 7 groups per second and destroys the group rather than the individual vehicles. Same VM accrual, and right on cue at ~590 sec (4094 / 7) it starts spamming RegMapStorage full.

When i try to load into a module it often takes 10min plus, sometimes it just wont load in at all and i have to close dcs. i also seem to have a problem with stutters when approaching other aircraft that has a high LOD. FXO, metashader2 & temp have been deleted VRAM: 8GB null dcs.log

I left DCS a few months ago when I started school again. Now that I have more time on my hands, every time I join a server, it is completely unplayable for at least 30 minutes (I wish I was exaggerating) because of extreme lag. This has never happened before, and I can only assume it's because the developers messed something up. I am infuriated by this as I will load for 30 minutes and then spontaneously crash the game. FIX THIS ED. This is unacceptable after the amount of money I have sunk into your game. Is anyone else having this issue?

Hey Guys, there is already a thread to this topic - but it is in the VR-Section and I wanted to report about my experiences in Pancake, so I figured to open a new topic. In short for those who are unaware of it: With the latest GeForce-Driver update, Nvidia upped it's sharpening feature to an universal upscaling algorithm similar to AMD FSR. It is pretty easy to use. Just activate the option in the 3D-Settings (you may also check the box for the overlay, with gives you an indicator when the feature is running), go to resolution and look for the scaled resolutions (85%, 77% and so on). Remember the odd resolutions, that comes with your desired upscaling tier (I went with 77%), but LET THE RESOLUTION SIT ON YOUR NATIVE ONE (Important!). For me the native Resolution (4K) is 3840 by 2160. The NIS 77% Resolution is 2956 by 1662. Now start DCS, go to the settings and change the resolution to the odd one from above. The option should appear in the drop down menu. Done. When you selected the overlay in the nvidia settings, you should see a green NIS in the upper left corner of the screen, when it's running. The results for me were the following: (GPU is RTX3080) Baseline (native 4K with msaa 2x): 19-11-2021, 18:24:08 DCS.exe benchmark completed, 10911 frames rendered in 140.047 s Average framerate : 77.9 FPS Minimum framerate : 69.3 FPS Maximum framerate : 87.2 FPS 1% low framerate : 68.9 FPS 0.1% low framerate : 67.2 FPS 4K with NIS (77%) and msaa 2x: 19-11-2021, 18:05:01 DCS.exe benchmark completed, 13512 frames rendered in 139.797 s Average framerate : 96.6 FPS +24% Minimum framerate : 86.0 FPS Maximum framerate : 107.7 FPS 1% low framerate : 85.7 FPS 0.1% low framerate : 84.3 FPS 4K with NIS (77%) and msaa 4x: 19-11-2021, 18:12:32 DCS.exe benchmark completed, 11569 frames rendered in 139.890 s Average framerate : 82.7 FPS +6% Minimum framerate : 73.0 FPS Maximum framerate : 92.2 FPS 1% low framerate : 72.8 FPS 0.1% low framerate : 70.9 FPS There are of course penalties in visual fidelity, but those are pretty small, given a 25% FPS-Increase. With msaa 4x and the sharpening factor tuned, your pretty close to the original quality. So if you struggle with FPS OR need some headroom to activate other options, NIS is a pretty solid option imho. Have Fun! EDIT: For those who use a TV instead of a Monitor (like me), it can be a bit tricky. There could be additonal hurdles to take. If you run into problems, let me know. I may be able to help. EDIT2: Added the detailed FPS-Numbers (note that I changed the settings over the original test, therefore the numbers are a little lower, but the percentages are the same.

Hello everyone, After a couple of months trying every possible settings you can imagine to get a good graphics and performance at 60 fps i finally reach it. OBS: I tested it for caucasus and PG maps, and it should work fine for NTTR and WWII maps although(I don't have these maps). For Syria and marianas forget it. DCS OB Version 2.7.9.18080 My Specs: Core i5 9400F GTX 1060 6gb 32gb RAM Windows 10 PRO NOTE: You'll need of the reshade to use just one filter very important to enhance the graphic quality. EDIT: I forgot to mention, you will need to install this mod for improve your perfomance too. ( https://www.digitalcombatsimulator.com/en/files/3317762/ ) @Luke Marqs Make exactly these settings as shown bellow. 1 - Set to ON game mode on the windows 2 - Set to ON Hadware-accelerated GPU scheduling at "Graphics Settings" on the windows. 3 - Open the NVIDIA control panel and choose Global settings tab, then set the shader cache size for 5gb or more. 4 - Change to "Program settings" tab and find to the DCS installation path on your PC (DCS World OpenBeta\bin\DCS.exe). Then set exactly as shown in the prints screen bellow for all options. NOTE: If you are having tearings, consider set vertical sync to FAST. 5 - At DCS settings choice these options NOTE: Textures: It depends what jet you are using, the f16C uses a lot Vram in HIGH option, you can test between medium and high Shadows - For more performance set it to medium, i prefer High. SSLR - To enhance the graphics ilumination set ON, better perfomance OFF. Try to test it. Full Screen as desired Terrain Shadow: very importan in FLAT 6 - Make America great again download of the reshade version 4.9.1 HERE . Then install it on DCS and chose a unique filter as shown bellow. It's very important to enhance the quality to the combination with the native nvidia FXAA, for decrease the AA blur and increase the sharpness. (Do not use the luma sharpen in reshade in this guide!!!!!) NOTE: Do not mark the box "Perfomance mode". If you need help for reshade installation or configuration, please watch some video on youtube. 7 - Close DCS and open again. That's all. I hope you enjoy it. Let me know if i helped you. Sorry for my english and thanks.

I recently updated to Nvidia 511.23, RTX 3070, latest DCS version Since some of the shader mods are really outdated, have artifacts etc I wanted to see what kind of native performance I'd get with stock shaders and no scaling. After uninstalling everything, repairing files and deleting the /metashaders and /fxo folders, the game recompiled shaders on first load of a map. Yet when the map started performance was still bad since some shaders still needed to be compiled. When I started the map for the second time however, I got the same FPS as I did with the shader mods and scaling, while having an overall better image quality, even though both tests used the same Nvidia driver. This was quite suprising. Maybe shaders have been improved with the latest DCS version or the Nvidia driver is more effiecient with those shaders. Setting textures to medium was the biggest performance improvement which seems to fix the leaky VRAM issue. Also restarting DCS after 2 missions, otherwise it gets slower and slower the more you hit "Fly Again" MSAA set to 2X and Nvidia control panel "Enhance AA" on and "multi frame sample" on

BLUF: Thrilled to be back...been jealous reading the forums and watching evolutions of DCS over the past few years. Would appreciate your help, so skip to the Questions section to bypass my melodramatic summary… I love DCS…I could not be happier with the trajectory, and it’s thrilling that study sims are making a comeback. I attribute this largely to IL-2 (including RoF) and DCS....things certainly seemed dead even in the early 2010s. So happy I no longer have to dwell on my first study sim loves: Microprose F-15 SE III, Janes F15, Longbow. However, as with many of you, it’s been a love-hate relationship that has ebbed and flowed over the years…here’s my quick story (please correct if memory provides inaccuracies): My DCS Story: 2009 – started with OG Black Shark CPU: AMD Phenom II 965BE GPU: Single HD5970 Top-of-the-line system; ran well, maybe 45fps, generally had a good time at 720p during real missions 2010 – picked up A-10C and never went back to Black Shark CPU: AMD Phenom II 965BE GPU: Single HD5970 Perf degrading, usually kept over 30fps at 720p...I started to get concerned. Generally enthralled but not much campaign/community content…interest came and went. Sadly, this would be the last year I could play DCS well on my 2 year old system (was top-of-line). Fun note: I have a good friend who’s an AF Hog driver (AETC) and back in 2010 he sat with my HOTAS Warthog, flew the sim, and could not believe it…just now in 2021 he sent me a link to this article: https://www.thedrive.com/the-war-zone/40620/a-10-warthog-pilots-are-using-the-digital-combat-simulator-video-game-to-train-in-vr 2011 – DCS World launched…perf got worse, still only flew the Hawg CPU: AMD Phenom II 965BE, but OC’d it more…didn’t help much (see BLAB) GPU: 2x HD5970s…added another card, didn’t help much (see BLAB) Struggled with maintaining 30fps at 720p BLAB: DCSW does not utilize multiple CPU cores well, nor does it utilize Crossfired GPUs. Super! At least I could play all the other games…so I often did for the next 4 years. :( 2015 – DCS 1.5 launched; DCS 2.0alpha launched CPU: AMD Phenom II 965BE GPU: New GTX 970 helped me take a swipe at 1080p…but just barely Struggled to stay above 20fps at 1080p during heavy action EDGE turned out to be a great long-term bet by ED…yet it did not solve my now very aged CPU/GPU combinations or fix the single-core single-GPU emphasis (as some suspected it may). 2017 to 2021 – sent overseas for 3+ years CPU/GPU: Packed away in my HHG, no sim’ing, no fun… At least once a week….for 3+ years…. I read about DCS’s progress and watched the YouTube/Instagram videos proliferate…could not BELIEVE the announcements around F-16, AH-64D, F-18, F-14…WOW! Mind blown…but all I could do was track things and wait to return back CONUS to give it another go. 2021 – DCS 2.7, I gave up and went gangbuster…didn’t even try to run on my old system CPU: i7-10700K OC’d to 4.85 GPU: RTX 3080 NOTE: I did try using my GTX 970 with the new CPU…and still only managed 30-45fps at 1080p. HAHA! Just proves you need both CPU and GPU to be top-of-the-line to really get any mileage out of DCS. For the first time in 10 years, I can play DCS smoothly again…and for the first time ever I’m at 60+fps on Ultra doing 1440p. IT IS INCREDIBLE….and it only cost me about $2,400! My Beefs with DCS (I love all the same stuff you love, btw…that list is too long): Performance = no question here…it costs a fortune to run DCS well and consistently over time. And I’m praying that my current top-of-the-line system keeps me at playable framerates longer than my last top-of-the-line system (2 years). Reliably merging the Aircraft with the World = missions/campaigns still seem super-buggy and constantly requiring high-LoE updates to maintain functionality as DCS constantly upgrades. It sucks to just be doing the same out-of-box missions from 2010 for A-10C. ED: you guys built these AMAZING high-fidelity aircraft…and this incredible digital world with beautiful clouds, terrain, and units on the ground…but are failing at unifying those 2 aspects together in a reliable and consistent way via community/ED-sponsored campaigns that do not fall apart every few months. [head-on-desk] My Questions to the community: Is ED seriously not supporting Red Flag for NTTR and A-10C II on 2.7? Building NTTR seemed like a questionable gamble for ED (not sure it paid off considering the new theaters, little content for NTTR I see now)…but having worked there before, I LOVED IT. And I adored the Red Flag Campaign…so is ED also falling victim to their own AI-brutality in mission design breaking with upgrades…is it too much of a pain for even ED to update? Should I ask for a refund here? Why does A-10C original even exist? I was quite surprised to see that OG A10 still is a separate module…how confusing and unnecessary. Why? It’s been over a year. All the content should be A-10C II by now… What SP campaigns should I play for A-10C II? Seems like just Enemy Within 3.0 - really? I want Red Flag…but see above. I played Enemy Within back in the day…happy to see there’s a 3.0 supporting A10-C II here. I see Piercing Fury is user-supported now…but it’s failing me on Mission 2 (I saw the fix threads…but don’t have time to screw with this stuff in the waning hours after the kids go to sleep…I just want to fly and blow sh*t up, fixes not working for me). Given the above experience with A10-C II - what do you think of investing in Hornet? What’s the single player campaign story there? I really want to dive into the Hornet once it goes on sale. I’m thinking to buy: Hornet SuperCarrier Persian Gulf Raven One But that’s a lot of money just to potentially be disappointed that I cannot play through campaigns after upgrades, etc. Other recommendations? I bought F-14 from HB…even though I won’t have time to study it. Just bought because I read they did a great job and want to support 3rd party on awesome modules like this. I’m definitely going all-in on AH-64D (same story, support the cause) but again worried about SP Campaign content… Thanks everyone and cheers

Hello! I got back to Supercarrier with Tomcat and Hornet after a time. I made a more or less empty training mission (just airplane and the carrier). Just before I catch a wire - lets say 10ft above the deck the whole sim freezes for a few seconds... this is highly annoying and destroys every landing. I have zero stutters, lags or other performance problems in every other thinkable situation in DCS. I have zero lag when landing on an airbase in an crowded city, but out on the sea with just the airplane and the carrier it lags at the worst moment possible. This is no performance problem, this has to do with the Supercarrier module. What can I do about this? Thank you.

I recently put together a server build for running multiple DCS clients. Unfortunately, it can't handle a heavy map. The mission on the server will proceed just fine until a client connects. Then all AI planes slowly loose their airspeed and it drops to 0. The airspeed will then skyrocket back up and down, with the planes hovering in place. I should note that lighter missions usually run flawlessly. Also, logs don't show a thing. Process Lasso did not make any performance improvements; to trick DCS into thinking all the cores from both processor are 1. Dual Xeon E-52678 v3 Processors (12 cores each - 24 with HT) 2.5Ghz 128GB DDR3 EEC Memory Nvidia Quadro RTX 4000 OS Disk is a dual 1TB SSD on Raid 0 DCS is installed on a separate 1TB SSD Windows 10

According to the F-15C manual (F-100-PW-200 engine - I am assuming that this is the one DCS version has) engines have a hard limit of 800 knots CAS and for altitude of 11600' maximum mach number is around M1.43 ~ M1.44. However, from the TacView screenshot, from one of the multiplayer servers, one can see an F-15C doing M1.7 (1244KTS) at 11600 feet. This guy's engines had no issues as he went latter on to over M2.0 at a higher altitude, I just didn't include the rest of the engagement.

Personally, I think that FSR will be an incredibly useful addition to DCS, especially for people with lower end computers. Disclaimer: I'm not a developer so this information may not be accurate, please take it with a grain of salt. What is FSR? As I understand it, FSR, or FidelityFX Super Resolution, is AMD's alternative to Nvidia's DLSS. Both make the game look like it's running at a higher resolution than it really is, albeit with different methods. For example, the game can render at 720p, but FSR will increase the resolution and fill in the blanks to produce a 1080p output. It's a way of improving frame rates while trying to have a minimal impact on graphics quality. Everyone can benefit from it, especially those with lower end computers. So it's AMD's technology? What about Nvidia users? Unlike Nvidia's DLSS, which only works on high-end Nvidia cards, FSR will work on a much wider range of devices, including Nvidia ones. It will work on the Radeon RX 400 and up, Ryzen 2000-series APU's, as well as Nvidia's GTX 10, 16, and RTX 20, and 30 series cards. Also unlike DLSS, FSR is open source and not proprietary. How difficult would it be to implement? For other games, it has taken from as low as two hours to as long as a few days. Of course, DCS doesn't use a common game engine like Unity or Unreal, so it would likely take longer, but from what other developers have been saying it seems relatively straightforward to implement. Conclusion I'm sure I, as well as many other DCS users would greatly benefit from FSR being added to DCS, as it would be an excellent way of improving performance for everyone, while taking (apparently) only a small amount of effort to implement. Thanks. For more information, check out AMD's page on FSR.

Hi guys, So basically, I need help. I'm going completely mad with my VR performances so far and I'm questionning what I've been doing wrong or if my rig is faulty. I hope somebody here will be my savior. Let's start with my setup then I'll explain point by point what I've tried and noticed. Setup Motherboard ASRock X299 Steel Legend Proc Intel® Core i9-10900X RAM GSkill 32GB DDR4/3600MHz GPU Zotac GeForce RTX 3070 Storage 1TB Samsung 980 PRO M.2 PCIe NVMe Cooling Corsair Hydro Series H100i Extreme Performance Liquid Coolin VR Headset HP Reverb G2 Flight Gear Thrustmaster Warthog HOTAS Stick & Throttle Trustmaster TPR Pendular Rudder UserBenchmark done today: https://www.userbenchmark.com/UserRun/45006662 Nvidia details Driver 471.41 See screenshots for settings Windows Settings HAGS - Off Game Mode - Off Fullscreen Optimization - Off DCS.exe vrcompositor.exe vrserver.exe all in High priority, added through Regedit Graphics performance preference - DCS.exe set to High Performance HPET - Disabled in Device Manager System page file - 32Gb Performance Options - Adjust best performance for Programs WMR Settings All by Default SteamVR Settings Using OpenXR at runtime. OpenXR Settings As I understand it, OXR settings don't apply to DCS even though SteamVR uses it at runtime for the G2 DCS Settings VR Settings by default (Pixel Density at 1, Force IPD Distance unticked, no bloom) Hotplug disabled. Environment No Chrome, no Spotify, no nothing but fpsVR. No DCS Mods but the VR Shaders I also have OpenVR FSR: https://www.userbenchmark.com/UserRun/45006662 Mission Environment I have a small multiplayer mission I scripted, nothing funky. Starts in Vaziani. I do all my performance tests and changes in the cold and dark F/A18. Attached is the .miz Mi-24P - Saving the 'murican convoy.miz Experience so far Okay so I guess it gives a proper idea of what I have in terms of setup and settings. I barely hold 30fps, cold & dark on the ground, with that whole configuration which is pretty disappointing for me considering the visual compromises and my setup that i would qualify as decent (it's a month old, all new pristine parts). I have followed several guides to improve performances. Guide specifically for the G2, guides specifically for the 3070, guides specifically for the G2 AND the 3070. When i see some posts on these forums showing 45 to 90fps in average with "weaker" setups, I'm just wondering what the heck I've done to Saint VR to be stuck at 30fps in a cold Hornet. Just to be clear, I am not a FPS chaser. I aim at 45 to 50 without multiplyer and without streaming/recording so that i can have a steady 30 to 35 when both in MP and streaming/recording. I have tried to put all the settings down to the bare minimum and got different results (which i can't really explain either). -90 fps (fpsVR) in the cold & dark hornet when i start the mission for the first time after booting the game up from SteamVR (meaning starting SteamVR first and then inside the headset to start DCS) -45 fps with the EXACT same settings and the EXACT same configuration after moving up some sliders and settings, applying them, starting the mission (crying because 20fps), stopping the mission, going back to settings, going all the way back down for everything then starting the mission again. -40 to 45 fps when launching the game not from Steam but from the shortcut on my desktop (I have the standalone version that i added as a non-Steam game on Steam), no matter if it's the first execution of the mission or not. -Randomly less then 20fps and huge stutters after starting the mission several times because i'm trying to tweak the settings and got back to the lowest possible Performance results As I mentionned, i barely hold 30fps with that configuration but here's a more in depth summary. GPU Frametime is 15 to 18ms in average depending on where i look in Vaziani GPU is at 58°C GPU is used at 35% in average SteamVR SS is shown at 50% GPU Mem is shown at 7.5 out of 8 Retro-projection ratio is shown at around 60% in average CPU Frametime is at 30ms in average CPU is at 65°C CPU is used at 65% in average CPUs are at 85% 20Gb out of 32Gb of RAM 2 dropped frames after 5min of time Overall smoothness is ok, the view doesn't "grip" when looking quickly around me. Obviously as soon as the aircraft is live and i have, let's say, the FLIR and a MAV on each DDI, I get stutters and the fps drops at 24/25fps in average. Conclusion What do you guys think? Is there something really obvious that i missed? I hope one of you's gonna be my angel because i'm literally clueless. Thanks for reading, -Hina

So while I was flying my F-16C on the Syria map I noticed a massive fps increase when the Slats and the wing tip got shot/hit off by gun/Missiles, my fps went from 10-20 to 40-120. So after I noticed this increase I did some testing and tried to remove non necessary variables like what other players are doing on a MP server. So I setup a testing area with the F16C controlled by player and some SA-9 (this is the same unit that caused the original fps increase). And after many attempts I got 3 tracks where you can see a massive fps increase when one full wing gets blown off and the 4th track file is an almost exact replica of what happened originally. F16 FPS increase Test 1.trk F16 FPS increase Test 2.trk F16 FPS increase Test 3.trk F16 FPS increase Test 4 best replica.trk

OK, looks stunningly beautiful but... From the FAQ: RECOMMENDED SYSTEM REQUIREMENTS (HIGH graphics preset settings): OS 64-bit Windows 8/10; DirectX11; CPU: Core i5+ at 4+ GHz or AMD FX / Ryzen; RAM: 16 GB (32 GB for heavy missions); Free hard disk space: 120 GB on Solid State Drive (SSD); Discrete video card NVIDIA GeForce GTX 1080 / AMD Radeon RX VEGA 64 or better; Joystick; requires internet activation. I am on a Windows 10, I7-10700K (5.1 GHz), 64 GB RAM (3000 MHz), RTX 3080. Also from the FAQ: Despite being an island map, you can expect similar performance to the Syria map So, Syria map gives me constant 60 FPS (consistent with my screen capability) and empty Andersen AB I get 40, Guam @ 3000 feet MSL I get 30-40, at 700 feet I get 30-40. Ocean alone at 1000 feet MSL shows as 80 fps, whereas Mediterranean sea on Syria map gives 120 fps at the same alt. I guess I need to wait for optimizations?

Hi all, apologies if this has already been discussed. I happened across a YouTube video by @Growling Sidewinder yesterday who was demonstrating and discussing the F16's rate turn performance when compared to the F18 and F14. The general conclusion of the video is that the F16 is underperforming in a 2 circle rate fight when compared to the F14 and F18 (or obviously the later 2 aircraft are overperforming) I can see how the F18 and F14 could/should outperform the Viper in terms of radius turns but not in a rate turn. Has anyone carried out a controlled test using something like Tacview? GS's video is here:

I am getting 23 fps in the menu screen and 11-15 fps in flight. All maps, all aircraft. Have not done anything else than come back from a vacation and started up DCS and get unplayable framerates. Using a Vive with a Nvidia GTX 1080. 6700K Skylake. 32G RAM. Normally have 90 fps(max for Vive) in the menu and around 45 fps in game. Other games like Star Wars Squadrons and Dirt Rally2.0 do not behave the same. Hopefully ruling out hardware or Nvidia drivers and the like. Like I said, no change in config or anything.