Відео

Good choice! Especially for someone who's not from software engineering background, unreal engine has enforced some best software engineering practices like design patterns and project structure for you out of box. Bluepring visual scripting is easy for beginners. Good graphics out of box. Remember it takes time to master coding, I'm talking about a couple of years. However, regardless of which engine you choose, even with blueprint scripting, you will still need to learn how to code. You won't go far without knowing how to code. 2 cents from someone spent years using unity but switched to unreal and never look back.

Really Great Explaination man

Thanks bro, this saved me days of research

When you comin back bro we need more videos of you

if you think unity compiles quickly then you've never had to deal with compiling shaders

We love u just because u put the timer for the code

Not Working for me

Hello i Know that u probably never gonna see this comment but I have a question. What is the diferent between using PlayAnimMontage and using this: UAnimInstance* MyInstance = GetMesh()->GetAnimInstance(); MyInstance->Montage_Play(m_pDashMontage); ??? Thank u if can answer me :P

I did both. I think it's much easier to get started with Unreal and you feel a greater sense of satisfaction more quickly, but I honestly found it was a case of giving with one hand and taking with the other. There would be something Unreal did great, something Unity was terrible at. There would be something Unity did great, barely existed in Unreal. Unreal did X straight out of the box. Unity needed a load of extra plugins or crappy community-built asset packs to do the same. Unity does Y. Unreal does Y slightly differently and they call it Z. The Unreal editor had something hidden behind a load of different panes and menus. Unity had it right there in front of you. In Unity it's dead easy to set up A. In Unreal it's a nightmare to get A working, but it's better than Unity when you do. Unreal has B, but again, it's a nightmare. Unity now has support for B, but it's a nightmare because it's a preview version and sucks. Unreal's Blueprint system is really not that beginner friendly and dragging spaghetti around just gets old. Unity lets you just write the code in C# and you can maybe write your own Visual Studio macro to autogenerate boilerplate. Meanwhile the C++ code used by Unreal is non-standard and very cumbersome, it's also not that easy to access it within the editor. And so it went on. I was conscious of the fact that there seemed no publicly available engine with the best of both.

Unity is a total waste of money. Its a money pit. The Unity company is just about making money as much as they can from any aspect of it they can.

Thank you for sharing what you know. It'll help me 😀

Unity's Asset store is a hell. I have to constantly rewrite purchased code to work with each other. I tend to use them more like a guide or a course / tutorial. Our 3D artist does the same with purchased models, and we are talking about best sellers here. I don't have much experience with Unreal, and for our current project it's a no go. But after a few years of Unity, it felt natural and user friendly to me. On the other hand, back when I was choosing a game engine to learn, UE4 scared me away. On the tutorial side: Unity's docs tend to be outdated ("this is called that from now on", "that is deprecated" "use the new stuff", new stuff? it's in beta). Can't talk for Unreal, more then likely there are outdated docs, etc. too. Blueprints is somewhat slower then C++, on the other hand, if you want to use Unity, and rely heavily on Asset Store packages it can be even worse. I'm not dragging Unity down, the engine itself is good, C# is good, even their Visual Script solution is, well, fine, but if the game you are building is a bit heavier on performance, then be prepared to get into C# or Visual Script (or modelling if you are an artist) to re-invent the purchased packages. So, best tip I could give is: when using Asset Store stuff, it's better to stay away from packages that do everything. Rather get multiple smaller ones. Need a character controller? Get one that does exactly that. Need an IK system? Get something that fits that need. Etc.

My man’s about to get struck by lightning

Great video! I'm not as new to coding, but I am new to game development and this video has been so helpful in just reasoning out to myself why I would want to consider one over the other.

If you think unity documentation is better heres a challenge: Try to make custom hdrp graphics settings in unity (not just presets, i want you to change the actual "scriptable" pipeline setting, you'll find out its not very scriptable) Don't cheat and use my scripts or tutorials, ignore the forum post where i posted the scripts. Let me know when you've given up or died trying.

@ 8:00 Well, Unity has a component based hierarchy only while Unreal has both. A class based hierarchy where one class is derived from another + the component hierarchy where components can also be derived from other components but you can just make a component for task X and apply it to anything you want that. You do not have do inhert from x other classes, it really depends on what you want to do. In Unity you do not have a choice and it's less of a choice whether you like it or not, it is more a technical design choice where you do whatever does the job best. In Unity you do not have this choice at all, you are always forced to do everything and anything by using components which is not good from a software engineering point in my opinion.

From what I can tell, unreal doesn’t have a transformation hierarchy, which bothered me at first, cuz I was used to Unity’s transformation hierarchy. But honestly, it’s interesting when you get use to unreal’s methods of doing this

As a cs student and programmer I can honestly say C++ is a headache. I also love C++ but that is mainly due to it being the main language I used at my school. Never used C# before so Unreal appealed to me over Unity but yeah C++ is one of the harder languages you can learn.

I find myself really torn between which one to go with. I'm a complete begginer at this too, and I started in Unreal for a few days, then saw a video about Unity and have been giving that a shot for the last week. I found a course I really like and the same guy has 15 hour courses for Unity and Unreal making essentially the same game, so I'll be taking the Unreal one once I'm done with Unity so I can more fully decide. Based on my little bit of experience I tend to agree with most of your points so far, so I'm leaning towards Unreal, but I still want to give Unity a fair shot.

unity 3d has 7000 employees. i guess 6800 of them work in marketing

Thanks for the video friend tell me please if I want to develop VR projects or create Metaworlds, what game engine will suit me best as a beginner? Друг спасибо за видео подскажи пожалуйста если я хочу заниматься разработкой VR проектов или созданием Метавселенных, то какой игровой движок мне подойдёт лучше как для новичка?

Is that your natural hair

17:36 i think that's inheritance, c# has it too

I would love to see this same perspective from a professional game developer with extensive experience in both.

Can I know what theme u use for your visual studio. I find that your code is much easier to read

Hey Brother. I love this video and your truly honest nature of this subject. If you would like to really break out. You should learn Lua programming. It's very simple by far in comparison to c# and c++ . You can use it to make Unreal games via the Core Engine. Which is built on top of the Unreal engine. I hope this helps you my brother. My name is Patrick Ginn my friend.

There seems to be major updates with UE v5, so how does this now compare a year later?

i started on unity, for months i could not do much if i did not spend money on third party assets, and than the personalization was a probleme unreal engine is way more easy to use, the blueprint system is so much better, creating complexe gameplay mechanics is way more easy than on unity very sad i spent time on unity to be honest :(

I already have two years of industry experience in C++, I guess I'll pick up unreal engine.

TY!!!!

godot user be like am i a joke to u

thanks!

Thank you!

u r channel is so underrater

How can you make it so that you don't have to hold down the sprint button, and just press it when you start sprinting, and then press it again to stop sprinting?

it is 2021 and you dont have a SSD?

Very important video thanks

I feel the same way

When I was younger I self-studied C++, the most difficult part is memory management and understanding others C++ codes. C++ syntactic sugar makes it more difficult to read other codes. Whereas C# is much simpler and straightforward, with built-in garbage collection, I don't have to worry about memory leaks. But I still like C++ because it is faster and it is a lower-level programming language.

I tried Unity and then Unreal... I think I'll pick Unreal.

Thank you for making this! I was struggling with this for a bit.

18:00 inheritance is normal in Unity as well.

The specific scripts for Character Actions or Functions.. That can be attached to an Actor in Unreal.. Are called "Interfaces" and "Components" 😉

If you're working on a serious 3D project mid to big size with Unity you're gonna encounter many problems as the engine lacks many tools and reliable systems.

very good video. thanks

For me I find that unreal has at best horrible documentation, community support and UI. unity for me has the vastly superior support, so it is easier to get into and find help. in my opinion you can have a superior game engine, but give no indication of how to use it and/or horrible UI, it will always be worse as it will be very difficult to draw out all of its potential, compared to a slightly inferior game engine but have tons of easy to follow and p to date tutorials, documentation and good UI, even if it is limited it is easier to draw out all of its potential.

not 'child', but 'subclass'

It was..... a game changer. Nice.

I use unity because it is more lightweight for weak hardware.

Maybe it is just me but I don't understand how C++ is harder to "learn" than C#. I do, however, think C++ is much more difficult to "use" in practice because you have a much greater chance of screwing up; so you need to be more careful in writing your code. the reason is that you have to manage all of your memory, you deal with pointers quite a bit, and it is not as type-safe as C#. On the other hand, C# does allow you to manage your memory and allows you to use pointer by unsafe means if you really want to.