2025-08-25 17:25 CEST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0000335Spring engineGeneralpublic2013-03-22 16:34
ReporterKDR_11k 
Assigned To 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
Product Version 
Target VersionFixed in Version 
Summary0000335: Disintegrator weapon does not aim correctly
DescriptionWhen a weapon is a disintegrator the unit firing it will ignore terrain in its path even when the weapon does not have noexplode set. Since a weapon is automatically a disintegrator when it is fired by the dgun command that makes using the dgun command for single-shot weapons that aren't supposed to behave like TA dguns difficult. Also the dgun will not be fired if the target is outside of the dgun range but inside the range of another weapon mounted on the unit.

Furthermore, non-disintegrator noexplode weapons do not ignore terrain.

My suggestion would be to make the aiming through terrain specific to noexplode weapons instead of disintegrator weapons and possibly also unbundle the disintegrator weapontype and dgun command so non-disintegrator weapons can be bound to that command.

Ideally we'd get a weapontype command that overrides the engine's attempts to guess what weapon type a weapon has. That algorithm is just a hack to maintain compatibility with OTA data anyway.

Marked as minor severity since I don't think many people use non-noexplode dguns in their mods yet so it doesn't affect most mods though maybe this bug is the reason it doesn't...
Additional InformationReproduction: The mod Dozerz (http://www.unknown-files.net/index.php?page=browse&dlid=1994) uses dguns that aren't noexplode, try using the dgun command on rough terrain or behind hills. Also try using it at the unit's maximum range (the dgun range is about 75% of the maximum range).
TagsNo tags attached.
Checked infolog.txt for Errors
Attached Files

-Relationships
+Relationships

-Notes
There are no notes attached to this issue.
+Notes

-Issue History
Date Modified Username Field Change
2006-12-06 15:11 KDR_11k New Issue
2013-03-22 16:34 Kloot Status new => closed
2013-03-22 16:34 Kloot Resolution open => fixed
+Issue History