It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
I have the XB1 version of The Witcher 3 and after a cutscene during the "Kings Gambit" quest it goes to a blank loading screen that never loads, even after 4 or 5 hours. It's frustrating because I can't continue with the main quests until Kings Gambit is completed, it inter-twines with "The Isle of Mists" main quest. A friend of mine said I can skip it and continue with the main quests anyways but I'll loose a good chunk of the story by doing so I'm afraid.

When are the next patches and will they fix this problem? Or do I need to start over?

I can't even get on the witcher 3 website in support to look for problems, every time I try it shoots a "504 Gateway Time-out" at me. This is the only problem I have experienced while playing The Witcher 3: Wild Hunt everything else runs great, I'm just stuck at an endless loading screen hoping that they will patch this problem so I can go back to enjoying the game.
This question / problem has been solved by TBreaker20image
avatar
theejeeves: I have the XB1 version of The Witcher 3 and after a cutscene during the "Kings Gambit" quest it goes to a blank loading screen that never loads, even after 4 or 5 hours. It's frustrating because I can't continue with the main quests until Kings Gambit is completed, it inter-twines with "The Isle of Mists" main quest. A friend of mine said I can skip it and continue with the main quests anyways but I'll loose a good chunk of the story by doing so I'm afraid.

When are the next patches and will they fix this problem? Or do I need to start over?

I can't even get on the witcher 3 website in support to look for problems, every time I try it shoots a "504 Gateway Time-out" at me. This is the only problem I have experienced while playing The Witcher 3: Wild Hunt everything else runs great, I'm just stuck at an endless loading screen hoping that they will patch this problem so I can go back to enjoying the game.
This bug is expected to be fixed in the patch 1.05, you can try to dodge it somehow or wait until this patch is released :)