Getting just a little bit closer to the end of the level development process! Though you can see from my other videos that my game is a 3rd person RPG, I wanted to change it up for a level. It was a good deal of extra work but I think this one is beginning to shape up pretty nicely. Figuring out the eyeball enemy dude was a real headache though.
For those of you wondering, I got the bendy tube effect by using the Curved World Shader asset from the Unity Asset store. It’s one of the few assets that I haven’t made myself simply because writing shaders is for wielders of arcane magic (An art form I was not blessed with). It was a little tricky getting the hang of it, but I think it looks pretty cool.
Hey guys. So I last week I joined a community of game developers called Game Dev Underground. Tim Ruswick, the guy who put the whole thing together, frequently posts videos on youtube about game development and things related to it. He seems like a genuinely good dude and is very charitable with his insight to the industry.
Hey all, just wanted to say what up and provide you with a quick snapshot of the progress on the current level. For the most part, the tedious work of white box testing is over and done with and I’ve also dialed down the boss mechanics, so it’s time to start adding some detail! I literally just finished modeling the last section (of 3) about an hour ago and just slapped a couple quick materials on to see how it feels. What do you think?
I don’t know about you guys, but I’m pretty excited for 2018. Initially, I was feeling pretty meh about our prior year, but after taking a closer look, I realized that there was some stuff to be happy about; at least in my circle of influence. After reviewing this very blog, it dawned upon me that I actually got a fair amount of poop done in the last 365 days.
Well actually, no quaternions. At least not this time. I just needed a third complicated sounding thing for the title. The other two are legit though. This week I began a new level with a puzzle. Worry not, player, you won’t have to be a rocket appliantist to solve it. But good God! It was a pain in the rear to set up.
So yesterday, I finished another level for my game. I’m pretty happy about it as it’s a good milestone to achieve. (I actually thought I finished it on Friday, but my roommate broke it in a run through on Saturday. So I fixed the issue Sunday and added the last little bit of polish on Monday.) Today however, I found myself in a spot that I don’t necessarily like being in… brainstorm day.
Hey all! I know it’s been a little bit since the last time I provided an update. It’s just that I’m pretty sure nobody reads these things so I’ve been getting lazy. Nevertheless, I’ve decided that I shall continue to forge these historical records as journal entries (hence the title). Anyway! The new level is coming along quite nicely and surprisingly enough, I’m actually ahead of schedule. With persistence and a bit of luck, I should be finished with it by the end of the month and have a bit of time to celebrate Thanksgiving.
Team morale is good. Everyone except for Sandor (the dog) seems to appreciate the recently bad weather as a legitimate, albeit convenient, excuse to stay inside. The stormy weather has resulted in a boost in productivity and has pushed things back on schedule. As expected, there are still a few moments of panic here and there, but as of late, the beast of anxiety seems to be rearing its ugly head with less frequency.
On another note, some of you may recall that I recently posted a short video of the previous level on youtube, codenamed KL6. Although that level was 99% complete at the time I made the video, there was still one nasty little bug in the boss fight that I hadn’t figured out. It was damn near impossible to reproduce and would only happen very rarely. This made it very difficult to figure out if it was fixed or not when I made changes to the code. I had put it on the back burner, but the other night, I decided to revisit the issue and not leave my chair until I figured it out…
Many moons passed and it wasn’t till the wee hours of the night that a single line of code nestled deeply within a coroutine caught my dreary eye. The function was meant to quickly turn the boss to face the player in certain situations. The boss would theoretically rotate until the angle between its forward vector and the vector between the boss and player became less than 3 degrees. To test the function, I changed the value from 3 to a negative number. This would be an impossible value to attain because the Vector3.Angle() function only returns positive values. In other words, I was intentionally breaking the function to see if it would produce the same bug that I had been encountering in the game. When I fired it up, voila! The bug was now happening consistently which told me that I was on the money. To make a long story short, it turned out that the broken function was conflicting with another rotation method being used by the boss. I made it so that only one would be called at a time which fixed the issue. Though I was quite tired, I happily accepted the victory and triumphantly passed out at my keyboard.
Anywho, enough of all that. Here’s a couple more goodies!
Here’s a quick peek at what I’ve been working on over the six weeks or so. If you have any thoughts/opinions/questions, hit me up here or on twitter @CWDgamedev Thanks!
Back with a sneaky peeky at the new level! It’s coming along nicely 🙂