Seconded on this problem, also happens after fast traveling.Originally Posted by LtGeneralAndrew Go to original post
Oh my god, yes. All the time, hence why I never use C4 or grenades anymore.
I cant do that. Its a game breaking bug for me right now. I'll also get stuck in a grenade throwing animation. Its ridiculous. This game was running great for days and all of a sudden I hit this wall.Originally Posted by LtCommander417 Go to original post
Also having the same problem. Unlike the video example posted in the first page of this thread, my GL's projectiles are going out, but will just ping off whatever i shoot it at, and some random amount of time later (between 5-30 seconds) all explosives used will detonate simultaneously, not necessarily limited to the GL. C4, grenades, and other explosives used will also detonate at the same time. After that, explosives will all work correctly for a time. It seems to happen after traveling various distances, like it's trying to load in the ability for explosives to explode.
I run a replay buffer with OBS so I even got an action shot of not only the bug happening, but of how it screws me over when it happens.
https://www.youtube.com/watch?v=S-2dBcDNMt8
I've provided proof of that bug and other bugs existence in the following video several times.Originally Posted by Ubi-Talos Go to original post
Please take your time and go through this video ubisoft.
I made it specifically so you guys could fix the damn game.
Not so you guys could ignore it.
And no, it's NOT the game files that are broken.
It's fps related the grenade issue, proof is in the video.
You guys locked the physics to frame rate count and when it's not in balance it breaks.
That's what's happening.
Hell I'm not even educated to use C++ and I understand this, should be damn obvious this would happen doing it the way you guys did it.
Again, please WATCH the video.
Reading through the thread I had the suspicion that the issue was similar if not exactly the same as the fallout/elderscrolls issue with physics being tied to the framerate and anything over a set limit breaks thingsOriginally Posted by Revixy Go to original post
Sure enough it seems more and more likely to be the case, an is a massive oversight if it is, and should have been avoided considering we had larger titles make this error to learn from. I guess that's what happens when you dont consider anything other than locked framerates outside of console development
I know right? *sigh*.Originally Posted by TeaVice Go to original post
had this same problem lastnight on my drone
click - camera zooms out - 10secs later explodes