I know newbies like me have said this alot of times but on a artist side of things that really has no proper programing knowleadge and trainning behind him. What would you think would be better in terms of me i want to be a enviroment artist (long way to go but i can dream)., Which game engine is better but i also want to slowly produce a game just as a side project to do when i not busy. Cause i feel getting into the game industry is a hard road ahead of me any tips on that.
Thanks for you time and any suggestions or tips please do tell i really want to learn.
Replies
then again, unity is quickly catching up on a lot of things UDK has
"UDK isnt really a game engine. Its UT3's modding tools without ut3 and a changed license. Unreal Engine was never designed for public use and has minimal access for modding, so using UDK for anything other than an FPS with common game mechanics is very difficult or impossible.
Unity (as well as almost all other engines targeted for public use) was designed to allow anyone to access and change any part of the engine and extend the engine and tools as needed"
- Make 3d environments and illustrate them using UDK. You will get beautiful results quite easily.
- Make the side project game using Unity. Much easier to learn.
to the original poster if you care more about pics for your portfolio --> udk if you care abotut making an interactive product --> unity
I think not.
You can write custom shaders in Unity as well.
I did, I have used UDK quite a bit and understand the pipeline and shaders and a little bit of Kismet but diving in deeper and creating an actual game besides a FPS with UDK seemed like a monumental task for someone like me with very limited programming knowledge.
I recently started developing projects with Unity and within 2 weeks I already had 3 working game prototypes (one of which I decided to take to finish and continue to work on). Also I am using uScript a plugin for Unity that you can buy from the assets store, it is really the only way I was able to create game prototypes so quickly without much actual programming knowledge. Although using uScript still requires you to think like a programmer you don't have to understand syntax which removes a huge hurdle for learning. uScript is not a proven method to create fully finished games and I could see it being quite slow if your game is overlay code heavy, but simple game concepts should be able to be created no problem with it.
Also I agree with what everyone else is saying stick to other engines if you just plan to show off your work, Unity is great if you actually want to make a game.
thats my 2 cents.
I've been thinkin about getting uScript for my future mobile game projects. Quite small games. sidescrollers etc..
Would you recommend it for small mobile games? Will it slow down fps/performance?
I would recommend trying it out, the PLE version on their site is free. I haven't yet dove into mobile stuff although I do plan to test out my project on iPad in coming weeks (although that's a bit more powerful then standard mobile.)
But as for it slowing down performance, comparing the scripts that uScript generates to something a coder would write you notice a large difference in size (Although the uScript Devs are very actively working on making them smaller and more performance friendly). I think using it to make a game will always create larger scripts (slowing down performance) but I suppose if your game is small enough that slowdown won't be noticeable.
They have PLE edition?! Nice, im definetly going to try that out.
I can use that to do a test game and if everything works alright, i will buy it.
Thanks for the info.