In this lesson we learned about key aspects of the creation of a project in UE5, with a focus on understanding said core elements and preparing for upcoming, more advanced, classes.
- File structure: UE files use distinct formats such as .uasset for assets like textures and .umap for maps, this makes file transfers between softwares not so straightforward, since assets need to be processed and migrated into UE.
- The structure in which projects are produced is quite layered, allowing for larger projects to be more manageable.
- When setting up a project, you are met with the choice of using either Blueprints of C++. I will be using blueprints since the logic is something I’m more used to, having utilised elements of node programming in Cinema 4D’s espresso feature.
- Render settings: these settings are optional and I don’t see myself using them for the time being, but can be tweaked for enhanced rendering for those who need it.
- Level Management: levels are essentially containers for scene elements, this makes shifting from day to night, for example, more manageable. I can have one project with multiple variations that can be switched with ease.
- Actors: sounds, meshes, animations, blueprints etc are all considered “actors”, and can all be used in tandem to build an interactive environment
- Starter templates and marketplace samples are resources that can be leveraged to streamline the development process, releasing the pressure of having to create a lot of things from scratch.
I’m fairly used to this concept, having used Sketchfab’s plugin in Cinema 4D. The marketplace on quixel/ fab seems quite expansive – and there is a wide variety of free assets at my disposal.
At this moment in time, I am relatively inexperienced in UV texturing and modeling in general. I’ve been relying on easy and inefficient shortcuts when using C4D because everything can be hidden or changed in post. Learning more reliable techniques will elevate my work to the next level.