Jeff said he's playing the PC version on the Bombcast. He's been having trouble getting the game to run well on his machine (especially with ray tracing on.)Hottest game of the season.
Giant Bombcast said it didn't run well on One X.
Also makes me legit worried about the per-game patches Sony is planning to adjust fan speed.
That's crazy to think that, with all the talk of the advanced cooling of the XSX, that a game can push it over its limits with a simple bug. I would have hoped the console would have been smarter than that to adjust at the system level to any CPU/GPU utilization.
Also makes me legit worried about the per-game patches Sony is planning to adjust fan speed. There's a lot that can go wrong there.
Sony to optimise the PS5 fan with online updates
Sony will optimise the PlayStation 5's internal fan with online updates, it's said.In an interview with 4Gamer.net (wit…www.eurogamer.net
Or maybe Xbox is doing the same thing, unadvertised, and just botched the fan speed patch?
honestly i'm not 100% sure, i think the article is unclear. i don't think sony or microsoft allow devs to crash games, undertale had to do something around that didn't it?Oh! What's in the OP reads like it's some kind of ingame mission that shuts down the console, Kojima style lol.
They better fix it fast.
Ubisoft has been developing games for the XB1 for seven years and should have QA measures to detect stuff like this.This is not a game bug. It's on Microsoft side.
Under no circumstances game code could overheat or brick consoles. It's either insufficient cooling or OS bug.
Seems crazy to me that six to eight hours in there's a critical bug like this and neither company's testing caught it.
it's not 100%, other reviewers have said they didn't encounter the issue.
To be fair, the console wouldn't turn back on for several hours after the shutdown occurred so the initial reaction was quite fair.
This is not a game bug. It's on Microsoft side.
Under no circumstances game code could overheat or brick consoles. It's either insufficient cooling or OS bug.
I think that's exactly this. If the game runs some kind of furmak code and the cooling is not designed for it.This is not a game bug. It's on Microsoft side.
Under no circumstances game code could overheat or brick consoles. It's either insufficient cooling or OS bug.
"The issue occurs around 6-8 hours into the main campaign (during a mission called - I kid you not - 404) upon which players are told their console is to shut down, as it's designed to, because of overheating - which it duly does."
After my first read I thought that the mission was designed to cause overheat xD
then why is Ubi the one patching it?This is not a game bug. It's on Microsoft side.
Under no circumstances game code could overheat or brick consoles. It's either insufficient cooling or OS bug.
1) that's bricking, even if temporary. And if it's getting so hot that it takes hours to cool down enough to work, that's incredibly bad, that's damage-the-console level overheating.So...
1) It doesn't brick your console, just knocks it out of commission for a bit.
2) It isn't something that happens 100% of the time.
3) It's likely on the OS side, not due to a bug with the game itself.
There's a lot of dangerous misinformation here that needs to be updated with this clarification.
Its not like every person on earth understands the right terminology for this kind of situation.Misleading tweet, the rest of the thread suggests the main story is glitched but they were able to dick around in the open world.
This is not a game bug. It's on Microsoft side.
Under no circumstances game code could overheat or brick consoles. It's either insufficient cooling or OS bug.