Luca

• Audio is 98% functioning, with a few optional additions to be completed
• FullScreen has been found and implemented
• Collision has also gone around the walls of the field and the goals
• The ball now deletes itself and respawns at the center of the field after a three second delay upon entering the goal
• The friction/mass and all that mess has been mostly tweaked to give the ball a fairly realistic response to being “kicked”
• The menu bugs have been fixed
• The score on the screen now increments whenever Bob scores a goal
• The score bugs have been fixed

And all of that, save for the triggers created to keep track of the score, has been done since Tuesday. So…all in all I’d have to say it’s coming along really well.

Next few things we’re working on:

• Texture for the walls (currently invisible, but with collision to keep Bob and the ball on the field), coming soon
• Two-player, hopefully coming sooner

I’m looking forward to what else we can accomplish with this. It’s been stressful, that’s for sure, but it’s certainly been fun at the same time.

`Elyse 007

It was not until that fateful day, April 27, 2010, that a slight miracle occurred. I noticed that Bob, when standing on a specific pinpoint of a spot on the field (the exact center, of course), would no longer sink. Take one step in any direction, and there he went, gravity taking over. But stay on the pinpoint, and all was well. That was when I decided that I did have a functioning collision box, yet it was hiding. Hadn’t quite occurred to me yet that this just might be TorqueX’s fault. But to make a long story slightly less…long, I’ll sum it up. The TorqueX Builder had been creating a collision sphere (a sphere…for a rectangular field ), and had given it a default radius of .65. Yes, .65, a pinpoint on our field. And it didn’t bother to tell us about this collision sphere, either. No, it simply buried itself in the Torque generated code and proceeded to overwrite any collision box I so desperately added over the weeks.

But now that the culprit had been found, I created a collision box out of the sphere and gave it the correct dimensions, and voila! Instant collision detection. However, to add insult to injury, the Builder continues to overwrite my carefully constructed box every time I save something from there. Evil of the highest degree, let me tell you.

So yes, it was a rather momentous occasion. So momentous, in fact, that I forgot to post about it. So here I am with the good news. A little late, but better than nothing.

`Elyse 007

Luca

Luca

Luca

http://bert.netsal.selu.edu/~jmorrison/teamdoubleo.html

-Johnnie

Fantastic. We finally have something to reference with this terrible engine. I suggest we all look through these to much better understand what we are working with. Not a whole lot of time left. We need to get this stuff going.

Luca

So the next obstacle is figuring out how to code these objects once they’ve been placed into the game. Of course, one brilliant idea I just had was to place the field into the game via the Builder, but not place Bob via the Builder. Hmm…Bob the Builder…who knew? Anyway, if I could get the field positioned beneath the Bob that I manually wrote, perhaps using this dumb Builder to place Bob wouldn’t be necessary. Ah-ha!

Well, it’s an idea, and I’ll go test it out. But hopefully all will come together soon, one way or another. At least we’ve gotten the field into the game…that’s a dream come true. Converting that stupid thing was a nightmare. Eric was able to help us out in the end, and now all is well where that’s concerned.

`Elyse 007

It’s an awesome step forward, though I just wish we could get the field imported into the game. That’s the biggest thing I’m worried about at this point. Hopefully that’ll happen soon.

`Elyse 007