There is maybe a discussion to be had about what optimizations could be done in the sim to make high numbers of blind/"dumb" units more performant. Or to add an option to make civilians (once positively identified as such) appear smaller in the UI, reducing visual clutter.

The message log is showing INS drift values that seem plausible to me in this case (50-100m typically for a flight time of 6 minutes, e.g. 0.6nmi/hr * 0.1hr = ~100m). So that is fine. But the issue is that the simulation is not actually applying the INS drift modifier to the CEP. The message log ...

Yes, I'm noticing a lot of stuttering as well. I haven't tested if it's specific to this scenario or not.

Yes, tested to be fixed!

Still an issue in 1706.

Still an issue in 1706 - 19x F-15Es ditch while on the mission, another 2 on RTB.

Fixed in 1706, thanks!

Still appears to be an issue in 1706.

Follow-up to a related bug. In this scenario both missions have "max receivers in queue per tanker" set to 1. However, this limit is not respected, and often all the fighters go to the same tanker anyway.

Get ready for a firestorm....

Bump, as there is renewed discussion of ABM early warning. From what I can tell, the LRDR in the simulation still has a much lower detection range against IRBM/ICBM threats than it is advertised as having.

Try the (extremely overkill) SBX-1 radar. If that doesn't work then nothing will, in which case it's likely a bug.

In the meantime, you can use this patched version.

Okay, thanks.

You can take a look at the flight plan in the posted scenario; it already uses explicit refueling points.

Can you explain what part of that scenario isn't set "properly"? Doctrine is set to "refuel with nearest tanker" which should clearly enable correct tanker selection and has in previous versions. You shouldn't have to manually restrict the flights to tankers within 100nm.

(Also, FWIW, this isn't ...

Yes, it seems possible to fire sometimes after clicking around a bunch, unassigning/reassigning, etc.

thewood1 wrote: Sat Jul 05, 2025 9:36 pm Set the tanker choice to any tanker within 100nm range of the receiver and the mission ran perfectly.

When I do that (as in this attached scenario), the aircraft all RTB after the first tanker, which seems to be yet another issue. Are we on the same build (1676, i.e. v1.08 stable)?

Here is a (zipped) video showing the submarine's depth behavior while the depth is set to "max depth." The issue is the submarine does this instead of forcibly going to periscope depth, yes. This also affects the AI, e.g. when an AI submarine is tasked on a patrol mission having max depth configured.

Sure, there are workarounds. Doesn't address the underlying issue though.