Unreal Engine 5 enters Early Access

Re:Unreal Engine 5 enters Early Access by ArkanExplorer on Wednesday May 26, 2021 @12:47PM (#27292861)

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.

[ Parent | on HN ]

Re:Unreal Engine 5 enters Early Access by t0mbstone on Wednesday May 26, 2021 @12:55PM (#27292999)

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.

[ Parent | on HN ]

Re:Unreal Engine 5 enters Early Access by contriban on Wednesday May 26, 2021 @01:07PM (#27293168)

So basically you’re asking for a node_modules for games!

[ Parent | on HN ]

Re:Unreal Engine 5 enters Early Access by typon on Wednesday May 26, 2021 @01:24PM (#27293409)

More like a /usr/lib shared across games on the same console

[ Parent | on HN ]

Re:Unreal Engine 5 enters Early Access by incrudible on Wednesday May 26, 2021 @01:47PM (#27293731)

This is Unreal/C++ we're talking about. If the size of some field somewhere changes, your 300GB will need to be re-cooked...

[ Parent | on HN ]

Re:Unreal Engine 5 enters Early Access by Arwill on Wednesday May 26, 2021 @02:23PM (#27294195)

You can do that with Substance. Store images in a library and procedurally generate textures at runtime.

[ Parent | on HN ]