FierceLV

I need to be fair, I did not try to turn of CPU Cores 16, 17, 18, 19. I figure they are some kind of special economical CPU cores. Can some one explain in more detail why exactly it is proposed to disable those cores? I don't want to alter the default performance of my personal computer, because it might detrimentally influence the overall performance. There are 20 cores for a reason.

Hi, thank you for your intention to help me with my problem. You have suggested many really useful methods to address my problem. Let us continue with the issue: 1. I play DCS World really simple, I use only the keyboard, no mouse, I have a decent performance-wise personal computer. 2. I do not use any kind of system tweaks that provide inconstant personal computer performance (fluctuating FPS, Overlays, overclocking and things like that). I aim at the clean and constant performance of the personal computer (things like FPS cap to keep the FPS at one level all the time). I do not use any third-party software or mods, I prefer the "as clean as it gets" approach, "the way it was intended to work". 3. With the help of the DCS World Community, some time ago I have unlocked my CPU cores with the help of the ParkControl software. The ParkControl software improved the overall performance of my personal computer. However the occasional Lag remained, and the Lag remained mostly in the F-16C and the F-15E. 4. Currently I am not updating the DCS World because the "Campaign Save" function is still too fresh. 5. Regarding the Windows 11: I don't want to upgrade the system, because I have achieved a good performance of the Windows 10. 6. Regarding the PageFIle: I returned it to the default system setting, because there was no performance gain with the DCS World, the system continued to allocate the same amount of RAM for the DCS World. Personally, judging by my long time observations I can surely (95 %) conclude that the problem of the Lag lies within the aircraft itself, or in the Game itself. I have managed to pinpoint the exact origin of the occasional Lag during flying the F-16C and the F-15E. And the origin of the Lag is: THE MOMENT WHEN THE CPU THREADS ARE SWITCHED. This can be easily seen on the video attached to this post. The Lag itself is the moment when the rendering threads are changed: CPU Bound (Rendering Thread) <- LAG -> CPU Bound (FPS Limit). But not always the Lag occurs during the moment when the rendering threads are changed: CPU Bound (Rendering Thread) < --- > CPU Bound (FPS Limit). To prove my point I have lowered every visual setting in the DCS World and recorded a video where I provoke the Lag by flying the F-16C high-G. On the lowest settings the Lag occurs much less often, but still you can cause the Lag to take place. So the problem lies somewhere in the: RENDERING THREADS (CPU Bound (Rendering Thread), CPU Bound (FPS Limit), CPU Bound (Main Thread), GPU Bound(?)). While researching the Lag, I have noticed that when the Game rendering is GPU Bound the Game doesn't lag at all, but the GPU Bound rendering doesn't last long for some reason. But then again, I am not a PC expert, I don't know much about it. So the problem is somewhere in the performance of the rendering process of the Game. Now I know it sounds kinda far-fetched since only I am using the Object Local Camera as the Chase Camera, but go ahead and try to fly the F-16C the same way I do, and check if the Lag exists for you. If the DCS World F-16C or F-15E won't lag for you with the same Local Object Camera configuration during the high-G, that means that the problem is on my end, but if it does lag for you as well, then the problem lies in the DCS World itself. There is no continue with the issue that I experience until someone tries to fly the F-16C with the Object Local Camera set as the Chase Camera. How to set the "Object Local Camera" as Chase Camera? Bind actions "Local Object Camera", "Zoom In Slow", "Zoom Out Slow" for the F-16C. Then chose the "Object Local Camera" in the aircraft list and bind actions Camera Height Up Slow, Camera Height Down Slow, Slow Left Key LCtrl-A, Slow Right Key LCtrl-D. For example: LRCTRL + NUMPAD8 Camera Height Up Slow LRCTRL + NUMPAD2 Camera Height Down Slow LRCTRL + NUMPAD4 Slow Left Key LCtrl-A LRCTRL + NUMPAD6 Slow Right Key LCtrl-D Load the F-16C on any map, press the "Object Local Camera" key and use the Camera Height Up Slow, Camera Height Down Slow, Slow Left Key LCtrl-A, Slow Right Key LCtrl-D, "Zoom In Slow", "Zoom Out Slow" keys to place the Object Local Camera behind the F-16C. A video of how it looks like is attached to this post. And check for lags, maybe it is only me who can't fly F-16C with a proper Chase Camera without lags. F-16C Lag.mp4 Object Local Camera Configuration.mp4

Hi, yes I do still have issues with the performance of the DCS World. The F-16C and the F-15E are causing the most issues. The F-16C has worse performance than the F-15E. The occasional Lag of unknown origin is occurring during high-G maneuvers and during high-speed flight, during fast change of the scene on the screen (when the full sky screen rapidly changes to a full land screen during the high-G maneuvers, or during high-speed flight maneuvers). I do not know the cause of this phenomena, but from what I understand it is directly interconnected with amount of scene rendered on the screen and the flight model scripts of the full fidelity aircraft being processed during the high-G maneuvers or the high-speed maneuvers. Due to the fact that I use the Object Local Camera instead of the built-in Chase Camera (because of the detrimental camera sway of the built-in Chase Camera) the Lag with the F-16C and the F-15E in particular are observable quite often. I have doubt that the 32 GB of RAM is causing this Lag phenomena to appear, mainly because other full fidelity aircraft (A-10C, AH-64D, Ka-50, Mi-24P) are performing much better than the F-16C and the F-15E, maybe it is because those are the slower flying ones, and the scene on the screen changes less frequently and that there is less high-G maneuvers. The performance of the A-10C, AH-64D, Ka-50, Mi-24P is such that I can't notice lags even if they still take place. The Flaming Cliffs aircraft on my end performs flawlessly, high-G or no-G - all the same. Maybe the Over-G performance of the F-16C and the F-15E is the route cause of the Lag. But this time I managed to gather some evidence to back up my case. Some F-15E screenshots and a F-16C short video of less-than-average-quality (<50 MB). Notice the Lags captured on the F-15E screenshots during the rapid change of the flight regimes. Just in case, I added the DCS World log and the DxDiag. Is there any thing else that I can provide in order to help to pinpoint the root cause of this Lags? F-16C - Example Of Lag.mp4 dcs 10.04.2025.log DxDiag 10.04.2025.txt

My bad... Setting the Pagefile Size to 32 GB didn't help. I confused the positive effect of it with the performance gain from ParkControl software (still didn't got used to it's effect on the PC). Setting Pagefile Size to 32 GB didn't have any observable impact. In the Task Manager the used Commited Memory value didn't go above 30 GB, but in fact the maximum Commited Memory value was 64 GB. As things look at the moment, the issue described in this topic is indeed caused by the lack of RAM, however reducing the Terrain Preload Radius helps a lot, something around 30600. Thank you for your attention.

Thank you, your suggestion helped a lot. Setting the Pagefile Size minimum and maximum value to 32 GB improved the DCS World performance, as well as PC overall performance. A follow up question: what is the optimal Pagefile Size minimum and maximum value provided that PC has 64 GB of RAM?

Hi. While flying the Ka-50, I have noticed that the KU-31 Shkval can't lock onto destroyed wrecks of vehicles, even after the flame and smoke is gone (in this scenario it is hard to distinguish the wrecks of vehicles from live targets, same like in the real world, which is how it must be. So I think, if on a Shkval screen there is a live tank and a wreck of the tank, the pilot must have the possibility to lock onto the wreck of a tank due to failure to distinguish the actual target from a dead target, and waste the precious Vikhr ATGM, which costs big $$$$$. In this case, if the Vikhr missile is wasted, that means that the pilot has poor competency - which is a big minus for the pilot. So, Pilots, what do you think? How WE want to fly? Do we need a help from a machine to chose to be dumb? Or should we start playing seriously, like in the real world? Totally up to you, but keep in mind that the real world will not forgive stupidity.

Hello Pilots. While flying the Digital Combat Simulator World (not MT), I have encountered a weird problem. First I had an overall poor performance of the DCS World, it was solved with the help of the DCS World Community. The problem was in Windows 10, the system was parking CPU cores, it was solved by the utility named ParkControl. Overall performance of the PC has greatly improved, in every game. Thank You for that. Now onto the issue of this topic: 1. I use only keyboard for flying, no mouse (like in the first Lock On - Modern Air Combat, the Classic). 2. I use Object Local Camera configured as the static Chase Camera (looks like in the Ace Combat series, but feels much better because of the superb DCS World flight model). The built-in Chase Camera shifts the screen during turns of the aircraft, I find it very annoying, and I lose sense of control of the aircraft. 3. So while flying like that I am noticing occasional Frames Per Second drop that last like 0.5 seconds. These FPS drops happen when performing high-G turns on full fidelity aircraft. 4. I noticed that the Flamming Cliffs series aircraft almost entirely lack the FPS drops, so this leads to a conclusion that the FPS drops are directly connected with the giant amounts of script that represent the full fidelity aircraft. So maybe someone can share his experience and shed some light on this issue. DCS World log while flying the F-15E without enemies in Afghanistan is included. DxDiag also is included. And a screen shot of how the Object Local Camera looks like in the role of the Chase Camera is also included. With big respect to the Fighter Collection ($$$$$), the Eagle Dynamics, the Friends of the DCS World (Other Studios), and the precious DCS World Community. Please, help me. DCS World Log 09.03.2025.log DxDiag 09.03.2025.txt

To be honest, ParkControl helped the entire PC performance. Thank you very much.

Greetings! I was working on the transfer of a DCS World onto another Hard Drive, and the process itself turned out to be not that simple, so I thought that I should share some important moments with others. 1. Before uninstalling the DCS World, make sure the game is set to "ONLINE MODE". 2. Before uninstalling the DCS World, save the Input Profiles of the aircraft you want to fly. This is done in "OPTIONS -> CONTROLS", then select the desired aircraft, click on any field in the "Keyboard" column, and press the "Save Profile As..." button, save the Input Profile somewhere safe. Also it is advised to save the Input Profiles for the "UI Layer", "General", and the "Object Local Camera" and others, if they were configured by you. 3. Before uninstalling the DCS World, make a backup (a copy) of a folder located at "C:\Users\User_Name\Saved Games" named "DCS", this folder contains the program's Performance Settings. 4. Download the DCS World Installer from the original DCS World homepage. Proceed with the installation, and select the desired location on your Personal Computer . 5. During the installation (downloading of the program) make sure that the Personal Computer is set not to go into the Sleep Mode, because this can abrupt the installation process. This can be done in the Power Settings of your Operating System. 6. After completion of the installation of the DCS World main program, launch the DCS World and download the desired modules. 7. When the DCS World is completely installed, go to "C:\Users\User_Name\Saved Games" and delete the folder named "DCS", and paste in that same location your backup folder of the program's Performance Settings (folder "DCS") (read "Step 3"). 8. After the restoration of the DCS World Performance Settings, restore the Input Profiles by going into "OPTIONS -> CONTROLS", then select the desired aircraft, click on any field in the "Keyboard" column, and press the "Load Profile" button, navigate to the required Input Profile, and select it. Repeat "Step 8" for all the aircraft you want to fly. 9. And finally don't forget to restore the Power Settings of your Operating System. Hopefully someone will find this information useful. Thank you for your attention.

Through some miracle I came across something that might help those in need... It appears that the Microsoft Windows (10) hides from the user a very important system processor settings. The settings in question are: 1. Processor performance core parking min cores 2. Processor performance core parking min. cores for Processor power efficiency Class 1 Both settings must have 100% value set. By default they are hidden from the user in the Processor Power Management in the Power Options. The way to get to alter those settings is to download and install a third party software named ParkControl. ParkControl - CPU Parking and Frequency Scaling Inside the software you need to set the Performance (P) Cores to 100%. Also, you need to set the Efficiency (E) Cores to 100%. The original Author Of The Solution is BJ55. His message: "In Settings disable "start at login", once configured there's no need to run the program in background". Thank you very much. This third party software appears to be something that is downloaded along with the next DCS World update. I mean the software is basically essential for some people to enjoy the DCS World. Can someone check this?

Thank you so much! It appears that the problem was on my end indeed. My bad, my apologies, but also keep in mind that it required some serious voodoo to solve. Thank you very much for your help, very good and comfortable forum, big respect, and wish you well.

Hi! I need help with this anomaly I have encountered. Just got wondering what the DCS World Log looks like and went on to reading it, it turned out that it is a 1000 line text document containing important information on the game performance, and I noticed totally unexpected lines: 2025-02-28 11:47:48.804 WARNING EDCORE (Main): CPU HAS PARKED LOGICAL CORES (this can be source of stuttering and reduced performance especially on hybrid CPUs with P/E-cores) Unexpected, because setting Processor Performance Core Parking Min Cores is already set to... 100% Or it should be 0 %? I added my DCS World Log and the DxDiag, maybe some PRO can help me out and take a look at them. Thank you. Thank you for your attention! DCS World Log.txt DxDiag Core Parking.txt

Came across a possible way to increase performance of the DCS World. Maybe some one still doesn't know about this. The possibility to increase the DCS World performance by adding the DCS World related files to the Windows Defender exclusion: Windows 10 -> Settings -> Update & Security -> Windows Security -> Open Windows Security -> Virus & Threat Protection -> -> Manage Settings (Under the Virus & Threat Protection Settings) -> Exclusions -> Add An Exclusion Add two Folders to the exclusions: C:\Games\DCS World C:\Users\YOUR-NAME-HERE\Saved Games\DCS Add two Processes to the exclusions: C:\Games\DCS World\bin\DCS.exe C:\Games\DCS World\bin-mt\DCS.exe This might help, but might not... And don't forget to turn off Steam while playing the DCS World. By the way, the notorious FPS Spikes still do occur, additional observation suggests that: 1. The FPS Spikes occur when there is some change in the CPU work while processing the game. In detail: the FPS Spikes occur when CPU Bound (Rendering Thread) is replaced by CPU Bound (FPS Limit), and vice versa. When the swap occurs there is a greater chance for the FPS Spike to be triggered. The FPS Spike - a moment in time, when resources that are being processed by one instrument (CPU Bound (Rendering Thread)), are getting send for processing to another instrument (CPU Bound (FPS Limit)). The time it takes for the swap of the processing instruments is the FPS Spike. 2. The phenomena that causes the most FPS Spikes is the drastic FOV change. Personally, in addition to he Cockpit Camera, I take advantage of the Orbit Camera, Fly-By Camera and Object Local Camera (configured as a static Chase Cemera). The resources that need rendering inside the FOV constantly change, and this causes the FPS Spikes. Maybe this is the case why some other players do not experience the FPS Spikes, because their FOV is confined within a cockpit.

WHEN THE TRUTH IS RIGHT IN FRONT OF YOU, AND YOU GO PRETENDING THAT IT ISN'T THE TRUTH, YOU GO...

Why not?