7 ms·

The sample project is 100Gb... I think I am going to need a new hard drive.

by nrjames 5y ago

TchoBeer 5y ago
What are they storing that the project is that big?
- jayd16 5y ago
  Source high res texture and model assets are quite large.
- hn8788 5y ago
  Graphics and audio are almost always the culprit for large sized games.
- Yizahi 5y ago
  It's a Chia mining plot and a few megabytes of demo project :)
defaultname 5y ago
100GB of rocks. I love the notion of their nanite engine and basically removing concern about LoD (though we've heard that pitch over many generations of engines), and it looks like they're finally improved on what was a terrible, clunky, extremely dated UI. What I don't love is that it leans into going crazy with assets. Already games are getting simply ridiculous, with new games hitting 300GB, many with an unending stream of enormous patches (looking at CoD Warzone). Instead of 100GB of rock meshes and textures, isn't there a benefit to procedural on-demand generation for stuff like this?
- Valgrim 5y ago
  In a way procedural generation can be tought of as extreme compression!
- ArkanExplorer 5y ago
  Since everything is just from megascans, it might make more sense to have 300gb of photorealistic assets stored on every next-gen device, and (UE5) games can just commonly load from them.
  - t0mbstone 5y ago
    Yeah, at a certain point, it probably makes sense to have a giant library of universal assets like rocks and grass and trees. There's no reason for each outdoor game to keep reinventing the universe.
    - contriban 5y ago
      So basically you’re asking for a node_modules for games!
      - typon 5y ago
        More like a /usr/lib shared across games on the same console
        incrudible 5y ago
        This is Unreal/C++ we're talking about. If the size of some field somewhere changes, your 300GB will need to be re-cooked...
    - Arwill 5y ago
      You can do that with Substance. Store images in a library and procedurally generate textures at runtime.
- Hammershaft 5y ago
  > isn't there a benefit to procedural on-demand generation for stuff like this? Like how demoscenes do it? I would think a huge trade off is the performance hit (and potential delay / popin) of the generation
- markjgx 5y ago
  "and it looks like they're finally improved on what was a terrible, clunky, extremely dated UI." doesn't hold true, it's mostly the same UI with a dark reskin. Certain editor hot paths have been reworked and that's about it. The editor is almost exclusively written in Slate, Epic's in-house Window framework/general GUI module. Slate's got a pretty interesting nested MACRO system. Most definitely not data-driven and pretty much as hard-coded as it gets, redesigning the editor for real would be difficult to say the least. In reality most experienced developers don't want a new design, they are happy with the workflow they have and I have to agree with them. I'm generally happy with the "if it ain't broke don't fix it" reskin decision.
- YinLuck- 5y ago
  Why is a 300GB game size 'ridiculous'? If you scale it for HDD cost and internet speeds over the past 20 years, I'd say game sizes are actually getting more efficient.
wronglebowski 5y ago
Can you compile and run the sample project and have something to walk around in?
- Animats 5y ago
  Yes. Your first compile may take an hour. It took about an hour and a half to get to a running sample game. You get all the source code for what goes on the target machine. It's here, on Github.[1] I tried to load the demo used for the UE5 videos, but that's only loadable through the "Epic Games Launcher", which is Windows-only. It's apparently possible to bash that into running under Wine, but I don't have time to make that work right now. For those who don't know what the deal is with Unreal Engine, there's no charge until you get the first million dollars in revenue. Then they take 5%. The nature of the game industry is that the top 50 or so titles generate almost all the revenue. So, rather than bothering with restrictive licenses for all the little guys, Epic just waits until a successful game starts getting media coverage and shows up on the industry charts, then has their billing department contact the game company. [1] https://github.com/EpicGames/UnrealEngine/releases/tag/5.0.0-early-access-1 https://github.com/EpicGames/UnrealEngine/releases/tag/5.0.0...
  - arunoda 5y ago
    You don't need the source code to make a executable version of the Game. And it won't take 1 hour on a decent machine.

The sample project is 100Gb... I think I am going to need a new hard drive.

TchoBeer 5y ago

What are they storing that the project is that big?

jayd16 5y ago
Source high res texture and model assets are quite large.
hn8788 5y ago
Graphics and audio are almost always the culprit for large sized games.
Yizahi 5y ago
It's a Chia mining plot and a few megabytes of demo project :)

defaultname 5y ago

100GB of rocks. I love the notion of their nanite engine and basically removing concern about LoD (though we've heard that pitch over many generations of engines), and it looks like they're finally improved on what was a terrible, clunky, extremely dated UI. What I don't love is that it leans into going crazy with assets. Already games are getting simply ridiculous, with new games hitting 300GB, many with an unending stream of enormous patches (looking at CoD Warzone). Instead of 100GB of rock meshes and textures, isn't there a benefit to procedural on-demand generation for stuff like this?

Valgrim 5y ago
In a way procedural generation can be tought of as extreme compression!
ArkanExplorer 5y ago
Since everything is just from megascans, it might make more sense to have 300gb of photorealistic assets stored on every next-gen device, and (UE5) games can just commonly load from them.
- t0mbstone 5y ago
  Yeah, at a certain point, it probably makes sense to have a giant library of universal assets like rocks and grass and trees. There's no reason for each outdoor game to keep reinventing the universe.
  - contriban 5y ago
    So basically you’re asking for a node_modules for games!
    - typon 5y ago
      More like a /usr/lib shared across games on the same console
      - incrudible 5y ago
        This is Unreal/C++ we're talking about. If the size of some field somewhere changes, your 300GB will need to be re-cooked...
  - Arwill 5y ago
    You can do that with Substance. Store images in a library and procedurally generate textures at runtime.
Hammershaft 5y ago
> isn't there a benefit to procedural on-demand generation for stuff like this? Like how demoscenes do it? I would think a huge trade off is the performance hit (and potential delay / popin) of the generation
markjgx 5y ago
"and it looks like they're finally improved on what was a terrible, clunky, extremely dated UI." doesn't hold true, it's mostly the same UI with a dark reskin. Certain editor hot paths have been reworked and that's about it. The editor is almost exclusively written in Slate, Epic's in-house Window framework/general GUI module. Slate's got a pretty interesting nested MACRO system. Most definitely not data-driven and pretty much as hard-coded as it gets, redesigning the editor for real would be difficult to say the least. In reality most experienced developers don't want a new design, they are happy with the workflow they have and I have to agree with them. I'm generally happy with the "if it ain't broke don't fix it" reskin decision.
YinLuck- 5y ago
Why is a 300GB game size 'ridiculous'? If you scale it for HDD cost and internet speeds over the past 20 years, I'd say game sizes are actually getting more efficient.

wronglebowski 5y ago

Can you compile and run the sample project and have something to walk around in?

Animats 5y ago
Yes. Your first compile may take an hour. It took about an hour and a half to get to a running sample game. You get all the source code for what goes on the target machine. It's here, on Github.[1] I tried to load the demo used for the UE5 videos, but that's only loadable through the "Epic Games Launcher", which is Windows-only. It's apparently possible to bash that into running under Wine, but I don't have time to make that work right now. For those who don't know what the deal is with Unreal Engine, there's no charge until you get the first million dollars in revenue. Then they take 5%. The nature of the game industry is that the top 50 or so titles generate almost all the revenue. So, rather than bothering with restrictive licenses for all the little guys, Epic just waits until a successful game starts getting media coverage and shows up on the industry charts, then has their billing department contact the game company. [1] https://github.com/EpicGames/UnrealEngine/releases/tag/5.0.0-early-access-1 https://github.com/EpicGames/UnrealEngine/releases/tag/5.0.0...
- arunoda 5y ago
  You don't need the source code to make a executable version of the Game. And it won't take 1 hour on a decent machine.