Matrix Games Forums

So, I was playing the Iran Strike 2025 (from the community pack), and I was messing with the Rapid Dragon Air launched JASSM-ER.

I ordered the C-17s to engage the various targets automatically, and the game's tick rate slowed to a crawl. Is this because I did something way outside the bounds of what the game engine is expected to handle or is there a bug?

I wouldn't be surprised if I just pushed the game too far, since I was trying to launch a total of 684 JASSM-ERs basically all at the same time on a fairly large scenario

Done on Build 1307.2

Save file attached

Almost 700 missiles in the air? In my experience, that'll do it. But there is no upper limit on what you force the game to do. Just common sense. But thats just me experience. Might be dependent on the PC also.

thewood1 wrote: Sat Feb 04, 2023 12:11 pm Almost 700 missiles in the air? In my experience, that'll do it. But there is no upper limit on what you force the game to do. Just common sense. But thats just me experience. Might be dependent on the PC also.

No, I think it has to be something to do with the palletized JASSMs. I just tried launching 640 JASSM from B-1Bs, and the pulse time after launching is less than 200 ms, rather than basically freezing the game like the rapid dragon did

Thats still a crap ton of missiles. I have an i9 and get slow when more than a couple hundred missiles in the air.

I wouldn't be surprised if I just pushed the game too far, since I was trying to launch a total of 684 JASSM-ERs basically all at the same time on a fairly large scenario

----
Besides the fact that as thewood mentioned yes it does slow to a crawl when doing that many (and even hundreds less depend on scene settings and hardware)

I see what you mean in the difference between b-1 (crawl but playable 350-400ms pt) save, vs pallet\c-17 (just not playable...as it seems to seriously choke out at the tail end of ever second for me up to like idk 30 sec last pulse of second) save. I can see a bunch of

2/4/2023 9:50:53 PM -- B1307.2 -- Object reference not set to an instance of an object.
Exception: Object reference not set to an instance of an object.
Stack Trace: at Command_Core.Aircraft_AI.HUCW6nT6NVupy0USB9MM(Object )
at Command_Core.Aircraft_AI.skRoz64QjyN(Single , Weapon& )
Call Stack & Error details:
Error at 1007843634777711,

When playing the c-17 version (per-second) that I don't see in the b-1 version in the exception logs, don't know if it's related though or how to explain difference yet.

I tried b-1 158b vs C-17 doing ~100 each to a single target, separately (most display\overlay options off), in a basically empty scene, both were about same pulse time (1-3ms) and without the 'choke factor' present for both, but that was just simple 2 sides without all the other stuff going just to see if anything popped out at lower scale with the c-17 rapid dragons, didn't seem too, and I got no exceptions during that testing.

BTW one thing I got used to doing while just waiting for impacts was to move map display off the area of the map from where it was all happening, and turn off everything background overlay related as well as most if not all the line\range\plot\etc drawing options, and to not have anything selected in 'tiny' builds. Helps a bit, but 600 is still 600.

Hi captainwolf,
thanks for posting about this issue.
it's now fixed and will be in the next update release

In today testing got a cascade of exceptions that cannot reproduce in the previous save .

One of them is this. And happens in B1892 in the first file uploaded by captainwolf, reproducible. Also the massive slowdown he commented.

02-07-2026 22:31:24!!!WARNING!!! EXCEPTION FUSE REACHED (x20 exceptions) FOR : -- Bv1.10 Beta - Build 1892 -- Object reference not set to an instance of an object. -- Scen : Iran Strike, 2025 -- DB : -- Exception: Object reference not set to an instance of an object.
Stack Trace: at Command_Core.Aircraft_AI.KuE2mQHCFN0(Contact , Single , Weapon& , Boolean )
Call Stack & Error details:
Error at 1007843634777711:

Being able to repro the same error.

Logged 0017397

The fuse error has been fixed for the next update.

Looking at performance hotspots separately.