Wow, thanks for the helpful post. How about instead of trying to up your post count, you don't reply unless you have something useful to say? If an Ubi rep is willing to try and help me on this, I'm gonna try their suggestions. Back off.
Printable View
how to workaround this is traveling to the location until you can move.
Still nothing?
----
Help? Try update your graphics driver :D (this is what Ubi says) or create a ticket, maybe they'll send you something usefull.
This is how this forum works: find a way yourself and then write here how did you fixed it, Ubi reply with "Glad it works!".
Just read any other topics.
----
Spend your time better, because last year I tried to report bugs (places where a bug is, pictures, videos, and other things) here and I wanted to fix the bugs. And Ubi? Gave me ban.
report bug == ban
Hello everyone.
I'd like to offer you as much information as possible regarding this issue, as I see there is a lot of uncertainty with what happened.
We raised this issue to our dev team with as much information as possible and despite everyone's strong efforts, we were not able to reproduce the issue in our test environment. Being unable to reproduce the issue usually means we are unable to understand the root cause, and therefore find the source.
The video provided by xHITMANx777x was heavily reviewed and our team attempted to replicate the exact same scenario, with the most specific details.
At this moment in time we don't have a fix. The only way to move forward is if we can provide our production team with new information.
I appreciate this has been affecting you all for a long time. If anyone is able to provide an up to date video of their experience, perhaps we will have new information to explore.
My post does not yet offer a solution but I hope it will help ease your mind that we absolutely were investigating this issue.
@Ubi-Raziel: I really want to believe Ubi dev team tried to reproduce the bug. If still nothing (really weird), the bug appears mostly when you're returning from expeditions and only in coop and for host (server) player. Second player doesn't have this problem. The bug also never appeared in SP.
Also, the bug doesn't appear always, but like 3 out of 10. I think you need to play at least 45 mins.
And yes, the bug IS there.
EDIT:
If your dev team still can't find the reason, then create a something like debug output from the engine. Players which will experience the bug will send you the debug output.
RealArmanIII: Thanks for that feedback, RealArmanIII! We can definitely reach out to our game development team with that information. I can assure you that as Ubi-Raziel stated, we are looking into this at this time. :)
@Ubi-Karl: Thank you for your reply. Can I expect the fix soon?
We can't promise a time frame unfortunately because it relies on another team. As soon as we hear anything we'll let you know.
I'm consistently having the same issue, and at this point the game, which I specifically bought to play multiplayer, is unplayable for me. I regret spending the money on it, and at this point am just trying to make it worth anything.
Is there any solution, or even update, to this issue yet?