19 ms·
Unreal vs. Unity Opinion
- rektide 5y agoThis speaks sooo close to the trends that pushed Microsoft to go create WSL, to become a viable healthy platform for multi-platform development: they had to. They had to create a platform people could use as they wanted to, had to support something that takes upstream pull requests. Simply shipping Ubuntu is basically the biggest possible fix they had for long term development, going where the puck is headed. This discussion about whether a game engine is long-term supportable, whether it invests back in the gamedev, it parallels the conversation about development-experience in operating systems so closely.
- pjmlp 5y agoWSL is basically a way to get the pseudo-Linux crowd that is giving money to Apple for UNIX laptops instead of supporting Linux OEMs. Anyone could already enjoy a similar experience since Virtual box and VMware exist.
- theThreeTuples 5y agoUnreal licensing is crazy compared to Unity. A % of revenue is millions of dollars potentially. You cant compare that to the fixed opex per developer seat with unity. It’s a strategic design for a company to use one or the other. So far in all companies I’ve worked for and have consulted for attribute their choice to cost and ease of hiring.
- enraged_camel 5y ago>>U nreal licensing is crazy compared to Unity. A % of revenue is millions of dollars potentially Sure but how many studios reach that level? And wouldn’t you agree that by then, having to pay that share of revenue would be, as the saying goes, “a great problem to have”? IMO it makes more sense to focus on developer productivity because that drastically increases your chance of reaching those revenue numbers.
- doikor 5y agoBig publishers/game developers just negotiate a custom contract. But yes in general UE is more expensive then Unity but it also comes with a bunch of useful stuff like quixel mega scans for free if you are using the engine. https://www.unrealengine.com/en-US/license https://www.unrealengine.com/en-US/license
- dleslie 5y agoNot even big; I am aware of indie studios having unity source. It's not nearly as expensive as you might expect, but I'm not able to give hard numbers. :)
- sidlls 5y agoTo underscore the sibling comment: at the point where a "% of revenue is millions of dollars" the company can easily afford to invest in an in-house solution if it's that important for their revenue goals. The tradeoff is hiring a sufficient number of skilled game engine programmers to make that work. It's not cheap.
- doikor 5y agoAlso it is not just making a game engine but you also have to build some kind of a editor, script/animation tooling, plug-in support, etc. Basically if you are big enough that you can make your own engine the engine also has to be usable by non programmers making the actual content for your game.
- mysterydip 5y agoTools can be nearly as important as the engine. I've read several postmortems where the lack of good tools made the asset creation and testing pipeline take way longer than necessary, leading to delays and crunch to compensate.
- Ralfp 5y agoTiger Engine that Bungie uses in Destiny supposedly took hours to rebuild a level and didn’t do incremental builds or cache so fixing that one bad light on the map was potentially days of wait. Still better than earlier versions of Frostbite Engine from EA Dice that took week if no cache was present and ran on server farm that took raw assets together with metadata and spit out final game assets.
- cdash 5y agoThey don't even need to do that. If they are large enough where it would become millions there is a different license for them that they can negotiate with Epic. Note: it doesn't have a royalty
- User23 5y ago
- suyash 5y agoIt's actually much better for indie developers because it's completely free to build and ship something and see if market wants to before worrying about subscription costs etc like in Unity.
- klodolph 5y agoYou only pay for Unity if you already have >100K in annual revenue.
- suyash 5y agoFor Unreal from thier website - "A 5% royalty is due only if you are distributing an off-the-shelf product that incorporates Unreal Engine code (such as a game) and the lifetime gross revenue from that product exceeds $1 million USD; in this case, the first $1 million remains royalty-exempt." - much better than Unity's pricing. The > 100k annual only give you Unity Personal whereas you can full powered Unreal at much greater threshold. https://store.unity.com/compare-plans https://store.unity.com/compare-plans https://www.unrealengine.com/en-US/license https://www.unrealengine.com/en-US/license
- klodolph 5y agoOh, I thought you were saying that you couldn't build something in Unity to test the market without paying for it.
- mynegation 5y agoSo it looks like there is a break-even point in revenue per developer above which Unreal is more expensive. The question is how often studios hit that.
- DerSaidin 5y agoso TL;DR of this gist... > > what is the point of Unity, now? > Unity was good for prototyping. Access to Unreal engine source is great. Doesn't sound they are making much of an argument to redeem Unity.
- peppertree 5y agoThe problem statement was unity projects are hard to maintain due to accumulation of tech debt. The answer is to give dev engine source access... I failed to see the connection here.
- rektide 5y agoA platform which takes input, which is participatory, is probably going to do much better about the core thesis (in bold on the article): > As impressive as UE5 is, I don't think the technology has to do with its appeal as much as the long-term user experience. I agree there's not a ton of explanation & support for this point. The post does jump to a very specific topic, whether the source is open / takes PRs. For sure there's a lot more that goes into this question. The post explicitly says it leaves others to deal with a lot of the pain of the back-half of Unity development, so it's not even like there's a ton of winning moves UE has to play: they just have to not self-inflict grevious wounds. It is, however- unsaid in the article but clear- incredibly much easier to keep yourself in a respectable, easy to use shape when you are open source. The post talks about a specific bug, but just things like improving the build toolchain or adding support for some new developer tool: developers will happily improve their quality of life in a product, if you let them.
- mattgreenrocks 5y agoWhat is the learning curve on UE like? Unity took some time but it seemed reasonable for the tiny game I made. Also, is UE something to consider for 2D games? Or is Godot more the pick there?
- BudaDude 5y agoFor 2D, Godot is the best in the game right now.
- runeblaze 5y agoThe prevailing wisdom in my circle is that you just don't want to consider UE for 2d games. Godot is fine, but sometimes you just wish that you have that killer Unity asset that you have always been using.
- barbecue_sauce 5y agoUE is much more of a "batteries included" engine, so there are a lot more existing systems that you have to learn to integrate to make anything worthwhile. UE is a lot more inheritance-oriented than Unity. Unity's C# scripting is a lot more flexible and composeable. Also, even if you are an experienced C++ coder, learning Blueprints is absolutely necessary so that you can get a handle on all of the included APIs of the engine and common interaction patterns. Even if you do get a good grasp on the C++ APIs, it is much easier to compose a complex game object with Blueprints because there isn't really a "Prefab" concept like in Unity. (Some people will compare Blueprints to Prefabs, but I initially found them much less useful). The mental model for how levels work is also very different. That said, I think UE is much more powerful overall, and worth learning if you take game development seriously.
- dleslie 5y agoI've worked with Unreal and Unity both, professionally and for many years. Several triple A games, indie titles, commercial sims, and social experiences. What sets unity apart by leaps and bounds is its asset store, community and educational materials.
- rendall 5y agoWhich do you like working with, better?
- dleslie 5y agoThey both have different irritations, but for most things I would still recommend unity. Much of the long-project pain with Unity comes from its biggest limitation, in comparison to Unreal: no source, and so you're stuck with Unity's default behavior, limitations and bugs, unless you plan on extending it, wrapping it or replacing it. Whereas Unreal making source available doesn't lend itself to safe boundaries and compartmentalization. Weirdly, Unity's irritation is also something of a strength, because those wrappers and replacements tend to find themselves on the asset store, often for peanuts. Often with source. There's serious differences at the extremes, of course. But unless you're working with eight, ten, or more figures of budget I don't think it will matter that Unreal has superior tech in numerous ways, because you won't have the teams of artists to make use of it.
- leetrout 5y agoDoesnt unity Just Work(tm) with git, too?
- thurn 5y agoAt one point in the past, Unity had a legendary commitment to backwards compatibility, but that's gone now (maybe their internal promotion process rewards shipping new features over everything else?). Old Unity would never have shipped a fiasco like URP. They'd have figured out a way to make incremental migration possible instead of having a global setting... I refuse to believe this would even be particularly difficult.
- luxxuor 5y agoIf you believe that then you have neither used or unsterstood the concept of the new scriptable render pipelines. Nevermind the fact that most people already switched over to either URP or HDRP.
- golergka 5y agoI've worked as professional Unity developer for 8 years after learning it as a hobbyist for 3, and I'm happy to finally be rid of it. It's good for prototypes and beginners, sure. But when you start to build big projects, you learn that al those learning resources guide you towards using awful architectural practices, and that there's a million of edge cases and weird bugs that would absolutely kill your project but will stay unfixed for years. Also, since ~2015, Unity as a company have been more and more interested in developing shiny prototypes of new features that would look great in presentations, but it would take forever to finally get them to be production ready, and they would be rid with problems even then. It's as if Unity cared more about increasing numbers of newcomers than retain old-timers and studios which already invested heavily into the engine. But I have to be honest, if you're doing mobile 2d game development, want to ship a product on both operating systems and don't want to invest in building your own game engine, it is still the best option. There are other solutions, but none have such an incredible amount of tools and assets.
- tonguez 5y ago“…since ~2015, Unity as a company have been more and more interested in developing shiny prototypes of new features that would look great in presentations, but it would take forever to finally get them to be production ready, and they would be rid with problems even then. It's as if Unity cared more about increasing numbers of newcomers than retain old-timers and studios which already invested heavily into the engine.” this sounds like the way every other company operates. maximize profits above all else naturally resulting in the degradation of the product
- ffhhj 5y ago> this sounds like the way every other company operates. maximize profits above all else naturally resulting in the degradation of the product Absolutely, that's the result of switching from a co-founder CEO that followed a humble philosophy to a mass market game industry CEO with own controversies.
- WillPostForFood 5y agothis sounds like the way every other company operates It doesn’t sound like the way Epic operates, which is why Unreal is a solid, successful product.
- mrfusion 5y agoIs Godot out of the question? Is it mostly a performance thing?
- suyash 5y agofor me would be lack of AR/VR support as that is what I want to build apps/games for.
- charcircuit 5y agoGodot was the only engine out of Godot, Unity, and UE4 that I could even get VR to even work.
- georgeecollins 5y agoGodot works fine for VR, particularly if you are developing the Quest. I am making a VR game in Godot. Check out: https://github.com/NeoSpark314/godot_oculus_quest_toolkit https://github.com/NeoSpark314/godot_oculus_quest_toolkit
- jimmySixDOF 5y agoUnity is the engine most used by indy VR devs & even the few using UE are not happy the new Nanite and Lumen enhancements don't work in XR. But don't take my word for it there was a good Unity vs UE twitter thread just last week [1] [1] https://twitter.com/andrewpprice/status/1514168832738607111 https://twitter.com/andrewpprice/status/1514168832738607111
- steve_coral 5y agoI've made several games in Godot and continue to use it, but it has serious issues that hamper it from prime time. Here are some I've encountered in my latest project, a point-and-click adventure in the vein of Myst - When playing non-OGV video files there will always be a black screen in the first frame of the video, no way around it - OGV video streams suffer from sound stuttering problems on playback - There are some performance bottlenecks around 3D and occlusion culling, which will hopefully be fixed in 4.0 - No browser web view so you cannot use HTML for markup or design, meaning making interactive pages (like an in-game wiki) is a massive slog - Font-rendering issues with blurriness and lack of pixel-perfect sizing (if you are doing retro pixel art fonts they will suffer from anti-aliasing) - Importing 3D assets is wonky and you still need to write custom import tooling scripts in order to make it even slightly usable. Even then you will most likely have to redo all the lighting on your models I think Godot 4.0 will be a great leap forward and I'm very much rooting for them. But if you are trying to make a big 3D A-level game, you will spend a lot of time with your head in your hands. At least with Unity and Unreal they have large asset marketplaces and very active communities so you can get around a lot of frustrations. Godot is still quite small in that regard. However for 2D or smaller scoped 3D indie games, it's really powerful and versatile. I personally enjoy the Godot workflow with nodes and signals connecting them much more than my experience with Unity and prefabs, which I found to be a bit convoluted.
- tonguez 5y agounity always required that you use a mouse to manually drag and drop certain things in its GUI interface (prefabs), and this is intolerable to people who feel like their entire project should be storable in simple (text) files. otherwise what are you supposed to do, take screenshots of the state of the editor when everything is dragged and dropped into the right place? it’s so bizarre
- minism 5y agoHaving worked in Unity as a hobbyist for about a decade and considering the switch to Unreal due to obvious issues Unity is currently facing (3 rendering pipelines being the main one), I'd like to hear more input from the programmer experience in both engines. I think C# in Unity hits a really nice sweet spot: You have a powerful and expressive type system, can use nice high level features like async/await, you get (relatively) quick compile times which help your iteration speed, and decent runtime performance due to IL2CPP. On the other hand, looking at Unreal, the main options seem to either be C++, in which case you sacrifice a lot of iteration time due to compiles, or Blueprints, which I really have no interest in (I like node editors for shaders, but i'd rather code all game logic). Those are both unappealing to me so I'm a bit stuck.
- keyle 5y agoHaving used Unreal for years in the past (UE4 only), I agree with you that C# would definitely win over the C++/Blueprint combo. Over the years, especially since blueprints compile down to C++, I've learnt to let go and embrace a lot more this visual programming approach. And it does have its benefits. With a strict approach, just as you would in programming paradigm, the readability and 'visual scanning' of opening old code in blueprints really stands out. You instantly feel where everything is, much faster than scrolling up and down code, navigating to/from methods. I've had experimented with Unity but I found at the time that UE4 was the way for me. At the time I was even working with some guys promoting UnrealJS or something, can't remember the name now, which was bringing JS to Unreal, but it sort of faded as it takes a monumental effort to bring another language to such platform. Ultimately, blueprints are fine, and I'm only using C++ for A* path finding or other heavy algo where math functions are the main focus. You can also make a library of C++ heavy math'ish things and expose them to blueprint. Overall It's pretty ok. One aspect that is not talked about much is the weight of it all. UE4 was huge. Recompiling the engine was a 3-4 hours business. When I switched to Godot for lighter games, the whole thing was rebuilt in 5-10 mins.
- wokwokwok 5y agoO_o Blueprints do not compile down to c++, it’s a VM that runs in the engine. The reason no one talks about compiling the engine is because most folk don’t do that. It’s like recompiling python. Sure… if you really want to…
- akyu 5y agoAs a hobbyist I found Unreal to be far better than Unity. The technical debt that Unity has continued to accrue starts impacting you even as a casual user. It's a bit of a mess to be honest. Unreal on the other hand has a very solid architecture and goes out of its way to be reliable and maintainable. Plus you have the full source available in your project to search through if you want to dig into the code. The code is generally well written enough that you can use the source code over documentation if you prefer. Blueprints are also great if you are prototyping things. Also if you are interested in doing networked multiplayer, there is no comparison. Unreal's networking is fantastic, while Unity doesn't really have networking built in.
- holografix 5y agoCan you expand on the networking bit?
- Jensson 5y agoUnreal engine has native support for networking. You add some configuration to your objects to determine how they should be replicated over the net and flip a switch in the settings, and now you have a multiplayer game.
- andrewmcwatters 5y agoI can't take any hobbyist game engine that doesn't implement multiplayer out of the box seriously. It's so stupid. QuakeWorld had it in 1999, and because game devs are too afraid of networking, you get a bunch of people saying "Oh, it's too hard," or "Yeah, but your networking model is dependent on what game you're shipping." No you dunces, you will always need to serialize something. You will always need some semblance of tickrate, or at least you will always need game events. The more simple features game engine developers don't write increase the risk for users who will inevitably not implement them themselves.
- hnthrowaway0315 5y agoTalking on sidelines, I really, really hope there is a new Unreal single player game that follow the veins of Unreal I. However, I do think given the complexity of post UE3 engines, it is extremely difficult for even a large community to push such a game out. Years ago I heard about a project that tried to recreate Unreal I in UE4 but never heard much about it. It just takes too much time and effort. What's your call on this? Do you think it is actually easier for a small, dedicated team (say a couple of programmers, a handful of level designers and artists for example) to get the Unreal I remake in UE4 project done, maybe in a few episodes? The first episode could be from "Vortex Rikers" to "Terraniux", the second from "Noork's Elbow" to "The Sunspire", the third from "Gateway to Na Pali" to "Cellars at Dasa Pass", and the last from "Serpent Canyon" to "The Source".
- whywhywhywhy 5y agoWon’t ever come from Epic. Think with Fortnite their future has to be these mass multiplayer half social experiences where their advantage is just the speed they can ship content to it. It’s pretty impressive technically. But if you want games like old school Unreal I suggest you google “Boomer Shooters” where there are a lot of indie FPS games now that imitate that era.
- markus_zhang 5y agoYeah thanks I actually played some of them. Very interesting. Also agreed Epic will never make another Unreal I, neither a remake nor a new game. If one wants one has to build one's own.
- tedunangst 5y agoI'm unclear on the unity source availability. It's impossible to fix a bug because you don't have the source? But you're staring right at it, which implies you do?
- charcircuit 5y agoUnity's source is not open source. They let you look at the C# code, but not modify it or redistribute it. You can purchase a license to get the source code including the engine code.
- User23 5y agoFun fact: this is the traditional (read greybeard) definition of "open." See, for example, the Open Group.
- cornel_io 5y agoYou don't have the source at all, if you're you. If you're a big company (think publicly traded, not just big), you do have near realtime access to both Unity dev teams and the full up-to-date source, and you may even ship builds made with internally customized Unity versions, but it's such bad code that you wish you didn't. And they don't accept patches back for integration in any timeline worth considering, so it's really hard to maintain local changesets while still pulling Unity's improvements in patches releases.
- luxxuor 5y agoWhat is your source on that? You do not have to be a publicly traded company to get source code Access, the source code is actually pretty well written and maintained. With the new approach of features being delivered in packages you get all the source directly in c#.
- cornel_io 5y agoUnless things have changed drastically since I was at BigCo (and maintained a branch of Unity 4 for several teams, so was very familiar with the codebase, and their native code was horrific) unless you have serious sway you don't get engine source, and in my experience that's where a ton of the bugs that will screw you lie. In fact I'm dealing with a few right now at a smallCo that definitely doesn't have access (we've asked) to the important pieces of code that are making our lives hell. I definitely agree that shipping more stuff in C# packages is a good thing, and those are mostly well written, I mostly just hate the actual C++ engine, which is frankly a disaster held together by bubble gum and spit.
- meesterdude 5y agoI have used unity for 2 years - abandoned my first project because it became unmaintainable. But my second attempt has been much more successful. I agree that unity is good for prototyping, and lots of people have experience with that. Turning it into a finished product is less well-trodden, but not impossible. The best thing I learned was to keep it simple, but not simplistic. It's easy to be too clever, but when you have good boundaries of code and reasonable coupling, it's pretty alright. My project is a bit unique in its simplicity, so i can't say someone with a more complex one wouldn't have more problems. But I'm not running to UE any time soon. Unity works surprisingly well for me, but there is a learning curve.
- overgard 5y agoOne of the most infuriating things about Unity is they tend to deprecate/stop maintaining working things even though the replacement is still in preview and/or not ready. It puts you in this awkward situation of, ok, do I develop against this stable thing only to have to replace it in 6 months, or do I do Unity's beta testing for them and waste a ton of my time dealing with their bugs? The other thing I really dislike is that quality of life improvements in the editor are necessarily bundled with engine updates. With IDEs, usually I can use a newer IDE with an older version of the compiler in something like C++ or Java. But with Unity, if I want the editor enhancements I have to upgrade /everything/, and it's almost assuredly not backwards compatible, a bunch of things are going to break, and half my plugins are going to struggle. It seems like the only realistic way to use Unity is grab a LTS version, and then never-ever touch it until the project is done. Also, while I'm generally a fan of C#, I think it was somewhat of a poor choice for games. When I was working in Unity professionally a few years ago I remember we would write code in such a way to avoid creating any garbage for the GC. But that meant that most of the nice features of C# were verboten -- no LINQ, only using certain types of loops, etc etc. Maybe the situation has improved, but it seems like there were better language choices.
- ChadNauseam 5y ago> Also, while I'm generally a fan of C#, I think it was somewhat of a poor choice for games. What do you think would be better? C++ is too verbose and full of footguns, and python and javascript are dynamically typed (which is imo bad for learning, because the error messages happen at runtime instead of compile time). I'm a big fan of rust, but even using the Bevy game engine has occasionally reminded me that I appreciate just letting the garbage collector worry about memory management. (The issues with the garbage collector have mostly been resolved at this point, now that they've implemented incremental GC.)
- wly_cdgr 5y agoGDScript in Godot does not use a garbage collector but has a nice Lua-like feel. Personally I like pure C best
- justinlloyd 5y agoAs a software developer I've worked with Unity and Unreal in a professional capacity for many years, and shipped quite a few games on both engines. Unreal is powerful, but really shows its game development studio and FPS game roots. Unity has limitations, I won't deny that. And both engines have their own issues and different frustrations in using and deploying them. I have also shipped games on internal, custom built engines too. From a business perspective, hiring Unity developers, i.e. people who can code in C#, is a lot easier. Unreal developers are plentiful, but their knowledge of the guts of Unreal usually stops at the surface level, barely dipping below Blueprints, at least from my experience. Personally, I prefer Unity over Unreal, but am not averse to using either, in the right context.
- markus_zhang 5y agoJust curious how does one go deeper into UE if not interested in Blurprint stuff?
- georgeecollins 5y agoC++ can be used instead of Blueprints.
- markus_zhang 5y agoThanks I understand that, just that the whole engine seems to be a huge blob that is difficult to approach. Maybe I should just focus on one part.
- chii 5y agoi would imagine it's easier to delve deep into UE since their source is actually available. I dont know if you can step into unity's code at all.
- Agentlien 5y agoSource code access in Unity is available but very expensive, even for large studios. Coming from a background of working with engines where the source is available it has been frustrating to me being unable to dig into or modify the engine. Especially when I'm at the mercy of some obscure engine bug. But most of the time I've managed to make do.
- deleted 5y ago[deleted]
- rudedogg 5y agoAs a macOS developer I feel like there are a lot of parallels between Unity and Apple, and the way they manage their platforms. Opening things up has a lot of benefits, but I think it's probably hard for management to accept the risk when historically things have been working out just fine. Hopefully the success of Unreal changes some minds.
- wly_cdgr 5y agoUnreal is trash for 2D. However, if I was making a 2D game, I'd use Defold or Godot or GameMaker or raylib or libGDX, not Unity. Only reason to use Unity for gamedev these days is if you wanna get a job at a mobile game company Also, both are FPS / TPAA engines. Unreal especially. Sure, you can make it do other things, but it's just not a natural fit for, say, an isometric 4X game....not that there's an openly available AAA quality engine for that at all
- rtpg 5y agoNot to tone police that much but I really don't get people like Casey. Like his whole thing is spending a billion years writing his game engine, and then whining about all these "bloated" tools. Just completely dismissive of everything that doesn't align directly with his values (which don't include actually shipping game!) I like people who write their own engines and make bespoke things for fun. Just really dislike people who lack the imagination to wonder why some people just want to make games rather than spend their life writing engine code, and actively shitting on stuff that exists. Just so much negative energy to put out in the world. Of course in practice Unity _is_ a major pain in the butt but UE has the nice aspect of actually working for very large projects and shipping stuff. Yeah there's obtuse stuff, but in practice what happens is you join a team and then you actually learn to use it. In exchange you have releases. The one thing that really is rough for me with _both_ UE and Unity is that they're both very oriented towards teams with dedicated art people who can put out assets to use. BSP-based workflows where you can quickly greybox out levels to playtest (basically giving level designers without art sense a fighting chance) are much nicer with older engines. There's a nice missing middle that Valve kinda fills with Source, except everyone that has worked with Source seems to dislike it for other reasons. But I'm sure we could make 3D engines with nicer usability for people who, for lack of a better word, can't 3D model too great.
- sk0g 5y agoJust curious, have you seen the new tools in UE5 for prototyping levels? I haven't used older game engines, but these are rapid enough for me for blocking out a level. https://twitter.com/highlyspammable/status/1496314557241098242 https://twitter.com/highlyspammable/status/14963145572410982...
- w-ll 5y agoProBuilder and ProGrids (I think ProGrids is still 'experimental' but easy to install) do all of this for me.
- sk0g 5y agoNot debating that, was just wondering if this is the sort of workflow they were used to. When I used ProBuilder and ProGrids, the workflows there weren't quite as intuitive for me. Not bad, I just didn't put the time in to get comfortable with them.
- thejosh 5y agoI really want to like Unity.. but they make it hard. There are a bunch of ways to do one thing, and those ways are probably deprecated. I really like their direction for DOTS, but their communication with their community is pretty much dead. They made a single post after a very long time with an update, and provide no real roadmap. UE5 is pretty good, having not used UE4. I like how they keep everything backwards compatible, so it's pretty good. I like blueprints and how you can use their C++ bindings pretty easily from it. I also like that UE5 is dogfooded by Fortnite, so they actually have skin in the game to make the editor better, instead of just relying on royalties.
- dleslie 5y agoAs a long time Unity dev, now: Wait for a feature to exist for two major revisions. It might still be deprecated in a future revision, or removed entirely; but with two revisions they'll generally have smoothed out all the rough parts.
- ntSean 5y agoUnity has changed their tact with features. Dogfooding with Animation, Game Development, VR/AR. You name it, they have an open source project to start from: https://github.com/UnityTechnologies/open-project-1 https://github.com/UnityTechnologies/open-project-1 New features include source access through Github, have QA testing statuses (Preview vs Verified), and have automated upgrade paths. I recently went from Unity 2019->2022 and it was seamless. Source code access is ubiquitous too. This is all very different from the Unity 4 days where a patch version would break your project! The downsides are that the Editor is mostly single-threaded, so in large multi-year projects, iteration time and navigation can be difficult. Unity have a “task-force” that are working to resolve these issues, but their communication is really lacking. Unreal devs by comparison are much easier to get ahold of and have more open roadmaps. I’m hoping that Unity moves in this direction, but they’ve been burnt by this before: promising features in timelines that weren’t feasible (i.e nested prefabs)
- jandrese 5y agoBeyond game engines one of the things that drives me crazy about commercial software is when I find a bug, document it thoroughly, and submit it to the company only to be ignored. Even with a support contract and on rather severe bugs it can be way too hard to get something fixed. I know I'm not the only person being bitten by this bug, it's all over the help forums and Reddit yet the company doesn't seem to care at all.
- bricemo 5y agoThis is frustrating. I’ve been on both sides of it, what’s happening is that the team is likely juggling thousands of bugs in similar or greater severity, as well as their roadmap for new features. Some things just get deprioritzed over and over, even though everyone knows it sucks. It usually takes a rogue engineer in their extra time, or a dedicated “user love” budget (which I always implement on my teams) to fix it
- Beltalowda 5y agoI completely get all of that; it's just frustrating when you know exactly what the bug is, and can almost see the code causing it as well as the fix in front of you (conceptually), but ... you can't actually fix it. For example I once spent weeks working around a memory leak in a piece of very expensive commercial software; it was not a fun experience and extremely hacky, although it did work (I later heard there were problems after I left though, causing subtle financial issues and which took quite a long time to find/fix :-/). I don't expect anyone to fix our problems for us, I just want to fix my own problems. I don't expect everything to be Open Source; I'm fine if it's not. I also don't expect them to drop everything to fix this bug for me. But it is critical for our business, and please, let me sign an NDA or something and let me fix this bug. Everyone wins with this.
- johnnyanmac 5y agoYea it sucks. I assure you it's not discarded, it's just marked as Jira ticket #8563, and during some periodic planning it's never the highest priority compared to immediate clients filing ticket #8654, directors filing an epic ranging from #8700-8712, etc. And it's not always something as easily implemented as the user thinks. Sometimes it goes that smoothly and everyone is happy. Sometimes it clashes with other future features the user isn't aware of yet or simply hit some nasty edge cases in testing. So it's now a low priority bug that is also non-trivial to fix. the worst kind. All I can say is to try and get other users to file the issue. The more user pain it causes the more it'll get prioritized.
- BeatQuestGames 5y agoIt depends on your projects needs. I built a music visualizer in Unity, and have no idea how I would of done this in Unreal. It was a small project, and I'm already using it to make videos. My biggest issue with Unreal is how hard anything is outside of Blueprints. C++ is much harder than C#, for my project I both load audio files locally ( you select your own music to play), and download some from a server. I'm pretty sure this is impossible without writing code. If Unreal allowed for Python scripting that would make it much more appealing. I've never worked on a big project in Unity, I'm not sure what issues arise then. Again, it depends on your needs. I do think most people are better off learning to program with C# over using Blueprints. Ether way your going to need to invest a significant amount of time learning. If you learn C# you'll be able to easily get a job even if it's not in gaming( this is what I did, and it's worked very well for me). I'm not sure what job learning Blueprints will get you. The visualizer: https://www.youtube.com/watch?v=2dv2cjJIh2s&t=1s https://www.youtube.com/watch?v=2dv2cjJIh2s&t=1s
- suyash 5y agocool project, I'm sure you can build this with unreal too just a steeper learning curve though payoff would be higher quality graphic rendering.
- BeatQuestGames 5y agoThanks for checking it out! Assuming Unreal does add their verse programming language later this year, I'll be open to recreating the same project with Metahumans instead. Maybe I'll even apply for an Unreal grant!
- dogles 5y agoOne thing that wasn't mentioned: (realtime) multiplayer. What's the story here for Unity these days? There's still a lot required in Unreal to implement things like bullet or projectile latency-correction unfortunately, but the base infrastructure they provide here is huge. Last I used Unity, there was essentially nothing. There were some third-party things but nothing you'd ever want to use in a shipping multiplayer game that isn't turn-based. Has anyone actually shipped a multiplayer (not turn-based) game with Unity that doesn't regret the decision?
- pelorat 5y agoThe networking in Unity is still terrible. Unreal is of course better but still not good enough out of the box. When Riot developed Valorant they had to rewrite the networking code to be more like Quake and Source.
- anonymoushn 5y agoI'm aware of some fighting games in Unity. These are real-time games but by convention they derive game states from sequences of input states from the players and use time travel to amend entire estimated game states (rather than e.g. estimated positions of individual objects). These games still face some unnecessary trouble imposed by Unity: it's not possible to handle all inputs and networking on a thread that's entirely separate from the thread that does rendering.
- pnw 5y agoHiring UE developers was a major issue at my last company. Not only are C++ game devs much scarcer, but they also seemed to gravitate towards AAA projects and were difficult to recruit for projects that didn’t fit that mold. Unity devs on the other hand are much easier to find. We ended up with a 5:1 ratio of Unity to UE developers, and all of our UE devs were remote.
- balls187 5y agoCurious what people with experience using Unreal vs Unity for film/animations feel.
- tomatowurst 5y agoIf you are an indie developer and have never worked with C++ before, don't even think about UE5, if you plan on ever finishing your game. Stick with Unity. Unreal makes money from royalties. Think about the odds of indie game developers generating more than $1MM vs an established studio who has shipped games/films before. You've been warned.
- rasz 5y agoOn a flip side Unity game has greater chance to be made by incompetent people, as evidenced by all the asset flips https://crappygames.miraheze.org/wiki/Asset_flipping https://crappygames.miraheze.org/wiki/Asset_flipping https://www.makeuseof.com/what-asset-flipping-gaming/ https://www.makeuseof.com/what-asset-flipping-gaming/
- kensai 5y agoSomebody wrote this comment. It was spot on. "UE5 is very pretty because Sweeny is a rendering god. But its hell to do any real programming with. A project that took me two weeks or so in C# is taking months to reproduce in C++ and Blueprints. UE5 is a very pretty FPS engine with a low-level plugin interface and a scripting language. The further you get from an FPS the more unwieldly it becomes. Unity is a programmable physics simulator that happens to have a render pipeline bolted onto it. It is much more flexible, though sadly not as pretty," Am also asking myself. Did the company behind Unity going public last year or so not help with the situation? I mean extra money and public scrutiny usually do.
- fxtentacle 5y agoIn my personal opinion, it's the opposite: Unity is a black-box machinery with a C# interface bolted on. But as soon as you touch the limits of the black box, your sand castle breaks. UE4 is the full but raw deal. If you stay within Blueprints, things are easy and predictable. But if you need to exceed its limits, then you have the C++ needed to recompile everything, but things are messy and ugly down in the basement. As for Unity going public, my impression is that now they are spending much more resources on shiny things to show off instead of fixing bugs that actually affect their paid customers - who mostly do mobile games. Also, it appears that they improved their profitability by massively increasing prices and simultaneously reducing support.
- Jensson 5y agoUnity is primarily the renderer and physics engine, everything else is really easy to just write yourself as c#, and unity in no way hinders your ability to write everything else in c#. If you want to change the renderer or physics engine then you have a problem, yes, but unity isn't for people who wants to customize the renderer or physics engine.
- fxtentacle 5y agoIn our case, we jumped ship because Unity had bugs and were unwilling to fix them for years. I believe it still is effectively unusable for anything requiring realtime multiplayer.
- saint_angels 5y agoas a professional Unity developer, I think Unity would be a much, MUCH better engine, if Unity Technologies would make commercial games with it, in-house. Just like Epic games do. Then they wouldn't tolerate all the crap unity devs have to deal with
- alkonaut 5y agoWhat’s the story for developing in UE without C++ these days? Can you get along with just scripting and shaders? What sort of functionality would require new C++ and wouldn’t be possible in script? What draws me to Unity is C# because learning C++ is a decade long project.
- Jensson 5y agoThe main things found in many games would be procedurally generated assets like maps, and strategy game AI/pathfinding. Most other things should be possible in blueprint scripts or standard components if you can live with the performance, which you can if you can live with unity performance.
- bick_nyers 5y agoBlueprints in Unreal is quite, quite powerful. You can do damn near everything with it. For the stuff that you can't do, the asset store is solid.
- flohofwoe 5y agoI think it comes down to two points: Unity has much better (real world) mobile support, , and there are many more people trained on Unity. IMHO chasing the elusive AAA carrot is Unity's biggest strategic blunder right now.
- yc-kraln 5y agoI've shipped Unity games, and had impact on some engine decisions for major companies (between Unity, Unreal, and a few others). Unreal is a FPS engine with a gorgeous renderer. Unity is a rendering pipeline, physics engine, with a C# interface. Are you making a movie? Unreal. Making a FPS (or third-person, I guess. an ego shooter? whatever.) Unreal. Making literally anything else: Unity. It's that simple.
- bullen 5y agoThe reality is that the only tech all companies are hiding in plain sight is Skin Mesh Animation and Unity doesn't even implement that in a vertex shader! They use a compute shader which means they have to send all meshes every frame. Here Autodesk plays a huge role in bottlenecking the tool chain and that is all perfectly legal. Monopoly by standardizing tech. Everything else involved in making a game is much easier from scratch. Combine that with the fact that all computers without keyboard and mouse are wasted energy and you'll quickly realize that if you only need to support Win on X86 and Linux on ARM your porting is trivial if you use OpenGL (ES) 3 which is the final GL with VAO. Add HTTP, OpenAL and use .dae, .obj, .ttf, .wav, .tga and .zip and you're done! Also don't use anything much beyond C and you can't fail.
- msie 5y agoHuh?
- pyinstallwoes 5y agoThe influence bots used the wrong GPT3 model.
- bullen 5y agomsie name checks out?
- StockHuman 5y agoI wish "Unreal as a Library" existed in the same way it does with Unity; as we use the runtime to ship the cross platform AR component of a react native app.
- torginus 5y agoA magical property of Unreal is it's open-source-ish nature. Industry leading people constantly contributing features at high quality that become integrated into the engine. I contrast, for Unity, you have to shop around in the Asset Store for that does the thing. An example for it is procedural shattering - some guy needed it in their game and now it's standard in Unreal. For Unity, you have to buy it from the store, and I guarantee it, it won't be even nearly as good. I think the Asset Store is a poisoned apple for Unity - for developers it makes very little financial sense, since you are looking at what, 1000s of sales for $50, of which Unity makes some significant commission? That's why people put a ton of half-baked stuff in there, which they abandon, and due to the constant shift of Unity, becomes unusable in like 3 releases. They also can't integrate their stuff at the same quality in the engine as if they had source access. Additionally this creates another headache for Unity as well - now if they wanted to 'properly' support this feature, they'd be competing with people who wrote the asset store version - sending the signal to them, that if you do really well, your feature will be stolen by your masters. What does also happen is Unity buys a particularly high-quality plugin (TextMesh Pro, ProBuilder) and they just give it away and don't bother to integrate it, which means it will stick out like a sore thumb.
- rasz 5y agoWhen I hear Unity first thing that comes to my mind is another asset flip scam and performance problems.
- lfkdev 5y agoGodot FTW
- jrootabega 5y agoI'm new to Unity and game development, and I'm starting to feel like there's another problem alongside bugs: misinformation. I've been reading through the official manual/prose guides, and many of the chapters blatantly contradict the UI and behavior. Official samples from Unity make typical noob mistakes. Unity employees make incorrect recommendations in the forums. Bug reports will go unacknowledged for a long time, which makes it hard to trust anything you read. So in addition to having to put in the effort to learn the tools and concepts, you have to be ready to distrust anything the docs and even the employees tell you. Unity itself is a force actively working against you.
- markus_zhang 5y agoThe more I read about these arguments the more I think it might be actually beneficial to male your own engines if you have 1) a small-medium size team and 2) not reaching for top notch graphics. Does it make sense?
- andrewallbright 5y agoIn this critique of unity they say that the back half of making a game is the half of suffering. In my experience, it highlights something else that is a massive problem in the game dev space. The game dev community is stuck in software practices of 2005, leading to naive implementation patterns. As a hobbyist game developer of ~1year, one thing that struck me was how I have not found many good sources of teaching that explains how to make a maintainable game. How does one make a code base for a video game that has desirable the non-functional qualities like maintainability? That question doesn't really have an answer... I think it doesn't have an answer because those teaching game development haven't really asked. I'm sure it's due to many factors. For anecdotal, I've asked about testing and CI/CD for unity in online spaces. There isn't much content on these critical subjects in the video game education space. I usually get a mix of responses but one that stuck out to me is that video games aren't appropriate for tests and it just slows down game creation. I think that thought process more than anything is what leads to back half issues. I think that the video game industry has lagged behind the rest of the software industry and there is a huge opportunity for disruption. In 5-10 years people should think it's absolutely outlandish to start a complex software project such as a video game project without a CI/CD engine running a suite of sensible tests. I think today that is true for most software projects, although as a community were still wrapping our heads around "what is a good test?" My 2cents
- ssimpson 5y agoI feel the same trying do develop an enterprise application with Unity. When I worked for Unity I found it fascinating that game devs (not coming from game development) were “locked into” a particular version. I hope the package system can alleviate some of that but there is a real need for some automation and upgradability.
- leetrout 5y agoSpot on. All the tutorials, articles, etc just cover small bits and nothing addresses the full software dev lifecycle as it pertains to games. Managing binary assets across even a small team presents a set of challenges the normal web-devs like myself have been unlikely to encounter, as well.
- 5y ago
- zschuessler 5y agoI'm late to the game but I'll throw in the opinion of a hobbyist doing VR development. I gave Unreal 4 a solid shot: did the tutorials, watched videos, learned simple concepts and advanced concepts alike. After months of learning one weekend I thought "I'm not having fun anymore" because 70% of my time was troubleshooting build errors and vague bugs (I actually counted). I'm no stranger to build errors (I'm an engineer) and even for me it was a difficult task to fix them. I would go down rabbit holes for hours fixing vague errors. Further, just about every tutorial I came across for UE4 was outdated and didn't work. I swapped to UE5 a few months before they released their first public version. It was an absolute beaut of a system to use in comparison: better UI, drastically fewer bugs, tutorials were accurate, and no build errors. Quite a bit Just Worked, A+. Ultimately I went to Unity because at least for VR, there were better tools that were better supported by the package maintainers. Adding a new third party Thing to a project in UE5 was a guaranteed recipe for troubleshooting weird bugs. In Unity, everything worked flawlessly. And personally, I dig C# more than C++. So, I did the same learning process with Unity: simple/advanced tutorials, plenty of time dedicated to picking up all the concepts over several months. I'd say Unity for a hobbyist is still the better route if you are planning on doing game dev part-time. It's just easier to use and breaks less. This is the opinion of a hobbyist doing VR development part-time though, and I fully believe other comments from industry pros saying Unreal is the way to go. I can't comment on that but I will say Unity was best for me. Both asset stores were pretty killer and I spent WAY too much money on assets and scripts. Prepare to have a checkbook handy if you get started with either ;)
- bstar77 5y agoIt seems like Unreal is a terrible fit for smaller projects where visual fidelity isn't a primary concern. Would I ever build a roguelike, city builder or 2d platformer in Unreal? Wouldn't something like Godot or Unity be a much better fit? AAA level graphics in nice, but there are many game genres that have visual fidelity very low on their respective list of concerns. With the rise of the Steamdeck, I'm sure there will be a rise in efficient portable-friendly games that can get that 7 hours of battery life. Not sure I would ever consider Unreal for those types of projects.
- ecshafer 5y agoAs a hobbiest, even if visual fidelity isn't a concern I would use unreal over unity. Unity optimizes for making a block move around the screen, but becomes increasingly convoluted in design. Unreal doesn't feel like you are just hammering random different unrelated systems together as much. If I were to do a 2d game I would use godot though.
- bstar77 5y agoI tried Unity for a while for 2d game development and really hated the workflow, so I floundered for a couple years trying to figure out what path to take for some of my project ideas. I've shipped 2 games in Phaser, but did not like the experience at all- optimization was a nightmare and structuring a non-trivial project was surprisingly hard. I've since switched to Godot which has been a dream so far. I would use Godot for 3d development as well, but I realize that anyone that prioritizes visual fidelity will likely look elsewhere. Godot 4 will have huge improvements there, but nothing at the level of Unreal or even Unity.
- bick_nyers 5y agoI used to sell Blueprint code on the Unreal Marketplace so I am biased in preferring Unreal over Unity. One nice thing about Unreal is how easy is it to give a modkit to users with Blueprint. You can keep all of your proprietary stuff compiled in C++ yet exposed to Blueprint which is pretty easy for any regular non-programmer to pick up. I have been playing around with the Conan Exiles modkit recently and you basically get access to everything that an actual salaried game developer would have access to. Heck, I could even turn it into a VR game purely with Blueprints (I'm actually working on this in my spare time, which admittedly, is few and far between). Seeing the control flow of Blueprint live while debugging is also great for non-programmer, as it allows them to easily reason about what is and isn't happening. You can talk about rendering pipelines and the marketplace all you want but Blueprint is the killer feature for Unreal Engine. You could make Python scripting for gameplay logic a first class citizen in Unity, but even Python is harder to work with than Blueprint for less-technical creators and users.
- sombremesa 5y agoUnreal vs. Unity is pretty much the 'spaces vs. tabs' or the 'emacs vs. vim' debate at this point. Nobody who makes a living from gamedev is dropping their engine of choice thanks to a flashy demo or even a killer feature unless they're facing some kind of existential threat. Thus, the most knowledgeable folks can't fairly compare the engines, and the only people really making noise in this debate are amateurs with little to no skin in the game. There are exceptions, such as where a studio that made the switch for reason X or reason Y is able to clearly articulate what they're doing and why, but these exceptions only serve to prove the rule since they're extremely rare to come across.