A Taste of Chocolate: Adding a Rendering Fast Path without Breaking Unreal Engine | Unreal Fest 2024 

5 years not 8

@@biiiiioshock Thanks for the correction

he works in the company, that means that the game is another game in their list, that be a great tool for future projects

That's what you get when you're owned by Sega

Then there's games that people work for 5 years and they never see the light of day :c

Engine*

I think the focus of the video is not on whether they did the correct call or not creating their game. I think the purpose of this video is to show people the customization of UE, that you can actually do anything you want pretty much. Now, most of us are aware of this already but I'm sure there are people who will have a light-bulb-moment after watching this or even just reading the title. But yes, I'm 99.99% sure your focus on the game and it's necessities are not why they had this talk. The game they worked on was simply an example to demonstrate capabilities. If the game was much larger and did look a lot prettier custom-tooling is a solution that could be and often is used. I agree though, doesn't look like it would be necessary for the project they worked on.

Not at all. Some of the things mentioned here have later been implemented by Epic themselves for example. Don't forget that Unreal is an "off-the-shelf" engine that has to cater to the masses, and while it does an admirable job, that comes with a lot of overhead many games just don't need, and it's extremely common to need to modify it - even at this level.

@@Jambaxyea I think their descriptors or chocolate instances ended up as Lightweight Instances which is really cool if true.

If they were reinventing the wheel, then it would be good to have information on what parts he proposes could be replaced with off the shelf methods. (I also think this talk is decent as a way to showcase how UE could be improved, by making more of these optimizations decently automatic)

Seemingly the art team and the game play team were supposed to work in parallel, making a 'procedural' solution necessary, which was terrible for performance. Agree with your bottom line.

So.. you're on RU-vid, can Google, and can ask a chatbot but if you aren't literally guided click by click in the app you're lost... But you're here? How do you rationalize this? Making games isn't a matter of just swapping character models and retargetting animations or using a common rig x.x you'd just keep asking for more and more "click me through this please" so just wait for super intelligent ai agents that can make games for you - though they'll likely only work with Unity at first due to the massive difference in training data available x.x Otherwise just type anything into a search bar and someone will explain it. There's no reason to make the barrier to entry lower - eventually researching is part of your onboarding, games are too unique to be cookie cutter tutorialized :/ The helper projects are a fantastic start - dig into the blueprint content examples library project in the learning tab of the launcher if you haven't already - sorry that I can't be more helpful :/ but I promise you that Unreal is an iceberg, far deeper than many know even after several finished games.

Go study Computer Science. The UE is easy.

There are many tutorials on RU-vid to get started! :)