Hey, what's up? It's me again, the uh, toxic negative Game Dev YouTuber here to tell you all about game dev and probably deter you from it. Uh, no, I'm kidding. Anyways, in the last video, I somehow made people misconstrue the video as a way of

saying don't use UE5, even though that's not exactly what the video is for, and a lot of people got misled apparently, and a lot of people felt uninspired to continue with Unreal Engine, even though that wasn't the point of the video at

all. I'm not trying to stop people from learning Unreal Engine. I've been using it for eight years, and I'm going to continue using it for the next years ahead, however long I do game development for. I love the engine, it's great, but here's the thing: A lot of people are

just learning it incorrectly. You're just, you're not learning it right. I know that's a weird sentence to say, "you're not learning it correctly," isn't that weird? But it's a thing that can definitely happen, and I notice it a lot with a lot of people trying to create

games and to do these large-scale projects on Unreal Engine. So in this video, I'm going to tell you how to not learn it incorrectly. Here's the first thing you don't want to do when you're doing a project, and I know this is going

to be kind of counterproductive or counter-intuitive, you don't want to go in and start a game. I know that sounds weird, but you kind of just want to go in and take it one step at a time. If you go in trying to make a game and you're

using every single feature possible the animation system widget blueprints all these other things it's like going to a classroom learning English math physics which is a part of math it's science and like five million other things at the exact same time and there's like seven

teachers talking to you at the same time you don't want to do that that's impossible so here's what I hear here's what I propose you do everything one step at a time you you tell yourself hey for the next two weeks I'm gonna dabble

with UI a little bit um and while dabbling with UI maybe you did do a bit of Blueprinting and stuff like that obviously that's going to be you know included with Widget Blueprints and working with UI obviously you gotta you know slap in some functionality and

stuff in there basically you want to treat it like a school curriculum now you could probably include that into a project and take everything in at one step at a time but you'll kind of have to I guess separate everything into their tasks and and you're going to

notice that hey when you work on animations it's not going to contribute towards gameplay fully or it might not contribute towards your main menu or little things like that obviously right you're kind of separating everything into their own section that way you can focus on specific things and not get

super overwhelmed that's what I would recommend for learning Unreal Engine don't learn it by switching from thing to thing because you're obviously going to be overwhelmed and here's another little thing you don't need to use every feature you don't in fact in my eight

years of using UE4, I think there's like 80% of the features I haven't even touched. There's so many other features that you're probably not going to touch as a game developer either. There's so many little things that contribute towards film and, you know, product design

and stuff like that that you're never going to use. So honestly, it's kind of like a process of you just ignore things. You kind of just have to look at what you're working on and what you're doing and you'll ignore the other things.

Unfortunately, that's kind of one of the flaws of Unreal Engine is that they just kind of throw a bunch of stuff at you even though you're not using it. Like back in the UE4 days, uh you would boot it up, start up a new project, you're

making a desktop project, but for some reason the VR plugins are enabled by default. So by the time you package the game, all of your players are gonna have their VR Steam, their Steam VR systems open up and they're like, "What the hell? I'm not playing VR!" I would say

you know, disable a lot of the plugins you don't need. Anything that's mobile related or VR related, and if you're not working on VR or mobile, disable that stuff, get it out of there. You don't need it. That also increases your, like, package development sizes and all this mumbo

jumbo that you don't really need. But unfortunately, that's one of the flaws of Unreal Engine is they kind of just throw a bunch of stuff at you, uh even though you don't really need it. So that's what

I would say short, little, sweet video, um, hopefully kind of just a little bit of like I guess the second episode to the wires UE5 show, complicated, uh, video that everybody misconstrued as me saying, "Hey, this is the engine." But in reality, that's not the point of the video at all.

I think if anything, the the engine can be, you know, sized down. We can definitely have toggleable things where you don't need to expose certain features of the the engine and until you need it or unless you need it for your project or the specific needs of your project.

That's what I would tell you though, if you're learning Unreal Engine, it's okay to be overwhelmed by it. Just, you know, take it one step at a time, focus on things almost as if it's a school curriculum. Anyways, thanks for watching. Hope this maybe helped you. I don't know.

I'll see you in the next video. Have a fantastic weekend and uh yeah, yeah, subscribe and like the video. You know, you know how it goes. [Music]

YOU'RE LEARNING UNREAL ENGINE 5 WRONG

Scripts