I nosedived with a chopper in editor and right after i hit the ground my character got some damage but everything was fine,chopper was still flying.I tried it 5 more time and still happened.In multiplayer it was crashing most of the times,but it happened there like 20% of the times i tried it,but in editor it acts like nothing happened.I saw that it happened only if i crahed on the front side of the chopper,side and tail still damage it like they should
Description
Description
Details
Details
- Legacy ID
- 2039171101
- Severity
- Tweak
- Resolution
- Unable To Duplicate
- Reproducibility
- Always
- Category
- Game Physics
Steps To Reproduce
Get a chopper,fly high,aim down and fly straight on the ground.In editor it'll happen 90%
Additional Information
My frames were 60,so it wasnt lag issue
Event Timeline
Comment Actions
I also noticed this when i smashed into the ground on the showcase, chopper became unflyable, but did not blow up or kill me or any other passengers, I hit the ground atleast 150km/h nose plunged.
Felt way too forgiving too jump out alive and kicking from that.
Comment Actions
I was lobbing M203s or the equivalent at vehicles earlier. I discovered that while the Hunter and Ifrit always blow up after 3 direct grenade hits, the Ka-60 does not, so maybe it has more armour than it should. Not sure.
I wonder if the difference between the editor and multiplayer could be due to the Extended Armor difficulty option?
Comment Actions
i dont know how to edit my original post(if i can) but i can confirm that thats happening in multiplayer as well.Engine got shot at 200+ m ,chopper was busy freefalling,i tried to balance it a bit but i couldnt,and it landed on some rocks.It got some damage,but nothing important.And i got about 10-20 damage,like i crashed an atv on a wall
Comment Actions
Have been messing around with my friends for a bit and after getting crushed by nosedives from the sky about a million times i can confirm they always bounce and after 1 second the character dies and the helo explodes.
Comment Actions
We were not able to reproduce this bug.
Please let us know if you are still able to reproduce this issue in latest developement build.