Loading...
  OR  Zero-K Name:    Password:   
Title: MM 729: 1v1, Rank Singularity
Host: Nobody
Game version: Zero-K v1.8.9.0
Engine version: 104.0.1-1544-ge1f249f
Started: 3 years ago
Duration: 30 minutes
Players: 2
Bots: False
Mission: False
Watch Replay Now
Manual download

Team 1 Won!
Chance of victory: 80.9%
XP gained: 124
EErankAdminAnarchid
Team 2 Lost
Chance of victory: 19.1%
XP gained: 193
NZrankesainane died in 30 minutes




Preview
Filter:    Player:  
sort


3 years ago
At 12:00 my commander near NZrankesainane's base is beset by Glaives:



It is armed with an HMG (weapon 1) and Rocket Launcher (weapon 2), and it is on fire at will.

It proceeds to not shoot at anything until manually ordered despite being in a target rich environment that is in fact shooting at it.
+1 / -0
An environment deeply saturated in target-based nutrition?

I don't know if this is still a problem or related but I noticed when duel wielding that there were edge cases where the more rapidly reloading weapon would wait for the slower (Rocket) weapon to be reloaded to fire briefly, then stop again. Like you'd only get a burst of HMG or laser during the rocket shot.

See if the above still bears weight when you investigate this.
+0 / -0


3 years ago
I think it can be entirely explained by the rocket launcher aiming at things that the machine gun cannot hit, either due to occlusion or range. Just look at which way the commander is pointing throughout the engagement. This is the peril of having two different weapons use the same heading-turret. Both weapons will only fire if they agree on a target, and it looks like the primary weapon wins ties.
+1 / -0


3 years ago
AUrankAdminGoogleFrog that also explains why when I tested my take on the issue, it was only reproducible half of the time - based on which weapon was upgraded first.

This is going to sound hacky AF but the first fix that comes to mind is to always designate the lowest range weapon as "primary" in terms of target conflict resolution.
+0 / -0


3 years ago
quote:
This is going to sound hacky AF but the first fix that comes to mind is to always designate the lowest range weapon as "primary" in terms of target conflict resolution.

In this case, HMG is weapon 1, which sounds like it should be primary.
+0 / -0


3 years ago
Then perhaps it is the secondary weapon that wins the targeting race. Or perhaps it is down to the order of the weapon in the weapondef. Try rearranging that.
+0 / -0


3 years ago
Now MG can cause rocket launchers to not fire.
https://github.com/ZeroK-RTS/Zero-K/commit/80bbcf81c7eef54001199dabd9898a8a12aab75d
+3 / -0