Page MenuHomeFeedback Tracker

mxm rifle not working after exiting the water, might be all normal rifles.
Closed, ResolvedPublic


Jumped in the water with an MXM sniper rifle, exited the water, ran around on the dock and it will not let me fire or change weapon selection on the rifle.
Have to swap to pistol which works fine, swap back to rifle which then works fine.
Game isn't registering when you leave the water and are able to fire your weapon again.


Legacy ID
Unable To Duplicate
Swimming and Diving
Steps To Reproduce

ready non diving rifle, jump in water, come out try to shoot rifle.
swap to handgun, swap back to rifle.

Event Timeline

Amedeus edited Steps To Reproduce. (Show Details)Mar 6 2013, 1:40 AM
Amedeus edited Additional Information. (Show Details)
Amedeus set Category to Swimming and Diving.
Amedeus set Reproducibility to Always.
Amedeus set Severity to Tweak.
Amedeus set Resolution to Unable To Duplicate.
Amedeus set Legacy ID to 167838777.May 7 2016, 10:42 AM
Varick added a subscriber: Varick.May 7 2016, 10:42 AM

It would be interesting if there was a wait time to use a wet weapon. I think the HK416 can be dunked and used almost immediately after a good shake.

Would also be neat to see/hear suppressors being more effective after being wet.

Ok so I tried this out myself. I used an MX and went for a swim. Everything worked fine.
Then I tried it again but this time in a wetsuit and with a Katiba. I couldn't bring it up to aim or fire the rifle. It was all I had at the time, so I dropped it to the ground. It worked again after I picked it up.

cevune added a subscriber: cevune.May 7 2016, 10:42 AM

I've had the same issue with every weapon thus far (including the pistol). The scenario goes like this: 1)have weapon out 2) enter water 3) exit water 4) weapon won't fire.
as has been listed here, there are several work arounds to this problem (ie dropping/re-equipping, switching weapons, and personally using the F key, which i believe is default firing mode, also made the weapon operable again.) however, due to the nature of the work arounds, I do believe this is a bug and not a feature. I just say this to clarify on the nature of this and related issues and that it likely isn't an intentional occurrence

Khan added a comment.Apr 22 2013, 1:06 PM

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.

Unable to reproduce in the latest dev build. Closing due to lack of response in a long time.

If this issue is still reproducable for you, please create a new ticket for it.