2019-11-20 01:12 CET

View Issue Details Jump to Notes ] Related Changesets ]
IDProjectCategoryView StatusLast Update
0005715Spring engineGeneralpublic2017-08-23 17:54
ReporterGoogle_Frog 
Assigned ToKloot 
PrioritynormalSeverityminorReproducibilityalways
StatusresolvedResolutionfixed 
Product Version103.0 +git 
Target VersionFixed in Version 
Summary0005715: 103.0.1-1272 noExplode weapons avoid non-target enemies
DescriptionWeapons with noExplode do not fire if their line of fire is blocked by an enemy unit that is not their target.

To reproduce:
 * Spawn a Pyro (jumpraid).
 * Set the Pyro to hold fire.
 * Spawn a large unit nearby for team 1. I used factorycloak.
 * Have the Pyro fire at the ground behind the enemy unit.
 * Notice that the Pyro is not firing.

103.0.1-1198-g3ff8f21 has the bug. 103.0.1-1169-gd576c41 does not have the bug. I have only tested with low spread weapons so this may just be an issue for low spread weapons.

Here is the ZK ticket made by a player: https://github.com/ZeroK-RTS/Zero-K/issues/2481. I was unable to reproduce the bug with firing through wrecks. Spawned wrecks are not quite real wrecks though so a bug may exist.
TagsNo tags attached.
Checked infolog.txt for Errors
Attached Files

-Relationships
+Relationships

-Notes

~0018234

Google_Frog (reporter)

This does not just occur for noExplode weapons. It seems to occur for all weapons with low spread.

~0018236

Kloot (developer)

The cause is already known.

~0018262

Kloot (developer)

Fix d3226687044e9b633791ef9ab4af56ec4cbd692f committed to develop branch: fix 0005715, repo: spring changeset id: 8619
+Notes

+Related Changesets

-Issue History
Date Modified Username Field Change
2017-08-20 12:59 Google_Frog New Issue
2017-08-20 12:59 Google_Frog File Added: screen00495.jpg
2017-08-20 20:41 Kloot Assigned To => Kloot
2017-08-20 20:41 Kloot Status new => assigned
2017-08-21 16:17 Google_Frog Note Added: 0018234
2017-08-21 16:25 Kloot Note Added: 0018236
2017-08-23 17:54 Kloot Changeset attached => spring develop d3226687
2017-08-23 17:54 Kloot Note Added: 0018262
2017-08-23 17:54 Kloot Status assigned => resolved
2017-08-23 17:54 Kloot Resolution open => fixed
+Issue History