Why is it that no matter how long I make the range of a vulture's weapon, it still drives in way too close to attack it's enemies?
Not sure what you mean without seeing it myself, but my first guess would be Flingy deceleration.
you might want to tinker with the target aquisition range, just remember a 1 in that is the same as a 2 for weapon range.
The attack order would probably drive it into the target acquisition range, so you'd need to make that as big as the weapon range. If memory serves, that's the "Subunit Range" in DAT editors (Arsenal III to be specific, haven't looked around DATEdit yet).
"Target Acquisition Range" is called there.
And if it's 0, the weapon range is used... also "1 TAR" unit equals "2 Weapon range" units.
Nevermind guys. I'm just a little stupid and I guess range is smaller than I thought.
Someone can lock this now.
QUOTE(SubFocus @ Dec 10 2006, 05:12 PM)
Someone can lock this now.
[right][snapback]602116[/snapback][/right]
You could lock it too if you want
I think it has to do with flingy. The Vulture takes quite some time to stop, so that would explain the long delay. Does it attack while it's decelerating?
QUOTE(Lord_Agamemnon(MM) @ Dec 10 2006, 08:54 PM)
I think it has to do with flingy. The Vulture takes quite some time to stop, so that would explain the long delay. Does it attack while it's decelerating?
[right][snapback]602194[/snapback][/right]
Well... I uh changed the .flingy entry, and managed to get it to stop being annoying... Then I guess I just expected the range to be longer than it was.
Its not only for subunits DTBK its also for how far you see target units, unless set to 0 it will use the weapon range.
Then how does vulture microing work? You HAVE to use patrol instead of attack or else the vulture rans straight back to attack, is it because of the halt time?
QUOTE(Kookster @ Dec 10 2006, 11:59 PM)
Its not only for subunits DTBK its also for how far you see target units, unless set to 0 it will use the weapon range.
[right][snapback]602338[/snapback][/right]
I know what it's for, but in AR3 they call it subunit range. Glad the misnomer was corrected in DatEdit.QUOTE
I know what it's for, but in AR3 they call it subunit range. Glad the misnomer was corrected in DatEdit.
Well it didnt sound like you knew, just trying to be helpful