2024-04-25 08:57 CEST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0004350Spring engineGeneralpublic2014-05-10 08:59
ReporterGoogle_Frog 
Assigned ToKloot 
PrioritynormalSeverityminorReproducibilityalways
StatusresolvedResolutionfixed 
Product Version96.0 
Target VersionFixed in Version 
Summary0004350: LaserCannons act as if they have burnblow
DescriptionLaserCannons in 96.0 fade out as soon as they reach the range of their target instead of fading at max range. This is undesirable because it affects inaccurate or noExplode LaserCannons. In Zero-K we have a shotgun type weapon implemented with LaserCannon as well as a flamethrower weapon. For these weapons the ability for the projectiles to fly further than their target is important. The behaviour works in 95.0.

This change appears to be responsible: https://github.com/spring/spring/commit/dfb17e7239cbd0ef3846f7d7d115834dc834f946

The projectile time to live is set to the minimum required to reach their target. The best fix would be to give LaserCannons the burnblow tag with the difference being whether the minimum or maximum time to live is taken.
TagsNo tags attached.
Checked infolog.txt for Errors
Attached Files

-Relationships
+Relationships

-Notes

~0012975

user744

Did you try hardStop & fallOffRate?
http://springrts.com/wiki/Gamedev:WeaponDefs#LaserCannon
Not sure if they are just for visual but also not sure if you mean only visual.

~0012976

Google_Frog (reporter)

Last edited: 2014-03-31 03:54

View 2 revisions

I am not referring to visuals. Anyway, the wiki says that those tags are for behaviour when the projectile hits max range. I have projectiles disappearing or fading out much before max range. I have tested whether the effect is purely visual and it is not, the projectile actually disappears. This is easy to test with a noExplode LaserCannon and two targets in a line.

~0012978

Google_Frog (reporter)

Lasers now obey burnblow so they are back to working for my purposes. Thanks.

~0013047

Google_Frog (reporter)

The issue has been resolved. This ticket can be closed.

~0013049

cleanrock (reporter)

Probably fixed by
https://github.com/spring/spring/commit/8e77afb
+Notes

-Issue History
Date Modified Username Field Change
2014-03-30 08:20 Google_Frog New Issue
2014-03-30 18:30 user744 Note Added: 0012975
2014-03-31 03:53 Google_Frog Note Added: 0012976
2014-03-31 03:54 Google_Frog Note Edited: 0012976 View Revisions
2014-04-01 14:10 Google_Frog Note Added: 0012978
2014-05-10 08:05 Google_Frog Note Added: 0013047
2014-05-10 08:59 cleanrock Note Added: 0013049
2014-05-10 08:59 cleanrock Status new => resolved
2014-05-10 08:59 cleanrock Resolution open => fixed
2014-05-10 08:59 cleanrock Assigned To => Kloot
+Issue History