Page MenuHomeFeedback Tracker

V3S sinks into the ground
Closed, ResolvedPublic

Description

Drive a V3S reverse through a gate. The gate is like it doesn't exist, you can drive through. Then the V3S starts to vanish into the ground, it needs some seconds, then the V3S has fully disappeared. The driver is automatically dead. When you go to the V3S, while it is sinking, your legs are broken und you get thrown a meter backwards. You have to relog, or you can't walk or crouch(like you are dead, but you see all, and you are able to look into your inventory). Some seconds after the V3S has disappeared, the corpse of the driver spawns at the V3S position with ruined boots and pants. {F31656} {F31657}

Details

Legacy ID
3979778366
Severity
None
Resolution
Duplicate
Reproducibility
Have Not Tried

Event Timeline

Hanfbaum set Category to category:environment.May 2 2015, 11:54 AM
Hanfbaum set Reproducibility to Have Not Tried.
Hanfbaum set Severity to None.
Hanfbaum set Resolution to Duplicate.
Hanfbaum set Legacy ID to 3979778366.May 8 2016, 10:28 PM
Geez added a comment.May 11 2015, 3:41 PM

Hello Hanfbaum.
By any chance do you remember where did you encounter the issue? It would be appreciated if you could mark the location on some kind of map such as http://dayzdb.com/map.
Regards,
Geez

This happened to me as well at Gvozdno, I went cross country, Hit a SMALL wire fence, The truck just dived in to the ground and vanished leaving my dead body on the surface. Attached a picture showing details (Truck_Crash.jpg)
This happened a couple of weeks back on 0.55.

Hey Geez,
the crash happend to me above Nadezhino at a power transformer. See the location in the attached picture(crash.jpg).
I hope it helps you to fix it.
Regards,
Hanfbaum

Geez added a comment.May 18 2015, 1:32 PM

Hello Hanfbaum.
One more question, was the gate open or closed when you reverse drove your v3s into it?
Regards,
Geez

Hey Geez,
the gate was open.
Regards,
Hanfbaum

Geez added a comment.May 22 2015, 10:37 AM

Hello Hanfbaum.
In that case, that is an issue we are aware of (#0021575) and it has been scheduled for a fix.
Regards,
Geez