Load the Game Video Games, Reviews, Game News, Game Reviews & Game Video Trailers
At the moment, the Witcher 3: Wild Hunt is the talk of the town in the video gaming world, and with good justification. But, with over a million copies sold in the pre-order alone and patches currently only released on the PC version. I’m going to go on a long shot and assume there are a few of you out there that have come across one of these bugs on the Xbox One. There is one where you get locked on the “please wait” screen as you are starting the game up; the other prevents you from saving, if you reset the game you lose your progress and then the console will lock on the “please wait” screen. I’m ashamed to say I’ve spent more time than is reasonable waiting in the hope it would finally load. But, at the same time, that’s why I’m writing this.
With the weekend upon us, it may not be until sometime early next week that a patch rolls out for the console versions. So, until then here is a basic fix for the “please wait” screen of doom. As far as I can tell, both of these problems on the Xbox One are because of its cloud. But, I haven’t confirmed this. I’ve powered down after dying and been rewarded with the “please wait” screen on my next visit. As far as I can assume, the conflict seems to appear when my saves on the console try to jive with what’s in the cloud for my Xbox profile. It would be interesting to hear in the comments below if anyone that plays without internet has experienced similar problems.
THE FIX
With that said, if you want to prevent losing your save files in the future put the console into energy-saving mode. That should nullify the Xbox One’s “resume play” feature. The console will take longer to power up, but you shouldn’t lose your progress. If you’re currently staring at the “please wait” screen and can’t get rid of it, you’ll need to do a hard reset. To do so, power down your console, unplug it, wait for about 30 seconds, and then you’re good to go. This has fixed my problem on multiple occasions. CD Projekt Red is aware of this issue, but we may have to wait a little bit to receive an official fix. Until then, hopefully this helps.
