Global Communications > killermonkey's Blog

Canvasing Open Source Game Engines

<< < (2/4) > >>

major:
Same with my roommate. Told her I was doing the PD17 interview, so asked not to bug me. Her first question was, "Are you getting paid for this?..."

"FUUUUU"

Rick Astley:
what about the unreal engine?

markpeterjameslegg:
I totally know what your saying about Cube 2. I used to create maps on it myself and I would say it's not sophisticated enough for anything you have planned, although it can look absolutely gorgeous visually.

kraid:
@Rick: engines like UDK, CE3 etc. are not exactly open source. But since you asked...

Here`s a little sum-up of what i know of a few engines:

UDK
Pros: State of the art tools, constant update with new features, very good content import pipeline, support of consoles and iOS, and many more.
cons: only UnrealScript on the free UDK version. Access to the "core" requires a bought licence.

Cryengine
pros: does a few things even better then UDK, but the content pipeline relies mostly on Maya.
cons: same as UDK. scripting only, code access just with a purchased licence.

Unity
pros: a very open content pipeline, very flerxible, usable also for mobile and browser games.
support for many different programming languages such as C#, Boo (phyton dialect), JS, all of them are able toi use .NET
cons: free version is missing some tools like Flash, iOS, Android Player and most important Team Licence.

killermonkey:
Kraid,

I just looked into Unity, great find!

I find it funny that most of the "pro" features are standard in the Source SDK... like HDR, dynamic shadows (eh), IK Rigs, and Render-to-Texture.

Although the license cost is pretty minimal... we could secure $1,500 on kickstarter in seconds.

Navigation

[0] Message Index

[#] Next page

[*] Previous page