So, you've kinda disappeared. What happened?
Long story short, life happened! Without going into too much detail, stuff happened, more stuff happened, and finally I'm back to programming on a daily basis.
Okay, so you're back from the dead, we get this. What ya doing now?
Well that’s a good question, what am I doing?
First off, I decided that I probably should learn something new to kick start myself and programming. So welcome Vulkan! And guess what? It’s actually not hard! For the last week I’ve been breezing through it like nothing! I would show, but it’s just a long wall of code. For those who don’t know what Vulkan is, it’s a 3D graphics API (something that talks to the graphics card in your computer, to make 3D images) and it’s also low level compared to older 3D graphics APIs like OpenGL or previous versions of Direct3D. And since it’s low level, it means it takes a lot more code to do the same thing. For instance, as of my code of writing this, for basic initialization and finding all the available GPU’s on a system, it takes a little over 300 line of code. This of course includes some debug code and informational code which is really just nice to have. Some of that code also rates the GPU’s, giving higher scores to a dedicated GPU over integrated.
So, 300 lines of code you say? What does that really mean? Well, in other API, 300 lines of code means a spinning cube on the screen, at least. A lot more if you're not writing your own code for math... which, if you are, have a cold shower, google math libraries for your programming language, and get one! Quaternions are not fun to code and can be easy to mess up! (If you don't know what quaternions are, that's even a better reason to get a math library!)
Oh wow, if that's true, why aren't you using other 3D graphic APIs?! As I said before, it's kind of a kick in the behind to get myself motivated to program, and nothing motivates me more than learning something deemed "difficult" and use it. This may sound that after I get a grip on Vulkan, I'm gonna drop it and be like, "NEXT!" But that won't be the case. Instead I'll be developing a game with this new knowledge, and working hard to make the best game I can! The original plan is to make a basic game framework with Vulkan, and after doing so, add assets and additional logic code to it to mass produce prototypes.
Ooh prototypes! That means you are working on a game right? What kind of game?
That. Is. My. Little. Secret 😉
First off, I decided that I probably should learn something new to kick start myself and programming. So welcome Vulkan! And guess what? It’s actually not hard! For the last week I’ve been breezing through it like nothing! I would show, but it’s just a long wall of code. For those who don’t know what Vulkan is, it’s a 3D graphics API (something that talks to the graphics card in your computer, to make 3D images) and it’s also low level compared to older 3D graphics APIs like OpenGL or previous versions of Direct3D. And since it’s low level, it means it takes a lot more code to do the same thing. For instance, as of my code of writing this, for basic initialization and finding all the available GPU’s on a system, it takes a little over 300 line of code. This of course includes some debug code and informational code which is really just nice to have. Some of that code also rates the GPU’s, giving higher scores to a dedicated GPU over integrated.
So, 300 lines of code you say? What does that really mean? Well, in other API, 300 lines of code means a spinning cube on the screen, at least. A lot more if you're not writing your own code for math... which, if you are, have a cold shower, google math libraries for your programming language, and get one! Quaternions are not fun to code and can be easy to mess up! (If you don't know what quaternions are, that's even a better reason to get a math library!)
Oh wow, if that's true, why aren't you using other 3D graphic APIs?! As I said before, it's kind of a kick in the behind to get myself motivated to program, and nothing motivates me more than learning something deemed "difficult" and use it. This may sound that after I get a grip on Vulkan, I'm gonna drop it and be like, "NEXT!" But that won't be the case. Instead I'll be developing a game with this new knowledge, and working hard to make the best game I can! The original plan is to make a basic game framework with Vulkan, and after doing so, add assets and additional logic code to it to mass produce prototypes.
Ooh prototypes! That means you are working on a game right? What kind of game?
That. Is. My. Little. Secret 😉
Conclusion
Sorry for not saying anything for the longest time! I'll starting to get life back in order so the goal is that you guys will hear from me every week! I'm also planning on tweeting more often at @RestartLaterS Hopefully every day, but who knows!
P.S:
The old content has been taken down from view. I will review them at a later date and see if they're up to the quality I wish RestartLater Studios to have. They will, however, stay unedited. If, for some reason, people really want the 5 posts up, I will put them up again (rather back on here, or copy them to a new blog).
