View Issue Details

IDProjectCategoryView StatusLast Update
0002527Spring engineGeneralpublic2012-11-17 19:59
Reportersmoth Assigned TojK  
PrioritynormalSeverityminorReproducibilityhave not tried
Status resolvedResolutionfixed 
Product Version0.82.7+git 
Summary0002527: feature weapon collision is broken.
DescriptionGunmetal harbor.
Dom
target one of the water towers.

projectiles occasionally go right through a building. moving can have it actually retarget it from a different direction but yeah broken.

The other issue I had was projectiles randomly would go through even the large hangars.
TagsNo tags attached.
Attached Files
screen00094.png (Attachment missing)
screen00095.png (Attachment missing)
Checked infolog.txt for Errors

Activities

Kloot

2011-07-04 12:56

developer   ~0006902

None of the features in Gunmetal_Harbor_1.sd7/features/smoth/ have collisionVolumeTest=1 set.

http://springrts.com/wiki/Units-FeatureDefs#Collision_Volumes
http://springrts.com/wiki/Unit_collision_volumes#Fast_projectiles_passing_through_collision_volumes

(how people can still be unaware of this is beyond me)

smoth

2011-07-05 06:46

reporter   ~0006911

"The type of test used to detect collisions. Can be 0 (disc) or 1 (continuous). Use the latter for catching high speed projectiles which may otherwise 'skip through' small collision volumes, but beware of the increased performance cost. "

*SMALL COLLISION VOLUMES*

*INCREASED PERFORMANCE COST*

I am not unaware but I was under the impression that this is going to cost me even more fps AND it was for small features. Not something that is 7X11 or 2x2 which are not small persay. 2x2 is fairly average. Care to clarify a bit on why it should be on a 7X11? which is in the second shot?

jK

2011-07-05 15:30

developer   ~0006914

| (how people can still be unaware of this is beyond me)

It's really beyond me, why it wasn't created as a per-projectile property.
In particular a check if the to be check colvol is smaller than the projectile's movement speed to automatically switch to the continuous check ...

FLOZi

2011-07-05 17:39

reporter   ~0006920

@Smoth; That explanation is my explanation and is a somewhat simplified abstraction of the problem

smoth

2011-07-06 02:26

reporter   ~0006934

that is what I have on the wiki so it is all I have to go by. I didn't want to add collisionvoltest on all my features for fear it would drastically hurt fps.

user744

2011-07-06 02:52

  ~0006935

Last edited: 2011-07-06 02:53

just try it out, maybe it does not matter so much after all.
And if it does, myth confirmed.

The second screnn looks strange though, that looks like it should hit even without collisionVolumeTest=1
Maybe usefull to know if it happens in current too or just test version?

Issue History

Date Modified Username Field Change
2011-07-04 01:28 smoth New Issue
2011-07-04 01:28 smoth File Added: screen00094.png
2011-07-04 01:28 smoth Graphics Card => unknown
2011-07-04 01:29 smoth File Added: screen00095.png
2011-07-04 12:56 Kloot Note Added: 0006902
2011-07-04 12:56 Kloot Status new => closed
2011-07-04 12:56 Kloot Resolution open => no change required
2011-07-05 06:46 smoth Note Added: 0006911
2011-07-05 06:46 smoth Status closed => feedback
2011-07-05 06:46 smoth Resolution no change required => reopened
2011-07-05 15:30 jK Note Added: 0006914
2011-07-05 17:39 FLOZi Note Added: 0006920
2011-07-06 02:26 smoth Note Added: 0006934
2011-07-06 02:52 user744 Note Added: 0006935
2011-07-06 02:53 user744 Note Edited: 0006935
2012-11-17 19:59 jK Status feedback => resolved
2012-11-17 19:59 jK Resolution reopened => fixed
2012-11-17 19:59 jK Assigned To => jK