So I’ve had this thought for a while. It’s been quiet here lately due to other things like work and kids and gaming taking up most of my time but I figured it’s time.
So the blog is officially moved over to GirlsCanCode.eu
You can easily subscribe there to keep following the blog for new stuff.
I will not remove any posts from this blog just yet, most of tutorials are making a way over to the new domain and I will be removing them eventually.
Thanks for the support guys ❤
So after getting my toes wet with getting involved with SynamicD, I didn’t wanna stop there. So I found Unity3D which is a 3D game engine. It’s pretty neat and although it seems somewhat limited at first to what it can do, there are workarounds for everything. I decided to learn Unity because of my timelimit, even though I looked into C++ again and some open-source render engines like Ogre3D (I might possibly go back to this at some point when/if I have more free time on my hands).
Getting Started with Unity
So when I first downloaded Unity, I wasn’t sure where to start. Like with any new program, I was quite overwhelmed with all of it. I was just playing around and following some tutorials I Googled for. Then one day I noticed software called GTGD was on sale on Steam. The screenshot of it looked like Unity, so I clicked on it, and it was! GTGD is a nice set of tutorials for people just getting started with the program. It teaches you how to make an FPS game, with rocketlaunchers, particle weapons, minecraft-like destroyable building blocks and many other things. I have to say I learned so much when following this tutorial. I even bought the sequel to it, though I haven’t got around to checking it out yet (The prices really are superlow for the good start you’ll get). So there started my road to really getting familiar with Unity.. along the way I’ve ran into several problems and this is what lead me to starting this blog. I figured other people out there could probably use help with the things we’ve tackled, the issues we’re ran into while doing it, and the solutions we came up with (and by we I mean myself and a co-worker of mine, I can’t take all the credit ;)).