11 ms·

Here's a warning: Unreal Engine is a haphazardly designed (at best) GUI bolted onto a hardcore low-level game engine. It looks sort of like an IDE that you coul

Here's a warning: Unreal Engine is a haphazardly designed (at best) GUI bolted onto a hardcore low-level game engine. It looks sort of like an IDE that you could sit down and get comfortable with in a few hours, but it's just an illusion. The whole UI is really just a thin graphical control layer over low-level C++ objects for which there is little to no explanation. Instead, you have menus within menus within menus... Anyone trying to transition from standard Microsoft/Apple/Google developer tools to UE is going to be in for a shock. The documentation is ludicrously sparse, there's almost no "discoverability" in the UI, and even the sample projects will have you staring at the screen asking yourself, "How the fuck did they connect that to that?? Crap, did this thing hang again??". You'll end up reading blog posts and watching YouTube videos filled with screenshots of blueprints and step-by-step instructions for which switches to toggle and which values to put where. After a few weeks, you'll be completely astounded that you still have almost no idea really of what's going on. So! For anyone thinking, "Hey, I like games and know C#! Now I can make a game!" Well, you probably should prepare yourself for disappointment.

dogma1138 6y ago
I think you have had a severe misunderstanding of what the UE engine IDE is or how to use it. In any case for C# to easy game dev you have Unity which used C# as it’s base language. Almost all game engines are written as bunch of scripts being called from a main loop so yes anything in UE regardless of what it is if it’s a graphical element or some piece of logic that changes the world state will be a self contained C++ “script” even the parts of UE that support higher level scripting languages are still then compiled to C++.
- russellbeattie 6y ago
  Yes. That was my point. The warning was for others like myself who might blunder into UE thinking it was an IDE, and not realizing it's really just "a bunch of scripts being called from a main loop".
  - pjmlp 6y ago
    It is an IDE, but whose main target are designers, artists, gameplay developers. Software developers in AAA are just putting the infrastructure in place, the real show is driven by others, so game development IDEs are tailored for those skillsets, not writing barebones C++ code.
  - dogma1138 6y ago
    It is an IDE but it’s just might be different than what you used too, although if you are used to visual component based IDEs like Visual Studio (not code) or Visual Basic it won’t be that unfamiliar. The whole point of blueprints is that the provide a visual interface to link the underlying classes together in a fairly easy manner you can actually make a game with using blueprints only now you’ll be limited in various ways from not having the exact functionality you want in a given blueprint to having performance issues if you are linking too many blueprints together to perform a relatively simple action but they serve their purpose and that is to detach much of the high level game/level design implementation from the low level code implementation.
OneGuy123 6y ago
>> Well, you probably should prepare yourself for disappointment. You have a foundamental misunderstanding of what UE actually is.
- deleted 6y ago
  [deleted]

dogma1138 6y ago

I think you have had a severe misunderstanding of what the UE engine IDE is or how to use it. In any case for C# to easy game dev you have Unity which used C# as it’s base language. Almost all game engines are written as bunch of scripts being called from a main loop so yes anything in UE regardless of what it is if it’s a graphical element or some piece of logic that changes the world state will be a self contained C++ “script” even the parts of UE that support higher level scripting languages are still then compiled to C++.

russellbeattie 6y ago
Yes. That was my point. The warning was for others like myself who might blunder into UE thinking it was an IDE, and not realizing it's really just "a bunch of scripts being called from a main loop".
- pjmlp 6y ago
  It is an IDE, but whose main target are designers, artists, gameplay developers. Software developers in AAA are just putting the infrastructure in place, the real show is driven by others, so game development IDEs are tailored for those skillsets, not writing barebones C++ code.
- dogma1138 6y ago
  It is an IDE but it’s just might be different than what you used too, although if you are used to visual component based IDEs like Visual Studio (not code) or Visual Basic it won’t be that unfamiliar. The whole point of blueprints is that the provide a visual interface to link the underlying classes together in a fairly easy manner you can actually make a game with using blueprints only now you’ll be limited in various ways from not having the exact functionality you want in a given blueprint to having performance issues if you are linking too many blueprints together to perform a relatively simple action but they serve their purpose and that is to detach much of the high level game/level design implementation from the low level code implementation.

OneGuy123 6y ago

>> Well, you probably should prepare yourself for disappointment. You have a foundamental misunderstanding of what UE actually is.

deleted 6y ago
[deleted]