So, lets get to the point here: Blowing stuff up is cool.
That statement probably will put me on a list somewhere — I mean virtually blowing stuff up is cool. In games, you hit something, and pieces of it fly apart, fragments go everywhere, cool particle effects, awesome sounds, all that feedback feels very satisfying. But sometimes, in a lot of games, that feedback is just par for the game. Like, a quick flash, some little sound byte, you reticle lights up, and it’s like, “OK, I did the thing.” but it’s not very gripping. To get that level of immersion, players need to not just see something break, but really feel it. Particles can only do so much – people want to see the result of their actions. They want to see stuff break.
The Unity UI framework comes with quite a number of tools for your disposal: Text, Buttons, Lists, Toggles, and so on. But sometimes you need a little more – something to spice up the interface you’re providing. Unity, surprisingly, has come up with a number of hooks in its UI framework, and all it takes is some simple trickery to turn these Buttons and Toggles into something completely different.
Enter Matt Graves (or “Mateodon,” his name which, I assume, dates back to his prehistoric ancestry). Matt used his dinosauric wizardry to combine multiple UI elements to create Tabs (much like the tabs in your browser (I mean, I assume they’re in your browser (What browser are you using, Internet Explorer 4?))) without a single line of code.
Give his site a checkout. He has a few good tutorials, and even has a YouTube channel.
I’m a simple man – I like creating big effects using a minimal amount of processing power. Sure, you can go and make something look “Industrial Light & Sound”-level good, but sometimes simple is better, depending on your situation. And one thing that’s gotten better and easier with age is Water Effects.
I came across Adeniran Moses Adeagbo Jr‘s blog while looking up some water normal maps, and his demo for Texture-Driven Water, where, not only does he utilize normal maps for creating some nice looking water (which, for most engines, is child’s play), but he pulls out a bit of refraction and Schlick’s Approximation to really get some great reflections out of it.
Hey, everyone! It’s been a few months since I posted on my blog like this, but that’s because I’ve been hard at work on a new tutorial for you all!
One of the more popular pages on this site has been a link I provided to ActiveState’s C++ A* Algorithm, and, while that’s good and all, it’s not really a tutorial by any means, and, well, it’s someone else’s stuff. I wanted to show you guys not only how it’s done, by the whos and whys.
OK, first off: No, I’m not dead. 2: No, I’m not a zombie. 3: Yes, zombies are considered dead. 4: I’d like to take a moment to consider a pivotal part of any game programmer’s arsenal of design patterns: The Observer.
The observer pattern, to put it simply, is an object that will only perform a specific action when another object/objects (called “the subject”) are in a particular state. A gentleman by the name of Bob Nystrom is working on an online (and soon physical) book regarding game programming, called GameProgrammingPatterns.com. In his book, he describes the fundamentals and design of the Observer pattern in a fun and simple way that can have even the most basic programmer up-and-running with Observers in no time; like a strange digital voyeur of code.
OK. That was disturbing.
Anywho, go run over to his site, and check out the other “chapters” he’s done. His book is still a WIP, but it’s already a classic. Take care!
So, my blog’s concept is nothing new: Games, programming, tutorials, the works. But everyone’s a little different and post up different content, and recently I found this blog, by Rodrigo Monteiro, where he not only posts up tutorials, game design, and even 3D game math, but he also gives his 2 cents on games and game design ideas. It’s a real great blog, and definitely one to bookmark. Here, I have a few pages of interest for you:
OK, so a while back I posted a link for a simple implementation for A* Pathfinding for C/C++. The page gets a bunch of hits, but I get a lot of people asking me to explain it. Well, it’s not my code to really explain, and I haven’t tested it out for myself. Rather than go through and make a huge tutorial, I figured I’d take the lazy route, and provide you with a resource to help explain it a bit. This page breaks down A*Pathfinding to the basics and gives a great explanation down to even the heuristics (If you don’t know that word, you’ll need this link).
So, now with this in hand, pathfinding should be easier to grasp now. Give it another go, and let me know how it turns out! Good luck!
Update: Oct. 4th, 2018
Hey! So I stopped being so lazy, and actually wrote up a tutorial for A* Pathfinding that I call KMStar! Go ahead and check it out!