2024-04-23 11:15 CEST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0002407Spring engineGeneralpublic2012-03-11 21:24
ReporterGoogle_Frog 
Assigned To 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionno change required 
Product Version0.82.7.1 
Target Version83.0Fixed in Version 
Summary0002407: Collide friendly check does not work when inside a friendly
DescriptionThis is most commonly seen when a unit is completed in a factory and there is an enemy nearby. The unit will shoot as soon as it is completed and the shot instantly collides with the factory.
TagsNo tags attached.
Checked infolog.txt for Errors
Attached Files

-Relationships
+Relationships

-Notes

~0006610

jK (developer)

erm what? describe better ...

~0006618

FLOZi (reporter)

I'm not sure if he's saying:
1. He expects the weapon not to fire when obstructed by a friendly unit when collidefriendly is true
2. the weapon is colliding with a factory when it shouldn't be.

I think the former, and in that case, that behavior is tied to avoidfriendly tag.

~0006622

KingRaptor (reporter)

It seems that if a unit center is inside a friendly unit's hitvolume, the inner unit will not check if its shots will collide with the outer unit (of course, they do).

~0008423

Kloot (developer)

Last edited: 2012-03-11 21:24

"It seems that if a unit center is inside a friendly unit's hitvolume, the inner unit will not check if its shots will collide with the outer unit."

It will and does check (when avoidFriendly=true, which defaults to that).

If on the other hand avoidFriendly=false and the inner unit fires, its shots collide with the outer IF AND ONLY IF collideFriendly=true (also the default), and that is not a bug but expected behavior.

+Notes

-Issue History
Date Modified Username Field Change
2011-04-16 09:30 Google_Frog New Issue
2011-05-07 14:42 jK Note Added: 0006610
2011-05-07 18:12 FLOZi Note Added: 0006618
2011-05-09 09:12 KingRaptor Note Added: 0006622
2011-06-10 16:35 hoijui Target Version => 0.83.0
2012-03-11 21:23 Kloot Note Added: 0008423
2012-03-11 21:23 Kloot Status new => closed
2012-03-11 21:23 Kloot Resolution open => no change required
2012-03-11 21:24 Kloot Status closed => feedback
2012-03-11 21:24 Kloot Resolution no change required => reopened
2012-03-11 21:24 Kloot Note Edited: 0008423
2012-03-11 21:24 Kloot Status feedback => closed
2012-03-11 21:24 Kloot Resolution reopened => no change required
+Issue History