CMO v1.10 Build 1900.18 Beta, New C-UAS Interceptor Drone Units Bug

[foxid259]

Hi developers,

I have systemically tested the newly added C-UAS drone interception assets in Version 1.10, Build 1900.18 Beta (using DB3K v519) and confirmed a fatal database mismatch that breaks both the DB Viewer and the live game simulation loop.

Affected Units:
1)SAM Sec (Merop C-UAS Drone);
2)SAM Sec (Sting C-UAS Drone);

Step-by-Step Replication:
1. Load the attached scenario save file (.scen / .sav).
2. Observe the incoming enemy Shahed-136 UAV flying at 1000 ft (as captured in Screenshot 1).
3. Select either of the C-UAS units and press F1 (Manual Attack) to order it to intercept the Shahed.

The Bug Symptoms:
- Simulation Freeze: The exact millisecond the attack command is issued, the simulation time loop permanently freezes. The game clock stops ticking (x1 compression is active but frozen), and units stop moving. The main UI/menus remain responsive, but the game world simulation is dead.
- DB Viewer Corruption: If you attempt to open the DB Viewer card for these units and click directly on the interceptor drone weapon carried by them, the DB Viewer window immediately crashes into a solid white screen (Screenshot 2). The data fields fail to render due to a core data linkage corruption in the .dxdb template for these hybrid platforms.

I am attaching both Screenshot 1 (before the bug), Screenshot 2 (the DB Viewer failure), and the scenario save file so you can easily replicate and fix this issue in the next beta build.
Thank you!

[Raptorx7_slith]

Logged as 0017612

[Dimitris]

I believe this has been fixed in B1900.20 ?

[Raptorx7_slith]

Yes

[foxid259]

I believe this has been fixed in B1900.20 ?

So, I just tested it—the issue has been fixed.