Very simple request - pK below 1%, please! The Oerlikon Mk7 Burst, weapon 1636 in DB3K, has a pK of 0.3%, but this is always rounded up to 1% by Command. In reality, hitting a whole bunch of different types of targets should be basically impossible with these guns - but I was playing the first ...

So I built this huge script over a lot of work to replenish, refuel, repair, all that, for EVERY unit on a side - I included a batching system, but it's a bit crunchy. So far, on No BREXIT No Problem!, the first run without a cache takes 200-300ms on my system with a denominator of 1, while running ...

For a normal auto-attack (Just F1) you only have to hold F1 if you're lassoing multiple targets. For a single target just press F1 to activate the targeting cursor and left click on the target. Let me know if I'm missing something


No, you've got it right, for a normal auto-attack you have to ...

No save enclosed due to this being a completely save-agnostic issue and I don't really know what I could set up to demonstrate this issue. When pressing Shift+F1 and then holding the left mouse button, you can select multiple targets for scheduling a manual attack. When pressing *just* F1 and then ...

The error is still present in 1706. I've enclosed a save that proves it. The two F-102s near the viewpoint are chasing where the Tu-16 *was* but isn't anymore. Unassigning them and retasking them causes them to go after where the Tu-16 was at the time of the attack order. This issue also emerges if ...

Set inDevelopment to true using the Lua console. The setup script will ask you whether to do the various startup things, including spawning missions (or not).

Sorry, I should have done so properly. Essentially, when the player side is set as omniscient, units engage the spot where they first detected an enemy unit, not the location they're actually in. This leads to ships shooting at a coordinate where they first spotted an enemy ship while said enemy ...

The error is here:

02/07/2025 18:14:05!!!WARNING!!! EXCEPTION FUSE REACHED (x20 exceptions) FOR : -- Bv1.08 - Build 1674 -- Object reference not set to an instance of an object. -- Scen : Act of War, 1968 -- DB : -- Exception: Object reference not set to an instance of an object.
Stack Trace: at ...

I've been playing around with Lua a lot more lately and I've come upon something I seemingly can't do. Since the Mount wrapper is read only, it's impossible to alter the capacity of a mount through Lua. I'd like to be able to do this to simulate having a portion of the ready launchers on a mount ...

This is an issue that's been reported in the past, but it seems to still be around in 1487 and impairs SOSUS function quite a bit. Peek at SOSUS #3 to see it.

I'm playing around a bit with Lua for my own purposes, and I can't seem to figure out how to alter aircraft exhaustion by Lua. Just getting the requisite unit and setting currentExhaustion to 0 fails since the method doesn't seem to have a setter. Are there any other exposed methods? Is this just ...

Issue still present in 1487. I seem to have mixed something up, so th scenario doesn't load properly, one has to load in as the 'Bug Reporters' side to use it properly.

When two sides are allied, with one being omniscient and the other being human, the human side will only see contacts show up as nameless with an unknown side, course, speed, and altitude. Units are also not relayed at all if they are sufficiently far away. Both properties are demonstrated in the ...

I edited the title to show that 1483 is affected, since the problem still exists. Sorry if I shouldn't have done that. The save still demonstrates the problem in 1483; the issue is specifically not fixed.

Still an issue in build 1483.

Confirmed fixed as of 1468 CIV.

Simple enough. When a SEAL team tries to blow up a target with their high explosives, they inexplicably also get blown up.

Normally, when loading a mission in edit mode, missions set to scrub if the side is human will not be scrubbed. Upgrading the scenario, while now preserving edit mode, still scrubs the missions, which makes plug-and-play upgrading difficult.

Gotcha, here's a save where the exception flood started. Load in as PLAN to see it in action.

To reproduce, load any scenario and upgrade its database. I don't believe this has been reported yet, but specifically, all the editor features EXCEPT the editor tab up in the top go away. Using C or M to manipulate units or groups doesn't work, the Edit Aircraft button doesn't show up, sensors can ...