Open wzdev-ci opened 13 years ago
Kreuvf commented
Have you tried modding the Ripple rocket damage (can be seen in-game) to make sure that your changes are actually applied?
Reg312 uploaded file weapons.txt
(32.6 KiB)
Reg312 commented
i sure my changes aplied see movie how ripples rockets strike with flight speed = 50 close distance = flight speed is very slow any other distance = flight speed is very fast
Kreuvf commented
Interesting and thank you very much. To me it looks like flight speed is set to some constant for indirect shots while for direct shots the specified value is used.
Iluvalar commented
When there is no possible balistic angle for the shot because of the distance, the angle turn at 30 degree and the speed is adjusted instead. I dont see any quick solution to that except maybe tweaking the gravity instead ? Assuming that if the rocket is slower then possible for a mortar, it's because it have some way to flight and cancel some gravity ?
Stratadrake commented
This one goes all the way back to original retail: For indirect-fire weapons, a slow flight speed only shows its effect at short range, long range ballistic trajectories use a fixed speed.
It is safe to assume that rockets can have a slower ballistic flight speed because they are self-propelled projectiles (where mortar shells are not). But in the name of tweakability perhaps the weapon's specified flight speed should always be obeyed, even if it means the trajectory has to be calculated using a reduced gravity.
type_bug
| by Reg312while playing with stat parameters i discovered that "Flight Speed" not affects projectile flight speed for weapon "Ripple rockets"
but "Flight Speed" works only on short distance 0 - 6 tiles
ripple rockets with "Flight Speed" setted to 100 have same projectile speed as ripples with default 1500 flight speed in sum WZ have very precise artillery
in original WZ campaign units have good chances to avoid artillery while fast moves, but in multiplayer ripples rockets strike with 100% chance to hit May be also here some accuracy bug or something like that
Issue migrated from trac:2872 at 2022-04-16 08:34:53 -0700