this post was submitted on 21 Aug 2024
52 points (98.1% liked)

PC Gaming

8765 readers
585 users here now

For PC gaming news and discussion. PCGamingWiki

Rules:

  1. Be Respectful.
  2. No Spam or Porn.
  3. No Advertising.
  4. No Memes.
  5. No Tech Support.
  6. No questions about buying/building computers.
  7. No game suggestions, friend requests, surveys, or begging.
  8. No Let's Plays, streams, highlight reels/montages, random videos or shorts.
  9. No off-topic posts/comments, within reason.
  10. Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)

founded 2 years ago
MODERATORS
top 7 comments
sorted by: hot top controversial new old
[–] [email protected] 20 points 3 months ago

translation: we did test it, but we didnt listen to any feedback after we decided to add mouse acceleration and combine unrelated keybinds

[–] halcyoncmdr 20 points 3 months ago

I'll believe it when I see it. These claims always end up being full of shit somehow. 190,000 of those hours will have been the tutorial area or some shit.

[–] scrion 11 points 3 months ago (1 children)

At 7h / day of just testing, 200k hours amount to approximately 110 years, given 260 working days per year.

Veilguard has been in development for around 9 years, so thats about 12 "years of testing per year", so pretty much at least 12 people doing nothing else but testing (this assumes sane working conditions - hi EA!)

Given how long the game has been in development, what does that number even mean? How much of the stuff they wrote 9 years ago is still in place, given that players would expect the technological advancements available since 2015.

Also, it's supposed to be released end of October, I believe? Or has it been postponed even further (again)? Anyway, why would they claim something like that before release? That will probably backfire.

[–] Bimfred 5 points 3 months ago (2 children)

A lot of that time, if not the vast majority, is likely performance testing. That's trivial to automate and can be run across 100+ systems simultaneously.

[–] [email protected] 2 points 3 months ago

Yeah not 200k actual man-hours.

[–] scrion 2 points 3 months ago (1 children)

Yeah, that's the implication. Unfortunately, that is also misleading people into believing they might get a well-tested, nearly bug free game.

[–] Bimfred 1 points 3 months ago

Yep. And if they fail to deliver on the lofty expectations they've created here, the backlash is going to be epic. I don't want to root for their downfall, but.... Imma stock up on popcorn.