#samurai robots

[harleyhuang]

*inhales* samurai ninja robots! *exhales*

[trucdesigns]

Master and Apprentice

Now that I have the controller and both robots in place, I could finally get the game tested by a lot of people at the exhibition. The feedback I got, which I knew that I would get, was that the Master was to fast. I think that a “teacher demonstration” button that is slower will help and of course labeling the controller so that people know what the buttons do. After some button pressing the testers figured out how the controller worked and wanted to try to copy the master, but he was still too fast for anyone to follow (yes even for me).

This is what it will look like when the player presses the finish button to see the result of their combos. When I fix the code and add the slower teacher mode I will have to give it another test to see if it give me a result that kind of look like this video. Even though I have had my presentation and delivery, I still feel that this “game” is far from finished and it was only a little part of the game that I actually wanted to make, which was a fencing game between two robots. But now that I have a good start I feel that I have to keep going and finish what I started, when I will get to finish it I do not know, hopefully soon.

[trucdesigns]

Not exactly nsync

Instead of having the player input the combo that they wanted to do with the potentiometers and buttons, I switched the potentiometers back to buttons only and I made it possible to see the moves instantly when you pushed a button, and the “go” button will now save the position that the robots have at that moment instead of showing you the move that you just guessed you did, the “go” button is now the “save position” button. With this controller I think that I finally found the right type of controller that the game needs. But these changes made the arduino slower because it had to check if a bunch of boolean statements were true or not. To fix this I will have to recode some of the functions in my code. Or maybe the skynet code and Asimov's three laws of robotics is mucking up the robots?

[trucdesigns]

Almost time for delivery

As deadline is creeping closer and closer I had to make a decision, continue trying to make the fencing work or use what I had to make something a bit different but still kept the theme of the game.

I decided to make this simon says type game, simon says is a memory game that uses buttons that light up and sounds that the players had to remember and press in the right order as long as they could. With this concept I would abandon the fencing concept, but I thought about how this could be some kind of tutorial for the players to teach them how the controller and how the robot's movements was. Some might say that I copped out but I had to do the best I could with what I had at the moment and have something that people could test without me worrying about the robot ripping each other apart after a few demonstrations at the exhibition on friday. Although this will only be a little part of the game I think this would add depth to the game if I ever get to finish the it someday. 

[trucdesigns]

Mind cleanse

Yet again I had to keep my mind busy while I tried to figure out how to solve the snagging problem so I made these figure that I will attach the servos to.