Limaro

About the not saved flags and group activations: That would be very cool that an once activated group remains active after loading. However, for those who also struggle with this, there is a little workarround that works for me at the moment. Let's assume, you want to activate a group (lets call it SupportForces) using the F10 Menu. (Set flag, activate group trigger rule). In order to restore this state after loading do the following: - Create an additional single unit group (lets call it twintrigger) far away which is active from beginning - a kind of activation-twin - Add a small trigger zone just beside it - Add a waypoint to move twintrigger into the zone - Add a 'hold' to the initial waypoint - > but with 'condition stop' flag, in order to make the twintrigger move only when flag is set - Add a trigger to set this flag whenever you activate your SupportForces . - Important: Add a trigger, to also enable SupportForces when 'Parts of twintrigger is within the zone Or maybe I oversaw an other, very obvious way to do it. in this case.. never mind

You can Test the App "Process Lasso" to improve workload of CPU.

Hi there, I just want to share my experiance upgrading the system as the results are quite impressive. As the title says, I upgrated my GPU. Before I did so, I created a small session in Afghanistan and recorded the replay with MSI Afterburner before I made the changes. Afterwards, I run the same clip recording again with MSI Afterburner. These are the results: AMD 6900 XT 23-05-2025, 17:14:30 DCS.exe benchmark completed, 5091 frames rendered in 74.281 s Average framerate : 68.5 FPS Minimum framerate : 53.5 FPS Maximum framerate : 92.9 FPS 1% low framerate : 39.8 FPS 0.1% low framerate : 39.7 FPS RTX 5080 24-05-2025, 15:38:24 DCS.exe benchmark completed, 12052 frames rendered in 77.281 s Average framerate : 155.9 FPS Minimum framerate : 125.4 FPS Maximum framerate : 197.8 FPS 1% low framerate : 39.4 FPS 0.1% low framerate : 22.1 FPS Honestly, I did not expect this increase of performance. By test sites I expected about 80%plus, bus this is now 127% plus. I am playing 2D in 4k. My CPU is a AMD 5800X3D, 64 GB DDR4 3200 RAM, X570 Mainboard I know this a very short "test" and would not fulfill verbose analysis. Just one run - in Afghanistan in a F/A18 from inside and outside, no other planes and just ~75 seconds. However, I think this can help one or another when thinking to upgrade. @ED It would be great to have a common benchmarking function to get more reliable results across the whole community. Kind regards Limaro Benchmark_Afgh.trk options.lua

Thanks for your feedback @razo+r and @Theodore42. I Managed to reproduce it, It's related with the pressure and RPM. Even though it's not happening often, I now know what to do better

Hi, I am currenlty very confused. I flew the P51 very gently, started an attack of a ship, and right after the attack my engine failed. I dont see a reason for that. Maybe some Veterans here can help me out. I made a video of the whole situation also showing the whole cockpit switches. - I verified that I was not hit by external view and TacView - I was to high to get hit by the bombs. PS: Thanks to ED, that Track-Files work so reliably now

Thanks, this showed the first issue. I accidently hat a trail formation in the default setup in my 0th waypoint. This is solved. Also I fixed the crashing. ONe group was only set to stay in formation until WP1. However, some groups still fall back out of the formation just before the bombing. I "solved" that now by setting the waypoint where bombing starts not so farm from the bombing location itself. Something confused me in that video. I previously saw the one from the grim reapers, and there they configure only the leader, telling that all settings are inherited from "slaves" of the formation. in that one now, he tells to improve performance to only set ROE for some groups. Did this change meanwhile?

Hi, I am currently deperately trying to get a bomber group to work. I currently have three problems. 1. The very first group (B17-1), the leader of all, is also a set of three B17, (actually like all the other groups). However, it's the only one where the second and third plane are placed far behind the first, and they need many miles to catch up. 2. Just before the carpet bombing, the B17-5 and B17-7 are starting to fall behind without any noticable reason. 3. After the bombing many plances are crashing in each other. Are there three tricks to fix this behaviours? I've attached the mission B17Crash.miz

Thanks @Flappie. IT seems to BE Same. Sorry I Just recognized I failt totally on Location of this thread

Since patch 2.9.12.5336 I have the aircrafts that start flickering, also parts of my own. I managed to make a screenshot showing the effect. As you can see there only the wing disappears, but not the fuel tank. It happened only in multiplayer so far for me. dcs.log

I found only in KA-50 III having that problem. Could an admin please move this to the KA-50 III area, I think it will be more appropriate? https://forum.dcs.world/forum/1108-bugs-and-problems/. Maybe there will be more help to reproduce this specific issue to trace down the root cause. I am sorry for the inconveniences. The patch came, when I was learning and only flying the KA-50 III so I did not notice this in first place.

I also had that error. easily reproducable. Mission and logs attached. My steps: - Joing the KA-50 III Slot - Change slot to KA-50 - Switch back to KA-50 III. Only restart of game helpes. Closing mission and loading again does not help Performance_Test_All_planes.miz dcs.log

I guess I found the actual reason for the drop of performance. It's the weapons. As soon as the KA-50 III is armed the performance drops when looking at it from cockpit. (In the outside view there is no effect). in 2D it's also reproducable, but the performance drops are somehow very little in that case. I attached three screenshots that shows the effect, when moving the head near the window. The last shows in performance meter the CPU getting a ventricular fibrillation. I hope someone else can confirm this. I just learned to fly the KA-50, and now, cannot use it any more.

Hi, since last patch, performance dropped a lot in my test mission. Especially in VR this resulted in being unplayable. After some testing I found, that it's somehow related to my mission (attached). However, this mission is very small without many units or triggers. I tried to figure out, what in the mission does cause the drops by removing everything. I tried a lot but could not figure out what causes the dramatic loss of performace. The screenshot shows the performance monitor in case of bad performance. Many unexplainable spikes in CPU area. This leads to stuttering movement and lags. In non-VR it dropped from nice 80-95 FPS down to ~65 FPS. this is a rough guess. null The missions I attached: - KA50III_Syria_Test. This is my original test mission which became unplayable. - KA50III_Bad_Perf. This is the mission, where I nearly removed everything. Only KA50 remaining. It's a little bit better, but not that much. - KA50III_Good_Perf. I just created a new mission placing the KA50. that works fine. It would be interesting if someone can confirm the hugh differences in the missions that I observe. I will try to reproduce and test further things in 2D, but just have not that much time. EDIT: Some strange findings, which I'd like to add: In my KA50III_Syria_Test it seams to be depending on the position of my head. When I move closer to the window, it starts stuttering. when being perfectly centered, everything is fine. Also in game pause, easy to reproduce. but only in this mission, the other us not affected. EDIT 2 I've tried the FA-18, there is no such effect. also external view seam to be unaffected. Maybe an issue with the KA-50? KA50III_Syria_Test.miz KA50III_Bad_Perf.miz KA50III_Good_Perf.miz dcs.log

Hey, I am currently experimenting a lot with VR. As everyone knows, the resolution is not yet that great. To enable more realistic target recognition, I use the lower zoom function to make objects appear slightly larger. However, when flying a helicopter, there is a lot of wobbling. While this might be realistic because helicopters naturally shake, in reality, the human eye is quite effective at compensating for such movements. Therefore, it would be reasonable to reduce or even eliminate this effect while zooming. Limaro

For me it looks like Vsync. I see it's disabled, but maybe active over nvidia driver? It would also explain the parking.