Gamebreaking Bug with Crossbows, Bombs, etc.

+
I don't know how to solve it, but i may know why it happens: during a fight when i was in slow motion the game autosaved, then i died and when the game reloaded that autosave all the world was stuck in slow-motion. A sprint fixed that, but from then every time i get in slow motion, when the time accelerate Geralt runs at super speed. The saves before that infamous autosave are ok though, some of you had the same kind of autosave during slowmotion?

Edit: I just saw the video on youtube, can confirm
 
Last edited:
Is there any new info on a possible fix? It's ridiculous that a bug that has been in the game since release still isn't fixed after 5 patches. C'mon CDPR!
 
This is a funny bug! Based on the youtube vid provided above, the bug is activated when the game autosaves during an advanced slow-mo effect. Obviously, the gamestate saved is assuming Geralt to be moving at "standard slow-mo" speed when it's saving, resulting in that value being saved to the autosave file. Upon reloading, the computer multiplies the equivalent and opposite value to your movement speed so that you do not reload in slow motion...resulting in -- Super Speed!!!

I would try to trick the computer into doing those calculations again. Remove ANY skill that affects your speed. Find a quest trigger that will initiate an autosave. Aim with the crossbow and move forward to activate the autosave. This should put the computer through the same paces, and result in your top-speed being permanently lowered. By reloading and doing it again, it should result in the top speed being lowered again -- as well as overwriting the next corrupt auotsave file. Not sure what the magical formula to return to "real speed" would be, if it even works.

Ideally, turning off all autosaving should prevent this problem from ever occurring. Instead of a super-speed glitch, you'll wind up losing 2 hours of progress when you forget to save and a drowner sucker-punches you in the pancreas...
 
Last edited:
Yewah, but even if this is the problem then it's ridiculous you need to use a work-around for a problem that's been in there since the first version. The lack of response from CDPR on this issue is also frustrating to say the least. So again, can CDPR comment on this issue?
 
Not that quickly, obviously. Which means that it's probably a "little" thing that is deeply embedded in over a million of lines of code. I know the concept of "just fix it, already" makes sense to people that have never coded before, but that's not the reality -- especially not with a program as frickin' HUGE as Wild Hunt.

Patience. You know what causes it, so just take care to avoid it. It shouldn't affect any save file that is not that one particular autosave file. If it happens, just delete the most recent autosave (to be safe), reload from an earlier save, and take care not to let it happen again.
 
Not that quickly, obviously. Which means that it's probably a "little" thing that is deeply embedded in over a million of lines of code. I know the concept of "just fix it, already" makes sense to people that have never coded before, but that's not the reality -- especially not with a program as frickin' HUGE as Wild Hunt.

Patience. You know what causes it, so just take care to avoid it. It shouldn't affect any save file that is not that one particular autosave file. If it happens, just delete the most recent autosave (to be safe), reload from an earlier save, and take care not to let it happen again.

Yet I never talk about the idea of "just fix it". What I want is a response from the developers saying that they're looking into it or that they need more info or hell them asking for a savegame in which this state occurs. Really, any info they want on this I can help them with. I know how development works, I've been a developer myself when I was younger so please don't patronize me as someone that has never coded before.
 
Quick question, I used the superior dragon's dream and its kinda weak even less than that of a standard grapeshot's damage, is it bugged or is that how its meant to be?
 
Top Bottom