4 ms·
Am I the only one who finds massive friction trying to learn the heavy GUI editors of both Unity and UE? I've been a hobbiest game programmer for 15 years, I st
by moron4hire 11y ago
Am I the only one who finds massive friction trying to learn the heavy GUI editors of both Unity and UE? I've been a hobbiest game programmer for 15 years, I studied computer graphics in college, I could probably write a software rasterizer in my sleep. I've been using Blender for quite some time, even in some semi-professional work. I've lead numerous projects from start to finish in all kinds of industries, including a few in raw, physical simulation. I've even built my own video game controllers.
But whenever I start one of these programs and start trying to go through their tutorials, they want you to go through some convoluted set of menus and toolbox windows to basically do nothing but edit a scene graph. And they have their own terminology for everything. And then I go cross-eyed.
And it's not even "terminal vs. GUI" talking, I actually like Visual Studio. I just want to model in Blender, export models to game-friendly formats, write code, and import them in the game, like every other project I've ever done, like a normal game project.
But even UE's "Expert-mode, C++ template" involves heavy, heavy use of their GUI, which might be relatively stable today, but it's still a hog on resources and terrible buggy compared to even Visual Studio, which itself is no lithe figure. I tried exiting out of the editor and loading the solution directly from Visual Studio and running a build just seems to... open the UE editor again!
I'm not a beginner, I don't want beginner's tutorials, and I especially hate video tutorials. I want something I can read that isn't just "click this menu, now open this tool window". What the hell ever happened to writing code?
- hesdeadjim 11y agoI make games for a living and for a hobby and the switch to Unity in both contexts has been painful for all the reasons you mention. A foreign and often confusing UI, arcane and undocumented interfaces (at least UE4 has source), and tutorials that assume you don't know how to read. The last point has been especially frustrating because what takes 45 minutes to learn from a video tutorial I could accomplish through reading in five. All that said, after getting over the learning curve and embracing the technology somewhat (even Blueprint/Playmaker over code sometimes!), I've found that the power available to me is well, well worth the cost.
- christoph 11y agoFully agree. Once you get in to the mindset, blueprints really aren't that tricky. They aren't the best way to tackle all problems, but they certainly make doing a lot of things very easy once you accept how they function, their limitations, the workarounds and commit some time to learning/practicing working with them. There's certainly an overhead in discovering how different elements of the engine talk to each other and behave together. Really it's no different to any other programming language. On a multi-monitor set up, the real time debugging is pretty sweet for seeing what's going on and where it's going wrong.
- fsloth 11y agoSorry, are you advocating UE or Unity? (I presume it is the former).
- christoph 11y agoActually neither specifically. I prefer UE4 - it seems to have a better technological core and I prefer their approach to many different elements in the engine. Unity is great as well, don't get me wrong, they've had a lot of money for licences/upgrades out of us over the years. I personally struggle to see how they will keep up with UE4 long-term unless they address some of their built-up historic technical debt quickly. I think even though they are both to some extent 'free', competition is still healthy and should be actively encouraged.
- greggman 11y agoI feel the technical debt is in UE's court. They're an engine designed for 100+ person teams where they assume you're a AAA developer and have lots of programmers to support your artists/designers. Unity is an app for making games. The difference in approach leads to vastly different experiences. It will be far easier to make Unity pretty than for Unreal to start being good at editing, good for small teams, good mobile, .. basically good at the things Unity currently does better than Unreal
- 11y ago
- liveoneggs 11y agodo you use ogre3d?
- vvanders 11y agoThat's because these tools are targeted at content builders not developers. Back when I was in games on a 70 person team we might only have 10 or 12 developers so the majority of the focus was making sure that your content builders were effective(and they cost less than getting developers to build content).
- greggman 11y agoI'm old school like you? I've been programming since TRS-80/Apple II,Atari 800 days. I know C/C++ and OpenGL, DirectX and can certainly get a simple game running faster with my own code than with Unity or Unreal at this point. But... I also go to game jams and watch the guys using Unity or Unreal run rings round those coding from scratch. I see many of my favorite games of all types being created with Unity (Threes, Monument Valley, Crossy Roads, Ori and the Blind Forest, Cities Skylines, Besiege) I also see the amount of time I'd save. I've written 6 game engines, animation systems, exporters, font renderers, image loaders, serialization systems, spooling systems, memory management systems, input systems, localization systems, etc etc etc. I've ported my engine to various systems. I don't want to do that anymore. > What the hell ever happened to writing code? If that what you like doing then do that but me I just want to get to the game. I can see very clearly learning one of these engines will get me there quicker. Sure the first time there will be learning curve but after I'm quite sure I'll be much more productive.
- moron4hire 11y agoNo, I'm not really talking about not-implemented-here-syndrome. Yes, you are right, all of those things can be fun to write for fun's sake, but I agree that it's stupid to try to write all of that yourself if your goal is to be productive and complete a game. My point is, why do I have to use their dopey editor to get at it? Why aren't these things libraries, dependencies that I manage just like any other project I've built since the dawn of time? For Unity, I can definitely see the appeal of a good "game builder" type application. Game builders have been around forever. Traditionally, game builders were crap, so to see Unity create something that can be used to make games that people are selling, for real money, is pretty cool. Unity was never going to be my cup of tea, but that's fine. But for UE4, Epic has been a long-time vendor of AAA-quality game engines. I expected a series of libraries for doing the vast majority of things, plus workflow tools for things like baking lighting into textures. That's what I mean about "what ever happened to writing code?" The way you used to wire up a game engine with your models and your gameplay scripts was to write code, not draw boxes in a flowchart editor. Command-line oriented build tools for processing scripts and packing textures and encoding audio and cross compiling could be abstracted through a GUI, but were still available to plunk down on a build server so you weren't wasting cycles on your workstation. I still get the feeling that that is in there somewhere. But where? I just can't imagine a professional game dev house using the UE4 editor.