Page MenuHomeFeedback Tracker

attaching a cone on a helicopter causes explosion after time
Closed, ResolvedPublic


After attaching a street cone to a helicopter and start flying, everything except of the "ARTQ" gets destroyed after a random time (max. 5-7 min.).


Legacy ID
No Bug
Game Physics
Steps To Reproduce

Attach per "attachTo" a street cone to a little bird (not tested with other objects/helis, position of the cone is not important) and start flying around. Do a few sharp curves and the heli should get destroyed.

Event Timeline

Naqual edited Steps To Reproduce. (Show Details)Mar 7 2013, 11:47 AM
Naqual edited Additional Information. (Show Details)
Naqual set Category to Game Physics.
Naqual set Reproducibility to Always.
Naqual set Severity to Minor.
Naqual set Resolution to No Bug.
Naqual set Legacy ID to 2487404557.May 7 2016, 11:23 AM

and.... why should you do that ? o_O

Naqual added a subscriber: Naqual.May 7 2016, 11:23 AM

In my case: Capture the Cone :P
But its likely that other objects behave in the same way and the community is very creative in such things ;)

CtC !

New game mode xD

not a bug try this in the init line of the helicopter will fix it right up for you can use it on player or any type of unit

this allowDamage false;

ps:it will make the Helicopter invincible hope that will still work with your game mode

Enjoy :D

oh i just remembered when the helicopters hit the ground they may still blow up

Naqual added a comment.Mar 7 2013, 4:43 PM

Thanks, this works for now. But its still weird, that the Helicopter explode only when i attach special objects. For Example, when i attach a roadbarrier, nothing happens to the chopper.

may have something to do with the way the new physics engine works my theory is its calculating the damage as if you were hitting the cone at that speed as if the cone was at standstill however my little line of code is a good enough fix for what you want hope you enjoy look forward to seeing your game mode on the forums :D

Thales added a subscriber: Thales.May 7 2016, 11:23 AM

We are very sorry, this issue was closed as no-bug.