Page MenuHomeFeedback Tracker

V3S does not respawn repaired and unable to destory
Closed, ResolvedPublic


-I took the Wheels off a V3S so no one would steal it
-Logged back in 12 hours later and the Wheels I hid are gone and no new wheels respawned on the V3S
-Tested by taking a wheel off and hiding it in a tree on restart tire gone and no new tire on V3S
-Tried to shoot V3S to cause it to "blow up" so that it can respawn somewhere else and emptied 40 rounds of SKS ammo on it doing nothing
-Unable to remove random tires to make 1 complete truck {F32557} {F32558} {F32559} {F32560}


Legacy ID
Steps To Reproduce
  1. find V3S
  2. Remove tire from V3S and hide anywhere (does not disappear on restart if in barrel)
  3. Wait for server restart
  4. Server restart
  5. Hidden tire gone and V3S with missing tire
Additional Information

lastMPServerName="DayZ WA 2-14 (Public/3PP:ON/Persistence:ON) 129143 - Hosted by";

this is the server the truck is at

Event Timeline

tmasazo edited Steps To Reproduce. (Show Details)Sep 6 2015, 5:41 PM
tmasazo edited Additional Information. (Show Details)
tmasazo set Category to General.
tmasazo set Reproducibility to Always.
tmasazo set Severity to None.
tmasazo set Resolution to Duplicate.
tmasazo set Legacy ID to 3784421197.May 8 2016, 11:42 PM
edwin3 added a subscriber: edwin3.May 8 2016, 11:42 PM
  • tires despawn after 30 minutes
  • you cant destroy a v3s by shooting it
  • server restart does restore tires (just saw it an hour ago), maybe public problem (tho it wouldnt be a bug, as that kind of magic isnt really supposed to happen)
  • when tires had been restored by restart, you cant dismount them (known issue) - your experience proofs the respawn

i don't think trucks should respawn their tires upon restarts. but i believe that they do repair at restarts, im gonna test and if that is a thing im gonna file it on here.
if that't actually a thing, its a bad design decision, so what is the point of having tires spawn a an item in the loot system ?

Geez added a comment.Sep 7 2015, 4:03 PM

Hello tmasazo and thank you for the report.
This is an issue we are aware of (#0027038) and it has been scheduled for a fix.