Tag: audiogames

An Update

Hey guys,
Steve here.
I found this really cool, blind accessible Solitaire game for the IPhone. It’s $2.99 for the full version, but you will definitely get what you paid for. Here’s a very well done review of the game that I listened to, and if what I’ve already said about it won’t convince you to buy it, this surely will: http://applevis.com/podcast/episodes/blindfold-solitaire-audio-version-classic-card-game.
Speaking of games, I’m happy to say that I’m making a lot of progress on the racing game that I’ve been developing. It’s only been 10 days, and the player interface is complete. I performed several rounds of testing earlier to day and can’t seem to detect any bugs so far, so if any do exist they’ll likely be found once I create some opponents to race against.
Speaking of which, I’ve coded the structure for the opponents thus far, but as of yet haven’t done anything with it, and don’t think I will until tomorrow. The reason for this is that coding them will be far more complex than it was to program the player interface. The reasons for this are as follows:

  1. Unlike the player, the opponent can’t think about what decision it will make; if an obstacle appears in its path, it can’t decide it wants to move out of the way. While I could easily program it to automatically turn to avoid the obstacle, this would give it an unfair advantage over the player: one would be hard-pressed to win if the opponents that they raced against avoided every single obstacle while they hit at least one.
    Fortunately, I have an idea of how I could code the opponents’ intelligence in such a way that it’s not always perfect, though I’ll not say what it is until I’ve proven that it works.
  2. Player Interaction.
    In this game, I’d like it to be possible to slow ones opponents down temporarily by coming up behind them and bumping them. Of course, if an opponent were to intentionally bump into the player, I’d like it to have the same affect on him. In theory, coding this should be a piece of cake, but previous attempts to do similar things proved this to be falsehood. Nonetheless, I know beyond a shadow of a doubt that this can be accomplished.
  3. It will likely take a good chunk of time to program all necessary opponent actions. Despite the fact that I knew what I was doing and had very little trouble when coding the player interface, it still took a significant amount of experimentation and testing to get it fully operational. And now that I’m coding players that are out of my control during game play, it will be harder to notice smaller less significant bugs that occur.

Despite the challenges outlined above, I’m optimistic about this game. As I stated on the audiogames.net forum, I’m programming it because that is something I love to do, and I enjoy playing audio games very much.
For those of you who want to stay informed of how the development process is going, I recommend that you visit the S Quad Racing Game Page. It is where I post the daily change log, and weekly audio progress demos.
Off the topic of game creation, I had a great rest of my week. The snow storm that came in early Wednesday morning didn’t give us another day off of school, though I hardly expected it to. In fact, all of what actually fell as snow melted right after the event was finished; much of the precipitation was sleet and rain anyway.
Yesterday, though, was a completely different story. Temperatures, as they did on Monday, didn’t rise above freezing, and it snowed all day. I still had to go to school because the snow didn’t even start to fall until around 9 in the morning though. Today, while I’m sure the roads were quite treacherous, it didn’t affect me at all, that is to say, none of my plans were affected. I don’t think we’re done with winter weather yet; we could get some sleet on Wednesday. I wonder, will it actually happen?
Aside from what’s already been written here, there hasn’t been much else to talk about, though I got my 6-weeks report card and discovered that I made all A’s except for algebra, but I still made a B in that class.
Well, I’m signing off now. Have a good rest of your weekend, I’ll blog again some time next week.
Thanks for reading,
Type you later,
Steve.

Programming and Winter Storms

Hey guys,
Steve here.
Wow. A lot has happened in the last 4 days, as you can tell by reading the title of this post.
Yes, we got a direct hit from an ice storm. I’d known about this possible storm since about Thursday, but didn’t think it worth posting about as all other winter events that were possible this season missed us. This one, however, did the exact opposite.
As a result of the 1 and a half inch sleet accumulations we received this morning and a sustained temperature in the middle 20s, school was canceled today and will be tomorrow as well.
Though temperatures are expected to rise above freezing tomorrow afternoon, a second winter storm is possible tomorrow night, which could bring up to 3 inches of snow to the area. This one depends on some key factors, however, unlike the ice storm that just hit. for 1, the storm system that will be the catalyst for this second bout of precipitation must move directly over us in order for the precipitation to fall as wet snow. If it doesn’t, we could end up with just rain, or no precipitation at all. Secondly, the high temperatures on Wednesday will exceed 40, turning what accumulates in the morning into slush by the afternoon. Knowing Texas and it’s erratic weather patterns, though, this could very well change for better or worse.
In other news, I’ve once again had an active programming week. For now, I’ve set aside the word pad application that I was working on, as it is very low priority and has most of the features I was planning to implement. However, I have an actual audio game in the works now, something I’ve only attempted once before and discontinued due to lack of new ideas.
The current game I’m working on is a racing game. There’s nothing too special about it: turns, obstacles to make the game more challenging… that’s basically it. I’ve been building it for about 4 days now, and was only able to compile a half-working version tonight. Even still, this has a significant number of bugs, and lacks several features that are to be included in the actual release.
Since I’ve never worked on such a project before, the hardest part has been fine-tuning it: the opponents have to have just the right amount of speed, because we don’t want them to fall too far behind, but then again we don’t want them to go as fast as the player, as that could cause some problems, especially if obstacles are present on the map. In addition, I’m still experimenting with other things such as sound (panning, volume), initial placement of opponents, and track size.
At any rate, I’m making considerable progress on this game. It will definitely be addicting once I finish coding it.
That concludes this post. I’ll blog some time this weekend.
Thanks for reading,
type you later,
Steve.