Categories
pipeline UDK XNA

UDK vs XNA: Part 2

Continuing on my testing of the Unreal Development Kit and XNA I focus a bit more on the development process between these two packages, this is focusing on tutorial and community strength and some asset pipeline use.

Given that the UDK is a much newer release than XNA it is somewhat surprising how quickly tutorials, youtube videos and articles are being written about UDK and all of its features. While the literature on UDK is still fairly small compared with XNA, I imagine that given this initial output it will not be very long before more people begin trying the UDK and expanding on its knowledge base.

XNA has a number of useful books and demos written for it, (still one chapter to go on the Beginning XNA 3.0 Game Programming from Novice to Professional (likely writing a review tomorrow)). The XNA community also seems to be quite established with lots of beginner tutorials as well as some more complex examples as well. Many of the examples often end up with demonstrating the ease of 2D elements in XNA as well as the usefulness of the content management pipeline for loading fonts, images, audio and models. The pipeline is quite intuitive and easy to setup your own images and content in the game using the customizable XNA content pipeline.

The UDK is a bit different, the Content Browser looks to be fairly flexible in managing the assets (as well as coming with a significant amount of import options) and appears to have a more complex overall structure to what elements it has to display. This I imagine has its strengths and weaknesses, in that it is easy to find things by grouping for larger projects but more rigid in having to use such a complex system (instead of a hierarchical directory structure). It appears that the Content Manager also supports a number of more complex file types like photoshop .psd files as well as all the unreal file packages.

All in all XNA is likely an easier choice for the beginner programmer to get started with from the community and content pipeline choice (if you don’t know you are looking for the content manager button in the UDK you might not find it straight away). The UDK editor has a larger focus on giving artists the flexibility they are used to in 3D modeling packages, but this appears to add some complexity for the programmer as well.

Still lots of stuff to explore with both systems, I will see if I can read up on some UDK literature soon (and not just online tutorials) to expand my understanding of both systems.

Until next time,
https://michaelhubbard.ca

Leave a Reply

Your email address will not be published.