A Hamburgler

Didn’t realize how much my old i7 was holding me back in performance. I used to be on the ground with 30 or less FPS sometimes low 20s and now with the new 9800x3d I’m at a solid 60 fps (which is were it’s capped at) on the ground with hundreds of ai the in the mission. I’m still using my 3090 so that didn’t change. Can’t believe the performance increase.

I see a repeat of when the 30 series released.

Cool, im excited to see how this new build turns out. I probably built my first PC around 2012 and have been exclusively intel so I’m in the same boat.

Just gaming and vr. After doing research I kinda came to that resolution too. Just get the 9800. If I feel the need to upgrade later on I can. Will be my first ever AMD. Been with intel for like 10 plus years now. It’s time to give my I7-10700k up.

I’m waiting for the 9950X3D to release in march. Basically gonna be the 9800x3d with more cores.

The issue is being discussed here.

So with that aspect they might as well cancel the dynamic campaign. Two four ship flights and 10 ground units for a thrilling environment.

You’re missing the point. 2.9.5 could easily run a mission with over 900 units. This creates an environment with multiple threats and complex packages. Now missions can only handle 100 or less units. This creates an empty environment with nothing going on. Again this is not a hardware or user problem. Missing the point again the missions still run fine with 900 plus units on 2.9.5.

Was this just a general FPS decrease across the board or was this a FPS decrease in large complex missions only?

All good but ya when you hit that barrier or threshold it never returns. Gone forever.

The thread was created concerning "massive dynamic campaigns or multiplayer missions" not just a small FPS decrease. I play a complex mission in 2.9.5 with 160 FPS and that same mission runs in 2.9.7 with 9 FPS. Thats over a 100 FPS loss. That is what we are talking about here. Lowering settings or anything of that nature will not have you regain a 100 FPS. In small missions my game runs fine.

Interesting I may try that. I actually didn’t realize how many units DCS could actually handle pre 2.9.6. Damn near 1000 and now its like 100 or less.

I think I tried almost every DCS option from a fresh install, removed old saved games fold, no tactview, no mods, no mission scripts, no mission triggers, and so on. I have both 2.9.5 and 2.9.7 installed on different drives so i can test back and forth. This is why I dont think its a driver or windows issue because 2.9.5 still runs the missions fine. Regardless I appreciate you guys taking the time to look into the issue. Thanks for the feedback and updates about it.

Thats the point of this thread. In 2.9.5 I could easily run a mission with over 600 units in total and now in 2.9.7 Im lucky if I can get 50 units.

An answer to all your problems is Falcon BMS. I started to play it after 2.9.6 release and I am a couple weeks in a campaign and can’t stop flying missions. I can’t believe I slept on BMS for so long. There are so many basic features that is missing from DCS like ATC, comms ladder, a bunch of AI commands, and so on.

@BIGNEWY I noticed something. If you look at the graphs and look at 2.9.6 how it spikes about every second. In the log I noticed a repeated message. WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED I then went to the log on 2.9.5 and this is not in there. After a little further digging I was going through some of the forum posts with people who described a similar issue as mine. I looked in their logs too and sure enough they also have the same message repeated. WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED So what causes this ANTIFREEZE during AI heavy missions in 2.9.6 vs 2.9.5? This causes me to go from 160 FPS in 2.9.5 to 9 FPS in 2.9.6 (also 2.9.7). Might be something to look into. dcs 2.9.6.log dcs 2.9.5 (1).log Interesting I also have to force close my DCS app.

One thing I have mentioned before but I will again. I seem to notice that everyone who describes the same issue all has this in their logs. WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED It is then repeated until ending the game.

That’s why I enjoy falcon BMS campaign because the AI will make decisions on what to strike, sead, and so on. You can adjust multiple sliders to prioritize certain targets/ target types. At that same time you can create your own packages.

Below are two images. The first one is 2.9.6 and the second one is 2.9.5. Its the same mission no scripts, no triggers, no mods, and look at the difference. I have been playing DCS for years and understand all the trouble shooting you need to do. I have done everything from removing tacview, fresh install, clearing fxo, and so on. Nothing has work and it seems to be narrowed down to the update with the issue. Please tell me how you go to 160 FPS in 2.9.5 to 9 FPS in 2.9.6. That’s not some small decrease. That’s an issue with the update.

Having the same issues since 2.9.6. I posted about it here with logs and photos.

Yes but if the resources permit. I could easily see a DC where you are on the defensive with limited aircraft, limited supplies and you have to hold out until reinforcements get to you. This case if there were aircraft that had a rearm, refuel, and repair this would create a great strike opportunity. I don't know if you ever played Command Modern Operations but that is a huge part in planning missions is the time it takes for aircraft to rearm, refuel, and repair. This is not so much an issue when you have a lot of aircraft as you said you can just send out a replacement before they RTB.

Very good questions indeed. I am also wondering about how aircraft will go out on multiple missions. For example if an awacs plan flies a mission and returns to base will there be a time delay for that same aircraft to refuel before it can go out on another mission. Also with other aircraft if they need to change their load outs will there be a time delay. So if an aircraft RTBs before it can fly another mission it may take an hour or two in game time to refuel and rearm which now gives you a chance to actually strike that target. This would be an interesting concept because it may actually create a reason to perform recon missions and locate actual targets before you send a strike package out. I am excited to play DCS in new ways. I think it will be fun to even do recon mission along the frontline. Imagine spotting a column of tanks heading to the front. You then send out a package to blowup a nearby bridge which now forces the tanks to take a new path or slows them down. This could give you time to move som troops around and so on. As mentioned above being apart of a mass transport of troops would be cool. Hopefully the DC will really make DCS shine.

2024-07-27 03:09:05.651 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED 2024-07-27 03:09:12.339 WARNING LOG (19316): 8 duplicate message(s) skipped. 2024-07-27 03:09:12.339 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME 2024-07-27 03:09:13.184 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED 2024-07-27 03:09:24.947 WARNING LOG (19316): 12 duplicate message(s) skipped. 2024-07-27 03:09:24.947 WARNING TRANSPORT (Main): CREATING PATH MAKES TOO LONG!!!!! 2024-07-27 03:09:25.236 WARNING LOG (19316): 6 duplicate message(s) skipped. 2024-07-27 03:09:25.236 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED 2024-07-27 03:09:25.270 WARNING TRANSPORT (Main): CREATING PATH MAKES TOO LONG!!!!! 2024-07-27 03:09:26.224 WARNING LOG (19316): 22 duplicate message(s) skipped. 2024-07-27 03:09:26.224 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED 2024-07-27 03:09:30.822 WARNING LOG (19316): 5 duplicate message(s) skipped. 2024-07-27 03:09:30.822 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME 2024-07-27 03:09:31.678 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED 2024-07-27 03:09:43.826 WARNING LOG (19316): 16 duplicate message(s) skipped. 2024-07-27 03:09:43.826 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME 2024-07-27 03:09:44.564 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED 2024-07-27 03:09:54.001 WARNING LOG (19316): 12 duplicate message(s) skipped. 2024-07-27 03:09:54.001 WARNING TRANSPORT (Main): CREATING PATH MAKES TOO LONG!!!!! 2024-07-27 03:09:54.330 WARNING LOG (19316): 1 duplicate message(s) skipped. 2024-07-27 03:09:54.330 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED 2024-07-27 03:09:54.538 WARNING TRANSPORT (Main): CREATING PATH MAKES TOO LONG!!!!! 2024-07-27 03:09:54.955 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED Straight from the log this seems to be the issue maybe.

So here is the log this issue happens with both SP and Sever. It also happens with ST and MT. The file dcs.log is for version 2.9.6 with the issue and dcs 2.9.5 log is the log for 2.9.5. I also noticed that with 2.9.6 when ever i quit to desktop the game never closes and i have to go in the task manager to actually close the game. Below are two images. The first one is 2.9.6 and the second one is 2.9.5. Its the same mission no scripts, no triggers, no mods, and look at the difference. @BIGNEWY Hopefully this is enough information. Thank you! dcs.log dcs 2.9.5.log

Hey guys just did some testing. So with the most recent update in AI heavy scenarios I get less then 10 FPS. The mission is an unplayable slideshow. I reverted back to 2.9.5 and played the same scenario with perfect frames. So I dont know what the issue is in the new update the is causing this. So with 2.9.6 it just consistently spikes causing the low frames. Again 2.9.5 is smooth as could be. Both same mission no scripts or anything.