Games

16796 readers

573 users here now

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

Posts.

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

Comments.

No personal attacks.
Obey instance rules.
No low effort comments(one or two words, emoji etc..)
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

nanoUFO@sh.itjust.works

361

No Man's Sky dev pulls out all the stops to fix a player's buggy save with 611 hours of playtime at risk: 'I promise to hawk that bug and fix it' (www.pcgamer.com)

submitted 3 weeks ago by misk@sopuli.xyz to c/games@sh.itjust.works

61 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] stringere@sh.itjust.works 6 points 3 weeks ago (1 children)

At least when you're wrong about something you're willing to keep doubling down and not see how!

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

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."

So where is the save being sent back for an engine issue….? This specific fix had nothing to do with fixing a specific save issue, they got sent a save that HAD the issue, and used that to fix a generic issue. Why is everyone going on about this being a save fix?