I was having too much trouble with UDK. I am unfamiliar with the engine and the tools at hand, even with the use of tutorials. I had trouble keeping things to scale, none of the interior environments looked how I wanted them to look and every step was taking twice as long as I had to keep rechecking guides as I went along. Using the SDK however is much easier. I have experience with it, which lets me experiment with new lighting methods, triggers and sounds. The familiarity of SDK means I can create a more enriching experience and hopefully provide more depth to the abstract concept I am trying to put across within my studio work. So that is why I am choosing to abandon UDK in favour of SDK. Obviously there are still downsides to this. I originally wanted to use UDK because graphically its a much more impressive engine. Its also more widely used in the industry and the computers at the university where I study all use it. However I feel the benefits of using the SDK outway the benefits of sticking with UDK.
Thursday, 16 May 2013
Switching from UDK to SDK
In my Learning Agreement I said I was going to create my studio work in UDK, however I have decided to change to using the SDK. I am trying to create a floor of an apartment complex, where each apartment on this floor is an environmental example of an abstract concept, ie loneliness.
I was having too much trouble with UDK. I am unfamiliar with the engine and the tools at hand, even with the use of tutorials. I had trouble keeping things to scale, none of the interior environments looked how I wanted them to look and every step was taking twice as long as I had to keep rechecking guides as I went along. Using the SDK however is much easier. I have experience with it, which lets me experiment with new lighting methods, triggers and sounds. The familiarity of SDK means I can create a more enriching experience and hopefully provide more depth to the abstract concept I am trying to put across within my studio work. So that is why I am choosing to abandon UDK in favour of SDK. Obviously there are still downsides to this. I originally wanted to use UDK because graphically its a much more impressive engine. Its also more widely used in the industry and the computers at the university where I study all use it. However I feel the benefits of using the SDK outway the benefits of sticking with UDK.
I was having too much trouble with UDK. I am unfamiliar with the engine and the tools at hand, even with the use of tutorials. I had trouble keeping things to scale, none of the interior environments looked how I wanted them to look and every step was taking twice as long as I had to keep rechecking guides as I went along. Using the SDK however is much easier. I have experience with it, which lets me experiment with new lighting methods, triggers and sounds. The familiarity of SDK means I can create a more enriching experience and hopefully provide more depth to the abstract concept I am trying to put across within my studio work. So that is why I am choosing to abandon UDK in favour of SDK. Obviously there are still downsides to this. I originally wanted to use UDK because graphically its a much more impressive engine. Its also more widely used in the industry and the computers at the university where I study all use it. However I feel the benefits of using the SDK outway the benefits of sticking with UDK.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment