By using this site, you agree to our Privacy Policy and our Terms of Use. Close
Otter said:
DonFerrari said:

Minor drops that aren't replicable are exactly what you would expect of a bug. Something that is present 100% time, for 100% people for 100% of a mode isn't a bug it is a tradeoff choice. Do you that curiously the time they though was a bug were the ones that Xbox was doing worse? And the only one that have been positive confirm of bug (doesn't always occur) is on the PS5 and they acknowledged that later. But on video you would thought Xbox version runs much better (and on Shikamaru table the impression is even worse) with PS5 hiccups being expected, on the other hand similar situation shoes reversed they will do different. But I feel like I'm restating myself. Even more as I already said I don't think they are biased, but struggling with finding explanations to their expectations not being met.

shikamaru317 said:

I'm not surprised really, this game was rushed out. Originally CoD 2020 was supposed to be a Sledgehammer game; since Sledgehammer's last CoD was WWII in 2017, it was Sledgehammers turn on the CoD studio rotation. However, there was some kind of falling out over at Sledgehammer with the founders leaving and then disagreements between Sledgehammer and Raven (who was co-developing it with them) on the direction of the game, so 1 year into development Activision took Sledgehammer off the project and Treyarch got brought in to convert their planned 2021 CoD multiplayer into multiplayer for 2020 CoD, with Raven put in charge of the Cold War campaign. So basically Cold War got 2 years of development, like CoD 1 through Ghosts, instead of 3 years of development like CoD Advanced Warfare through Modern Warfare 2019. And CoD 2021 will presumably have 2 years of development as well now because of the upheaval to the studio rotation, though we don't know yet if CoD 2021 will be Infinity Ward or Sledgehammer developed.

So a game that potentially had much more rushed development and was favored to PS5 got a virtual tie, how does that fit with the other games that had preference to Xbox but run worse?

Well Series S just had its shadows patched in so, so I think bugs can be present 100% of the time (obviously DF didn't know this was the case). If not a bug than an error. Trade off implies something was done to salvage performance this is what they assumed off the missing shadows (even if RT Is still missing from XBSS), error/bug means human mistake in the code which is impacting the experience unnecessarily or delivering something that was not intended. You'll be surprised that sometimes the first time devs are finding out about issues is when DF or other sites contact them. DF makes their money off comparisons, whereas developers are super time constraint working on 8 versions at the same time and can easily miss this stuff 

The last note on the fps topic, if they never restarted from the checkpoint it could be human error that Digital Foundary missed it. I think you're going on the presumption that they were already aware that it could be eliminated by restarting but just didn't report it. The tweet where John acknowledges it as a bug was today only, but the video was of course made before that tweet was sent.

And no I don't find it curious that they've often looked at the Series X versions for having bugs. Again if you just look at the examples its clear why they thought there was something up. AC, literally screen tearing so much its hard for people without VRR to enjoy and features a camera glitch which makes the fps looks unstable when it is. Dirt5, has LOD which are multitudes worse than PS5 despite us understanding them to be comparable machines where the difference should be fps or resolution. DMC, dropping 50frames below the PS5 version during the 120fps mode....

COD, runs almost perfectly, just dips a bit here and there during setpieces. This is not like the others lol. By your logic they would have claimed the Series X running worse at 120fps was a bug but they didn't. I don't see the bias but I'll leave this thread here.

I wouldn't be surprised that something escape devs and is seem by users or crash reports, etc. That is nature of bugs. But Compared to the time QA test the games compared to the time DF had with it something as obvious as the whole mode not having the right level of assets seem very odd to miss.

Nope not saying they already knew it was a problem, what I'm saying is that for the drops in Xbox versions they assumed it was a bug (almost all of them), while for this case on PS5 they passed over it accepting as HW limitation.

If you don't find it curious that let's say 100% cases of problems on Xbox (even if repeatable and present the whole time) are supposedly bugs, but 0% on PS5 are expected to be bugs ok.

You know what they said about Series X running worse at 120fps? VRR will cover for it, it isn't much of an issue, and "I don't know why that is happening".

duduspace11 "Well, since we are estimating costs, Pokemon Red/Blue did cost Nintendo about $50m to make back in 1996"

Mr Puggsly: "Hehe, I said good profit. You said big profit. Frankly, not losing money is what I meant by good. Don't get hung up on semantics"

Azzanation: "PS5 wouldn't sold out at launch without scalpers."