When a player has allowDamage false set setVelocity no longer functions.
Description
Description
Details
Details
- Legacy ID
- 2760432255
- Severity
- None
- Resolution
- Open
- Reproducibility
- Always
- Category
- Health System
Steps To Reproduce
Execute the following in the editor.
player allowDamage false; player setVelocity [0,0,100];
Player does not move.
Additional Information
Obviously this prevents the player from getting damaged via what I assume is some sort of simulation of g-effects, but it should by pass the damage handling, not the actual moving. This seems like the unintended consequences of this possible fix: http://feedback.arma3.com/view.php?id=13762
Event Timeline
Comment Actions
This is still an issue in 2.16.151618.
Furthermore, if you are in single player and the player has damage enabled, it will just apply damage immediately to the player, without actually applying the velocity.
Comment Actions
I believe it is related to the fact that the player is touching the ground at the time
try
player setPosWorld (getPosWorld player vectorAdd [0,0,0.1]); player setVelocity [0,0,100];
Comment Actions
I believe it is related to the fact that the player is touching the ground at the time
You are right, but the behaviour remains inconsistent.
Comment Actions
I think it makes sense engine-wise, as in "setting velocity kills the player, then ragdoll at this speed" whereas setting velocity on no-damage unit will not ragdoll it, therefore never throwing it in space.
I do not think it was related to a specific fix but was more or less always there. Still, worth asking for setVelocity to apply when touching the ground!