JohnRedcorn

Well, the solution is simple though. Just don't create missions with orbit AAR. The AI of both air and ground units in this game is dumb, so just don't give it task which are to complicated for it, problem solved.

The AI aircrafts have a predefined tasks which are spreaded between all waypoints. The predefined tasks are defined by the aircrafts group role (SEAD, CAS, e.t.c.). If you want your aircraft friendly group to do more or less the things that you want them to do, then click on the aircraft group and in the bottom you will see a waypoint properties. There will be a tasks which have a "-" sign. Delete these tasks and then set your own tasks and behaviour for the group. Set ground targets on desired waypoint and aircrafts will attack only the ground targets that you sat. They will no longer fly somewhere to attack some SAM that you didn't even ment them to attack. But in this case AI aircrafts will be a little dumb. They will attack ground targets by queue. On the start, first aircraft will perform ground strike until it get out of bombs, then the second one will start to attack and so on. As a result, they will spend a lot of fuel for nothing. So if you want them to attack the targets all at once. Create 4 groups of aircrafts, 1 aircraft in each group. Then make them follow after the first aircraft, so they will fly in formation. Then when they will get to the attack waypoint they will attack their targets all together. Just remember to set them in formation on the next waypoint.

Well, the core parking feature is an OS feature and I guess that other games don't have any problem with it because they are not divided to a so many threads like DCS does. I have posted an article from NVidia which describes that it is actually not so good to divide the main game process to a lot of threads. You can read it here: https://developer.nvidia.com/blog/limiting-cpu-threads-for-better-game-performance/ It is an interesting article, but unfortunatelly we can't do nothing here. Only developpers can limit the number of threads. Anyway, did you checked your UEFI setup? It might be that there is some power options which can be disabled, so the OS wouldn't be able to park the cores anymore? You can try to download a manual for your motherboard from its manufacturer site and check if there is some power options which can limit the OS core parking functionality.

You are welcome. Well, with DCS you never know which solution will give you the best result. But it is worth trying every solution possible.

Well, the guy here on the forum says that disabling "Power" service is better than to set your CPU to a 100% usage for minimum and maximum performance in power plan. The reason for this is that even if you set it to 100% usage, the "Power" service continue producing a lot of interupts, so your CPU need to handle these interupts. When the "Power" service is not working then there will be no interupts at all from this service, which is reduce CPU usage. But because this service is not working, winodws woesn't controls CPU usage at all, so it will work with 100% performance all the time and I guess that there will be no core parking at all. But I'm not sure about core parking. Just read this thread:

If I understood it well. When you stop the "Power" service, your CPU will never park cores and will work with 100% performance all the time. So you don't need to run an additional software and you reduce a lot of interupts made by "Power" service. So it might be a better solution than "CPU Unpark". I have an old CPU so my cores are never parked and I didn't tried this solution myself. But there is a guy who claims that this is the best solution ever. The game starts running very smooths.

It is because after the game loading for the first time, it cashes it's code and data in memory and the memory is not getting clean after yo close the game. All of the game data and code remains in memory as "cashed". You can check it through task manager. Open the "Resource monitor" and switch to a "Memory" tab. You will see that there is a memory usage bar. The blue line is marked as "Standby". This is the cashed data and code of DCS World which remains in memory even after you close the game. So when you run the game again, it checks if the desired data or function is loaded in memory. If it is loaded, then the game won't load it again from the drive, but use the loaded data / code from the memory. This way you can also cash the map. Just open a mission before flying it. Zoom out the map to see all the map. Then you can also zoom in until you start see cities and trees and move the map with the mouse to cash all the objects (You can just move over the mission area to cash it). Then exit the game to release the memory and turn it from "In Use" to "Stanby", launch the game again, open your mission but don't play with the map again, just start the mission right away. As a result you will have less stutterings on the mission start.

Hello Eagle Dynamics team. After a couple of last updates, a lot of people even the ones who have hi-end PCs started experience significant performance problems according to a lot of performance problems forum threads which where recently created. I personaly have runned a mission on Syria map which have a lot of moving ground units and which was working acceptable well for me in ST and MT when it was firstly introduced, but now it works much worst. I don't have a hi-end PC so I'm not expecting stable 60 FPS or 120 FPS. But the mission worked much better in ST and early intorduced MT than it works now in MT. So I have found the following article which explains that dividing a game to a to many threads is actually not a good thing to do. I have heard that DCS can run 32 threads. I don't know how this info is accurate. Anyway maybe the following article will help you to find a balance between the number of game threads and game performance. https://developer.nvidia.com/blog/limiting-cpu-threads-for-better-game-performance/

You are welcome. I just made my own tests and I have noticed that ED changed something to AI. At least it looks like this. I have a mission set on "Syria" map which I have created a long time ago when there wasn't MT yet. The mission have a lot of moving ground units columns which are also very long columns. So even when MT was introduced, this mission worked well for me both in MT and ST, but after a couple of last updates (especially after the last one), this mission is just working very bad. I even noticed that when one of the AI planes drop the bombs or when I drop the bombs. The microstutterings starting right away. Then they are stops but after the bombs impacts to the ground the microstutterings starts again for a couple of seconds. Then I have tested a mission with less ground units on the same map, and it runs much better. Then I have tested a mission without ground units at all and it runs smooth. So I think that the change in AI targets spotting algorithm which was mentioned by ED in one of the previous updates has impacted performance a lot. It is only my thoughts, but it looks like this. The algorithm has become much complex and it stucks CPU. I'm honestly don't know why ED has divided the main game process to so many threads. I have found an interesting article from NVidia where their devs explains why it is doesn't good to divide the main game process to a lot of threads. They actually explains that there has to be a balance and if you start to open to many threads you are signifficantly reducing the game performance. You can read it if you want, here is the link, it is NVidia site: https://developer.nvidia.com/blog/limiting-cpu-threads-for-better-game-performance/

There was also a solution to disable the "Power" service. The guy who mentioned it says that even if you set "High performance" power plan, the "Power" service continue to make a lot interupts, so disabeling it completely helps sometimes to make the game much smoothier. Than there is a guy who mentioned that after each mission load, you should open the task manager, go to DCS process affinity option, disable the "0 Core", back to the game, then switch to task manager again and enable "0 Core" and the game starts to be smooth. But you need to do it each time you load a new mission.

Well I have to say my word. It will be a little off-topic but I just want to say what I'm not happy about in this game. (I will back to topic at the end of my post, I promise ) The huge problem for me is an AI. It is bad in a way that it can't perform even a simple task. What is even more annoying, that ED always ruining AI even more. Just a little story. I have tried creating a free campaign for this game twice. The first one I have tried to create on Caucasus map. The second one, on Syria map. Both times I spent around month and half to make these 4 - 5 missions work as intended, fighting the AI stupidity. And then both times the update comes and ruined everything, because ED has changed something in AI and triggering system. And it was O.K. for me if they were fixing things, so I should able to get rid of all the crutches, but they have ruined the crutches and didn't fixed the native triggers. So the month and half of AI fighting were just thrown away. I have never tried again to create a campaign for this game. And it was actually a reason why I have stopped buying new modules for DCS. And this is actually a main thing, people complain in their comments under the "Iraq map pre-purchace" video on "youtube". And this is a signal to ED what they need to fix, because a lot of people on "youtube" telling that they will not prepurchase "Iraq" map because everyting else is just not working for them in this game. I know that ED is the only studio on the market that creating a modern military aircraft simulator. But if it will continue like this then there is a chance that there will be no companies that creates military aircraft simulators at all. People just not happy with the fact that the core game is not working as intended (The last update also caused a huge performance reduction for a lot of people with high-end PCs) and ED continue releasing new modules (including maps) for a game which doesn't work. And yes, we all know that those are different teams, but hte overall image just doesn't looks good from the customer's point of view. Now back on track. As for me, I will not prepurchase this map, because as I mentioned above, I have stop buying modules for this game, because of the bad AI. As for the maps. Well I don't see a huge diffrences between "Caucasus" and other maps. Even "Syria" map which looks better is just the same thing. The ground is indestructible. The explosion craters where updated to a 3D craters, but they are still a "ground patches". The trees are indestructible and with the addition of a wind blow effect, when the bomb is dropped into a forest, the trees begin to sway in different directions like rubber tumblers. The trees are non-flammable. You can drop any amount of bombs into a forest and there will never be a fire. Why I'm talking so much about the forests? Because there is a lot of forests on the "Kola" map. Which makes the only possible solution for creating ground strike missions on this map is setting "cutting forest zones", otherwise it will be impossible to destroy any ground unit at all. And the mission creators have to set all the units to hold their places, otherwise they might drive into a forested area and, well the rest you know. In the video presentation of this speciffic map I have noticed the same canion which was displayed from different angles and a city. The city looks good, but there was shown only a part of it. So nobody knows how the rest of the map looks like. Anyway, I have enough modules already, but I'm not happy with the core game at all (to the point that I even have no desire to learn the already puchased modules), so I'm flying the modules I have already learned, from time to time but mostly I prefer to play something else which have modern graphics and all features working as intended. I even play old games with old graphics but all features working. So the key for DCS to success in my opinion is to make all features working and stop throwing new products to a customer's faces for a game which is working like a broken car.

There is no problem to roll back. Just read the following thread and follow the instructions: You can roll back to any version that is listed in the second message of this thread in a table. You probably won't be able to play multiplayer because the servers are usually running on the latest version. But you can play single player to check the performance.

If you have a gaming mouse you can also try to reduce the polling rate below 500 Hz. Some people are complaining about stutterings from mouse movements when the polling rate is set 500+ Hz.

Just read my post here, it is No 13 from the top. It explains how to set an affinity mask: It is not disabling Hyperthreading but forces to run DCS on physical cores. So the hyperthreaded (virtual) cores should not be used. I cannot 100% assure you that it will help you. But it did the trick for me, so it worth trying.

It is easier to disable the hyperthreading. But then he should remeber to enable it each time he finished to play DCS. As for me I have set the affinity mask through the shortcut on my desktop (one time) and it is much easier just to run the game as usualy without disabling and enabling hyperthreading for each run. My PC can't handle all the graphical settings but when the "Multithreading" version was firstly introduced, I didn't had any microstutters at all. The microstutters has started after updating to 2.9.7.58923. I didn't touched any graphical settings, they stayed as they were always. But the microstutters has just tarted to appear in v2.9.7.58923. There is a lot of people here by the way who have PCs with very high specs and they have the same problems. Just open the forum on "DCS 2.9 -> Game Performance Bugs" and see how many people complaining about microstutters and performance reduction after the latest update. So it is not only the graphical options but there is definitely a problem in the game itself. The last two updates by the way, were rushed. The next update is a planned update. So I hope they will fix a lot of bugs.

The following is from Intel site: Performance-cores are: Physically larger, high-performance cores designed for raw speed while maintaining efficiency. Tuned for high turbo frequencies and high IPC (instructions per cycle). Ideal for crunching through the heavy single-threaded work demanded by many game engines. Capable of hyper-threading, which means running two software threads at once. Efficient-cores are: Physically smaller, with multiple E-cores fitting into the physical space of one P-core. Designed to maximize CPU efficiency, measured as performance-per-watt. Ideal for scalable, multi-threaded performance. They work in concert with P-cores to accelerate core-hungry tasks (like when rendering video, for example). Optimized to run background tasks efficiently. Smaller tasks can be offloaded to E-cores — for example, handling Discord or antivirus software — leaving P-cores free to drive gaming performance. Capable of running a single software thread. As you can see. The P cores and E cores are a physical cores. But Intel has implemented a technology which is called "Hyperthreading". This technology make each Performance core work as 2 cores. And this is what I mean by virtual cores. Each virtualy doubled P core is actually a core which doesn't exists and you should prevent DCS from running on these virtual, non-existent cores. I guess, there is no problem to run DCS on E cores alongside with P cores, but you should create an affinity mask which will exclude the Virtual cores. Now I don't really know how the cores are distributed in your speciffical CPU. It might be that for exmaple 8 cores, starting from core 0 are P cores. Then there might be 8 virtual cores and then all the E cores. It might be also that there is 8 P cores, then all E cores and then the virtual ones. So I guess it would be much easier to run the game on the P cores only. Because they are the first ones? You should try and check different affinity masks to find out what is working the best way for you. As for me, I have an older model of CPU which have "Hyperthreading" but don't have P cores and E cores. So it is a little bit easier for me to create the proper affinity mask.

I'm happy to help you, but changing to 2.7.x is a little bit radical I would say. As for me, I'm currently at 2.9.7.58923. It have microstutters for me as well, but I have applied the affinity mask to run the game on physical cores of my CPU only and it did the trick for me. The game is running much smoother in "Multithreading" mode in this version for me than it was in both "Multithreading" and "Single-threading" in 2.7.x. Pay attention that in one of the 2.7.x versions, the "INS" alignment for "Ka-50 Blackshark 3" was bugged. So I recommend you to install the 2.9.7.58923 version and then apply the affinity mask. And make sure you are running the "Multithreading" version of the game if you will update to 2.9.7.58923. The "Single-threading" version will be deleted soon anyway. Check my post here, it is No 13 from the top, to find out how to set the affinity mask. I think it is better than to downgrade to 2.7.x for "Single-threading" version. Anyway its up to you. As an alternative, you can just wait for a new update to be released and then try it. I hope they wil fix the microstutters in a new update.

As I already said in my previous post. The latest version of the game messed up an FPS for a lot of people. The guys who have RTX 3080 and had 140 FPS two updates ago, now have around 40 FPS. So try to downgrade two versions back. Pay attention that if you play multiplayer than you won't be able to play it on public servers. You can still play it only if you and your friends are running the same version and play on your own server. The single player is not a problem to play. Here is a guide on how to do it, read the whole post, the second post have a versions table:

A couple of solutions I have found myself: 1. If you have a gaming mouse which polling rate is set above 500 Hz, then reduce it to 125 Hz. This simple solution helped a lot of people as I have found out from forum posts. 2. Run your game on physical cores only. This solution helpped me personally. Here you can check how to do it. Just read my post, I have described it pretty well. 13th post from the top. You will notice it, its bigger than any other on this thread. 3. Disable the "Power" service. Someone on the forum mentioned that even if you set your power plan to a "High perfomance" the "Power" service can still cause stutterings in DCS. So disabling it completely before starting DCS might help (reboot required). Just don't forget to enable it again after finished playing, otherwise your laptop will finish battery charge very fast. 4. You should also check your BIOS/UEFI setup. Some setups provide an ability to choose how many cores of your CPU will be running permanently. This parameter is usually set to "Automatic". So the cores may power up and down. Set it to a maximum available number to make them work all the time without turning off. P.S. According to the people's posts, the latest update brang a new bug into a game. The AI planes are causing sutters. Some guy have tried to remove all the AI planes from his mission and the stutters are gone. In this case, the only thing I can suggest you to do is downgrade two versions back. I personally didn't updated my game because I'm reading about bugs before updating. So I'll wait for it to be fixed. If you play like me SP only then it might be a good solution for you.

You are welcome. Well, I'm not sure that this command will do the proper core distribution. It just limits the number of cores if I understood it well. It's not a magic wand of some sort. The proper core distribution should be codded by the devs. Otherwise OS will use the free core or the core with shortest processes queue and you don't really know which one will be used. Anyway, I'm sure there is other solution that will work for you. Maybe setting the the power plan to a "perfomance" and then settting CPU min and max power to 100% in advanced settings? You should also check the BIOS/UEFI setup. It might have a CPU core usage settings and it might be set to "Auto". You can change it to "4" so CPU will always power up all of the cores without putting them to sleep or parking. I hope you will find solution. Sorry that my solution didn't worked for you.

Well, my icon is still showing the DCS icon, not a cmd one. But if your CPU doesn't have the virtual cores "no hyper-threading" then there is no reason to set the affinity, because the game will run on 4 physical cores in any case. So if you still have stutterings then there might be some other solution for you.

Well, this is strange then. No I didn't changed anything. There is no DCS_Updater.exe in "bin-mt" so the shortcut is pointitng to "DCS.exe" as it should. Maybe you should try to create a new shortcut to "bin-mt\DCS.exe" and then try adding the command? I'm really don't have an idea why its not working for you? Its just an additional command for the OS. You should be able to run any program like this, not just DCS.

Do you keep a "space" between the affinity command and the execution command, and do you keep the execution command in quotes? You should also take only the "F" without the zeroes and "x". And the most inportant thing is. If you have copy/paste my command then change the "Your game install folder" to actually a game install folder whatever it could be. For example "C:\Games\" or whatever else where your game is actually installed. If you are using steam version then find the game in your steam install dir and use that dir path to replace the "Your game install folder". The thing that should happen is the cmd window should open and close almost immediatelly and then the game should run. And if you check the cores, you should see that the only 4 is used. I personally always running the game like this because otherwise I have stutterings and the command works for me. So it is real and it works. By the way I have found this solution on this (DCS) forum, but it was buried somewhere betwwen the posts if I remember it well. So this was the reason I did my own post.

I didn't encountered this problem, but I believe that author of the topic researched the problem deeper than me and I tend to trust him because I encountered similar problem with my AI wingman. I have a training mission for Su-25 (from Flaming cliffs 2024 package). In this mission I have a couple of areas with all kind of targets. The first area have a line of bradleys which are standing on the road near the sea. There is no obstacles around, the area is flat. But when I command my wingman to attack the ground targets it says that it can't. And it can't attack them beacuse it doesn't see the targets, as I discovered later. If I will dive on the targets and let my wingman dive with me to a pretty much low altitude and command my wingman to attack the targets after diving, it will start attacking the ground targets without a problem. Its like I need to put my wingman's face right into a targets to show where the targets exactly are. Before the changes to AI field of view everything worked much better. But of course there was another problem like the bradleys which were see me from a pretty much high altitutde and were shooting at me like snipers. Now their behaviour is more realistic. So there is definitely a problem with this new mechanic of AI's field of view and it needs some tuning and I guess its not that easy. It might be that each individual type of unit requires its own tuning, which requires a lot of time. But it definitely requires fixing.

Hi, don't know if it will help you, but it helpped me. I had the same stuttering problems in MT version as many user here have. So I found that the solution is to run DCS on physical cores of CPU only. I have an Intel CPU and it uses the "Hyperthreading" technology as all Intel CPUs do nowdays. I don't know how this technology works exactly but I guess it do some kind of a quick context switch for each core (or some cores) of CPU. So it is like if CPU have one physical core it will virtually work as two cores. So we should say that the CPU have 2 cores one physical and one virtual. For some reason DCS doesn't like the virtual cores. If you are not forcing somehow your OS to not use them when running DCS, than you will experience stutters in game. So, how to force you OS to run DCS on physical cores only? First of all, visit Intel's site to find your CPU model. Check how many physical cores it have in its specs. The second step is using this online calculator to create a CPU affinity mask for forcing your OS to run the game on physical cores only: -> https://bitsum.com/tools/cpu-affinity-calculator/ How to use the calculator? It is very easy. For example you have an old CPU which have 8 cores, but only 4 cores are physical. You need to select "CPU 0", "CPU 1", "CPU 2", "CPU 3" in claculator. You will see a 0x000000000000000F in CPU Affinity Bitmask (hex): field. If your CPU have 8 physical cores than you need to select until "CPU 7"(inclusive), and the affinity mask will be like this 0x00000000000000FF. The only thing you need from the affinity mask is the last hex value. For example, from 0x000000000000000F you need only F. From 0x00000000000000FF you need only FF. From 0x00000000000007FF you need only 7FF. In other words, you don't need all the leading zeros and the "x". After selecting all your physical CPU cores and finishing creating the affinity mask. Right click on the DCS folder on your desktop, click "Properties" and in the "Target" field, where you see a path to your game execution file. Enter the following before the execution path: C:\Windows\System32\cmd.exe /c start "DCS" /affinity [enter your affinity mask here, without the squared parentheses and without the leading zeroes and "x"] "Here continues your execution file path, do not change it". Example: C:\Windows\System32\cmd.exe /c start "DCS" /affinity 7FF "Your game install folder\DCS World\bin-mt\DCS.exe" The above example will force your OS to run DCS on 11 cores. You can just change the affinity mask to run it on any quantity of physical cores you need. Make sure that the execution path is poiniting to "bin-mt\DCS.exe" otherwise you will run a ST version of the game. I hope it will help you and others. P.S. I don't know if this solution will help the AMD users. As far as I know AMD CPUs have all physical cores (at least they were) so AMD CPUs should not have this problem.