this post was submitted on 27 Mar 2024
623 points (97.7% liked)

Games

32960 readers
1906 users here now

Welcome to the largest gaming community on Lemmy! Discussion for all kinds of games. Video games, tabletop games, card games etc.

Weekly Threads:

What Are You Playing?

The Weekly Discussion Topic

Rules:

  1. Submissions have to be related to games

  2. No bigotry or harassment, be civil

  3. No excessive self-promotion

  4. Stay on-topic; no memes, funny videos, giveaways, reposts, or low-effort posts

  5. Mark Spoilers and NSFW

  6. No linking to piracy

More information about the community rules can be found here.

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 9 months ago* (last edited 9 months ago)

My brother in christ, what the fuck do you think i’ve been describing then?

Algorithms that use the models/meshes/etc., and not the models/meshes data themselves. Algorithms take up allot less space on the hard drive.

What I see is that you don’t understand how procedural generation works.

I'm a computer programmer. I've written that kind of code before (gotta love some Perlin noise). /sigh

Also, you're not quoting me on that part, but someone else. I didn't make any mention about a 'Damaged Helmet in gitf format' (or anything else in that text you quoted).

As is today, how do you think planetary terrain is generated?

It mixes/matches models (that have meshes, etc.) like Lego pieces to assemble the landscapes/things. If you want more new/varied worlds, you need more models/meshes. The algorithms are not going to create them, its going to just assemble the ones that already exist as files on the hard drive.

Edit: Funny enough, I'm currently downloading the update, all 7.48GB of it. The whole game takes up 14.69GB on my hard disk. I'm going to bet most of the update is the new stations look/variety, and not the logic code for mix-and-matching ship parts.