this post was submitted on 02 Dec 2025
193 points (99.0% liked)

Games

22223 readers
300 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 2 years ago
MODERATORS
nanoUFO@sh.itjust.works
193
HELLDIVERS 2 Tech Blog #2 - Opt-in install size reduction beta (from 154Gb to 23Gb) (store.steampowered.com)
submitted 5 days ago* (last edited 5 days ago) by inlandempire@jlai.lu to c/games@sh.itjust.works
85 comments fedilink hide all child comments
 

*We have followed through on our plans and made small reductions in the PC installation size over the last few patches while still adding new content. While this was a good start, our short term fixes have not been enough to keep up with all of the new content in the latest patch. The longer term goal has always been to bring the PC installation size much closer in line with the console versions. We are happy to report that, thanks to our partners at Nixxes, we have reached that goal much sooner than expected._

By completely de-duplicating our data, we were able to reduce the PC installation size from ~154GB to ~23GB, for a total saving of ~131GB (~85%). We have completed several rounds of internal QA and are ready to roll this out to early adopters as a public technical beta. Our testing shows that for the small percentage of players still using mechanical hard disk drives, mission loading times have only increased by a few seconds in the worst cases. This is live NOW!*

you are viewing a single comment's thread
view the rest of the comments
[–] kadup@lemmy.world 1 points 4 days ago (1 children)

Now replace a badly modified version of FSR 1 with support for FSR 3.x, 4.x and DLSS, as we are in 2025 please.

[–] carrylex@lemmy.world 2 points 4 days ago (2 children)

Fuck fake frames. All my homies use real frames.

[–] AlexisFR@jlai.lu 3 points 4 days ago

They are still better anti aliasing than TAA.

[–] kadup@lemmy.world 1 points 4 days ago (1 children)

I never said anything about frame generation.

[–] carrylex@lemmy.world 0 points 3 days ago* (last edited 3 days ago) (1 children)

Then what the heck do you think FSR3+ and DLSS use?

[–] kadup@lemmy.world 3 points 3 days ago* (last edited 3 days ago) (1 children)

You're way too rude for somebody this unaware of the topic at hand.

FSR and DLSS are at their core temporal upscalers. They take motion vectors, subpixel samples from jittering objects, and a low resolution scene, and using shaders for FSR or AI models for DLSS, interpolate the existing pixels to fill the entire target resolution. That's it. This is not frame generation, and they don't use anything, whatever you meant by that.

You can then, on top of the regular upscaling, enable frame generation to enable an entirely different path that holds frames in the buffer and creates intermediary frames. Those are the fake frames you complained about.

One can use both FSR and DLSS without no frame generation whatsoever, and both were originally created without any type of frame generation to begin with. At the present, Helldivers already uses FSR without frame generation - just for upscaling - but it's FSR 1.0 (previously called FidelityFX), a matrix based spatial scalar that only looks at one central pixel and tries to apply weights to determine how to fill in the neighbors. This looks horrendous. FSR 2.x and onwards, and DLSS, use the full temporal mechanism I described.

That's "what the heck" I think DLSS does.

[–] carrylex@lemmy.world 0 points 3 days ago (1 children)

[–] kadup@lemmy.world 2 points 3 days ago

Glad to see you recognize you were completely wrong and had to shift the conversation to a different topic.