this post was submitted on 29 Oct 2024
357 points (96.6% liked)

Games

16758 readers
1003 users here now

Video game news oriented community. No NanoUFO is not a bot :)

Posts.

  1. News oriented content (general reviews, previews or retrospectives allowed).
  2. Broad discussion posts (preferably not only about a specific game).
  3. No humor/memes etc..
  4. No affiliate links
  5. No advertising.
  6. No clickbait, editorialized, sensational titles. State the game in question in the title. No all caps.
  7. No self promotion.
  8. No duplicate posts, newer post will be deleted unless there is more discussion in one of the posts.
  9. No politics.

Comments.

  1. No personal attacks.
  2. Obey instance rules.
  3. No low effort comments(one or two words, emoji etc..)
  4. Please use spoiler tags for spoilers.

My goal is just to have a community where people can go and see what new game news is out for the day and comment on it.

Other communities:

Beehaw.org gaming

Lemmy.ml gaming

lemmy.ca pcgaming

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] shani66@ani.social 1 points 3 weeks ago (1 children)

It's not fixing a bug, it's fixing a bug for a specific person.

[–] SchmidtGenetics@lemmy.world 0 points 3 weeks ago* (last edited 3 weeks ago)

Actually in this specific case it wasn’t even that…

The good news is that Griffiths managed to save the player's, uh, save. In a further update, he posts a video of the game running flicker-free in the same area on the same save. Per Griffiths, the problem was a "general engine bug/limit being reached," which means that his fix will "probably help other large bases that had this issue on Xbox."

The save helped with it, exactly like I’ve been saying this whole time.