Page MenuHomeFeedback Tracker

RAK appears to be firing in inventory of dead player
Closed, ResolvedPublic

Description

Yesterday while playing in the NWAF I encountered a player shooting at me with an SKS ("Terminus, Sanctuary for all" server I Believe). When he ran out of SKS ammo he apparently tried to switch to a RAK that he had in his backpack and was (I imagine furiously) attempting to fire it (I believe spray it) as I killed him with my AKM. We were both firing automatically at the time I killed him. When I checked his corpse, the gun in his backpack appeared to be firing, and when I moused over the item it had the same image of the gun firing. (http://imgur.com/p4PSTwl).

The only other relevant information I can recall is that he was crouched near a tree at the time he died. I can identify the location on the map if that is helpful.

Details

Legacy ID
1091509048
Severity
None
Resolution
Unable To Duplicate
Reproducibility
Have Not Tried
Steps To Reproduce

Have not tried, pretty unique set of steps, but I imagine it would look like this:

  1. player 1 with RAK in inventory one way or another tries to pull out the RAK and start shooting while crouched
  2. Player 2 kills player 1
  3. Player 2 checks the contents of player 1

I imagine I Must have just killed him at the perfect timing as he was firing the gun. so to the game it was in his hands, as he died went back into his inventory but was still firing on the frame that happened?

Additional Information

Seems to be pretty popular, so people might try and recreate it.

Event Timeline

typicaljs edited Additional Information. (Show Details)
typicaljs set Category to category:weapons.
typicaljs set Reproducibility to Have Not Tried.
typicaljs set Severity to None.
typicaljs set Resolution to Unable To Duplicate.
typicaljs set Legacy ID to 1091509048.May 8 2016, 11:00 PM
Geez added a comment.Jun 17 2015, 11:58 AM

Hello typicaljs and thank you for the report.
We have tested this thoroughly but unfortunately we were unable to reproduce the issue you have described. This has been most likely caused by the various desync issues, which we are aware of and they have been scheduled for a fix.
Regards,
Geez