koobas.hobune.stream
Learning process
I'm sure you get a lot of these questions, but here it goes.
I've been playing around with unity, UDK and a few sprite based game engines for the past few years and decided to stop fiddling around and actually try to do something. I'm trying to decide the what way the learning process should flow. Should I learn the basics of 3d modelling first then learn the code while I'm progressing with unity or code first then learn modelling as I'm learning unity?
I'm proficient with Google sketchup, not that it really helps.
Thanks and I hope my question ins't too vague.
Well my advice would be to learn coding first, simply because that's what really matters if you want to make a game (IMO). Say you want to make an angry birds style game, it'd be better to have all the physics and other code laid out, you could even play with primitive shapes and still get a good, playable demo going. But this really is completely up to you, depending on what you would want to do as a job later: one, the other, or both.
I agree. Ultimately, you need to be at least somewhat proficient in writing code to make a game. Plus, there are TONS of really, really good free and low-cost 3D assets on the AssetStore, which, in many cases, are production quality. Obviously, being able to produce art assets from scratch is a good skill to have, but make a game, you're going to need to code.
That was the direction that I was leaning but just wanted to be sure. I guess my next question would be is is it better to learn C# separately from unity or try a unity based C# tutorial?
$$anonymous$$y recommendation is that you learn C#, by writing code inside of Unity. For starters, the latest release of .NET is 4.5, but the version of $$anonymous$$ono framework that Unity uses is only compatible through .NET 3.5. That means that lots of the fancy C# features in the latest releases of the core .NET libraries won't work in Unity. Also, learning C# through Unity will allow you to familiarize yourself with the UnityEngine library methods, as well as the popular patterns that you'll find in Unity code.
I would use both $$anonymous$$SDN and Unity Script Reference depending on what you are trying to learn at that time.
