It's more like I don't want to choose an engine and then later regret not choosing the other engine. Sort of similar to how I read in some other forum that some guys that learned cryengine regretting it because it's not friendly to indie devs. And thanks for the input :) , definately some stuff I should consider! For the…
I'm very new to the whole gam dev and UDK (I heard about it first) really gave me hard time with most basic things. Then I tried unity and never looked back. Took me 6 days from not knowing a thing about code to writing my own character controller just like I wanted. Tons of tutorials, great community and asset store. If…
I can probably speak to this pretty well as I use unity for my job and our hardware spec is comparable to what I experienced working on the order. Unity is great about 95% of the time. However, I find that some of the light mapping and dynamic lighting features you want to be using on a high end title are not fully flushed…
In terms of development workflow, I would easily pick Unity. The game I am working on we originally built in UDK, but ported it soon after to Unity for a host of reasons (notably the atrocious scripting and asset system). Unity gets you up and going with your project ridiculously quickly, and with the help of the Asset…
Assuming you're doing things yourself, I'd recommend Unity. Its much easier to rapidly iterate a useful product even if you're "doing it wrong". UDK and Unity are both highly capable, but they each are a different philosophy of "how to make a game". Which one resonates with you, and what your end goal is, will determine…
Tbh wouldn't really get so hung up on the details sooooooooo much. Allot of guys are comparing both engines to each other but in this scenario what's really important is what works for you and the fact is both would do a really good job on a diablo style game. If that's the type of game your doing you wouldn't do massive…