Unity vs UDK

Hello,
First of all I realize that there are 100s of topics of Unity vs UDK and I am aware that posting a question like this on the unity forums will get me bias opinions but nevertheless I thought it would be worth the time to throw together a quick post in hopes I might gain some insight from it. So I am taking a game design course and we were presented with a choice in our engines, source, unity and UDK. I have had some experience poking and prodding Unity and have taken quite a liking to it. As I was poking Unity my friend started to play with UDK. I am more of a coder and he is a modeler and plans to do level design and one of his biggest qualms with Unity was how the tools for level design seem inferior to the UDK. I suggested to him that he could use programs and then just import his levels… Anyways after my short ramble my question is this: What can I do/say to help make my argument stronger in convincing him to use unity with me.
Thank you,
Ombra

Well, if his thing is just finding a tool to design a level in, then UDK will probably be easier. It has more built in tools to help an artist do that. But the process is a little slower. A little delayed gratification when it comes to making art and then actually seeing it in the engine.

If you’re making a whole game, then you have to decide what your market is and what your resources are. What gives you the best overall balance in workflow?

How many people are on your team? What kind of game do you want to make?

Art assets are a lot easier and faster to get into Unity than they are to get into UDK. So he could almost instantly see what his stuff looks like.

What parts of level design does your friend find lacking in Unity? There are definitely points where UDK is the winner, I’m just interested in which ones are important to him.

If you use the nFrige, you can code your scripts on Visual Studio, debug, set breakpoints, watch variables, have intellisence, autocompletion, compile your scripts and even execute your game from there, no need to close the editor. :wink:

You can make any kind of game with UDK.

But, theres no point in comparing UDK to Unity.
Both have different workflows, differents editors, differents lighting and rendering techniques. Everything is quite different, no one is a winner.

UDK have a lots of fancy middlewares and tools that make it quite rich for any profetional game dev. On the other hand, the lact of features in Unity make it easier to pick up (less stuff to learn).
Unity Editor workflow is easier to pick up.
With Unity3, it seems that Unity is catching up
next gen engines, but still a hell lots of work to do
in orther to seat next to Unreal Engine or CryEngine.
But kudos, i love Unity and thats what i chose. ^^

It was the first day of the course today so my group isn’t set in stone since… well my friend is wanting to not use Unity and I am solid on my decision to use it. The group is looking like it will be Two coders including myself, one level designer, two animators/modelers/riggers and one sound guy. The type of game we are planning to make is most probably one of these two:

A) A small openworld mystery puzzle set in the early 1900s

B) A fantasy action/adventure game. For lack of better words think of Legend of Zelda: Windwaker type game.

The part that he complains most about is the terrain editing and the fact cliffs and buildings can’t (as far as I know) be made easily in Unity itself. He also says that coding is “easier” in UDK because you have the visual aid of Kismet which I don’t really see it really affecting him since I am going to be doing the bulk of the coding myself.

No way, the scripting part in UDK is not easyer thanks to kismet. Kismet is just for very basic stuff, as I’ve been told. To do any game coding with unreal script you need some other 3rd party program, it’s not integrated like in unity… when you have the code file then you gotta change some stuff on some config file to let udk know what to compile, i forgot already, all I remember it was a real mess, if this have changed or I’m mistaken let me know, because I was let down by UDK for this very same reason.

And when it comes for level design, if your friend is an actual 3D modeler, he’ll be better off using the 3d tools he most likely learned to use, instead of whatever tools UDK might offer for people without access and/or knowledge for commercial 3D modelling tools.

There are at least 5-6 other extensive threads exactly like this one. Please use the search function instead of starting another one next time. Not because it’s wasteful (which it is) but more likely because fanboyism always kicks in and nobody has anything to benefit from them.

but he did mention he realized there’s 100s of posts like this, meaning he doesn’t care, lol

I’m not a huge fan of Unity’s terrain engine either, but for coding/prototyping and workflow… Unity really can’t be beat. Small teams can really cover a lot of ground quickly.

If your friend is working on level design, perhaps they would be comfortable working with a 3d modelling suite like Blender or Google SketchUp? Level components (or entire levels) can be constructed externally and imported into Unity scenes for use.

Also if they have to do minimal coding…Unity’s Javascript is quite easy to use (though I personally prefer C#! :smile:)

Anyways, I’m not terribly familiar with UDK…so I am not saying to jump ship completely on it, but I do know Unity and I must say I’ve never enjoyed developing games so much.

At any rate good luck!
Cheers

This probably isn’t the best place to get an unbiased comparison.

You can debug exactly the same way on UDK using nFringe and Visual Studio, set your breakpoints, the game will stop on your breakpoint and watch your variables. You can also step in and out and see every output in the UE console.

I’ve been making a bunch of smaller projects in Unity alone and I spend nearly all my time in either 3ds max, photoshop or Visual Studio. The work I do inside of Unity itself is minimal. However there are a few places which I think Unity is behind.

Particles is one of them. Coming from a 3ds Max background particles in Unity are sucky, honestly. :slight_smile: I think particles are one of the most important features for any game and the particle system in Unity is limiting. The most crucial feature that is missing is particle rotation. You can overcome a lot of the other missing features through scripting, but I would like it if they were there from the get go. A node based particle editor would be the best new feature in Unity for me.

Another feature that is missing is the ability to create custom geometry inside Unity. I probably wouldn’t use this much for modelling, but for making triggers, colliders etc. it would be great.

I haven’t got much experience with UDK, but I’m pretty sure it has a much, much better particle system and the ability to create geometry inside the Editor. :slight_smile:

I can give some information from an artist point of view, since you need to keep “your man” on your side I can give some examples why he should use Unity instead of UDK…

Just to be clear, graphically speaking I prefer much more UDK, the engine itself is awesome and the features are great…but let me show some pros and cons of UDK:

  • Very powerfull engine
  • Perfect combination of lightmapping ( Beast ) and realtime lighting gives you a great look
  • Awesome post effects that allows you to quickly change the look of your scene in no time
  • Possibility to do a game with one of the most famous game engine
  • Very slow import options ( fbx or ase, one mesh at the time )
  • If you’re not familiar with node shaders texturing can be a really pain in the a…
  • 25% royalties…ok is not a lot, but with taxes and some other stuff you risk to get almost nothing
  • Too much game related, if you’re an artist and you want to do, for example, Architectural Visualization, you need to code basically everything ( except the cameras maybe )

I haven’t seen (work with I mean ) Unity3D 3.0 yet, I still think that ( graphically speaking )UE3 is far better, but considering that Unity since the last release was graphically a bit crappy, this is a huge step, the new features are great and I’m pretty excited to try this new engine…
The good thing about Unity is that is immediate, I mean that, once you have a scene in your 3D app, is quite easy to import everything into Unity3D and try it out, even if nothing is textured, but the ability to check “on the fly” the scale of the scene, see if everything is ok is a really nice thing, since you have the ability to re-export a mesh and Unity will update it!

Pros and cons:

  • Beast lightmapping ( huge timesaver )
  • Good post effects
  • Immediate, export an entire scene and try it out in few minutes ( depends how big is your scene )
  • Huge and growing community, very helpfull to solve small/big problems
  • Share your game on PC, Mac, Ipad, PS3, Xbox, Wii
  • Still ( from an artist point of view ) if you need something specific you have to code it

For my project I decided to use Unity basically because I need a fast visual response, but having the possibility to use amazing tools ( such as Beast, that avoid the annoying process to export your lightmap from your 3d app to Unity ) and check the results in a reasonable time is pretty amazing!
And don’t forget that you have much more audience if you plan to develop your game with Unity, since you can develop for almost every digital platform available :slight_smile:

I recently switched to UDK. and to be honest, i was amazed with how powerful that engine is compared to Unity, and since i’ve been using the beta for three months now i dont really think Unity is catching up yet.

Good thing that particle rotation is coming to Unity 3.0 soon!

But yeah, I do agree that our particle system could use a lot more improvements.

This can be done by writing some editor scripts I think.

@Aras, that sounds great.

And yeah, I’ve seen people script the geometry thing themselves, KurtLoeffler’s BSP geometry and lightmapping comes to mind. However, I’m not skilled enough to make such things myself yet. :smile:

The engine does have very powerful features. But what about coding in unreal script? how is it done?
In unity you double click on the javascript asset and start coding, how you’d go about coding in UDK?

I like the engine, it’s just the editing that is useless.

I use WorldMachine2 and import it with this script:

http://www.unifycommunity.com/wiki/index.php?title=TerrainImporter

WM2 is a great match to Unity, no real overlap.

Hi all guys,

I read this entire topic. I am suffering from engine decision, I mean which engine is suitable for my project? Unity or UDK?

Because We decide to make a game (platformaer) which looks like Trine Game.

So my friends can any one please suggest which engine is good for this project, because I don’t want to change my engine at middle of the project.

may thanks in advance.

try them both, as a pilot (broad evaluation time per engine, you NEED to dive into documentation and willing to learn each engine indepth, to really see the pro’s and con’s in relation to your project wishes).
That’s the only way to discover which engine suits your workflow/requirements/investments.

Also consider the target audience for the game. (e.g. platform, hardware demands)

bonus: don’t forget to review the attached licenses per engine (or version of the engine), in relation to your project goals/needs. (it should suit your business model)

Both are capable engines, each with their pro’s and con’s. Both have a trackrecord of released games/applications.

Good luck.