SchmidtGenetics

joined 9 months ago
[–] SchmidtGenetics@lemmy.world -1 points 3 weeks ago* (last edited 3 weeks ago)

As the article specifies, the save was to help with an issue, it wasn’t “personal assistance” it just helped the person as well.

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

Read. The. Damn. Article. Instead oof a single tweet taken out of context.

The devs posting to social media is for clout and viral marketing. Why else would they post about it their own bug fix…?

[–] 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?

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

I read what you said, and you still haven’t read the article with the argument you keep going on about.

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 how is this anything about using personal assistance with a save…? They used the save to fix a generic bug, which is what I was originally talking about until you derailed the topic with your bullshit.

So again, did you ever. Read the bloody article…? Because nothing you’ve talked about is related to it…

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

The dev who the article was about…? Who else would “they” be in this context?

So they posted to social media for clout? That’s an even worse take.

And no it was a specific dev… did you even read the article?

. As No Man's Sky engine programmer Martin Griffiths details over on X

[–] 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.

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

No, but they tweeted what they did, it didn’t have to made public by the dev, but they obviously did it for the viral marketing, and then an article picks it up and here we are. Someone is being accused of saying an article is commissioned lmfao.

If every dev that did this tweeted about it, yeah you would hear about it more, but most devs have better things to do than get some stupid marketing for things almost every dev already does.

So I ask you, why else would someone tweet about a mundane thing like fixing a bug?

view more: next ›