Difference between revisions of "Equipment/The Beast"

From London Hackspace Wiki
Jump to navigation Jump to search
(Updated training/acnode data)
(Whoops. No acnode)
Line 10: Line 10:
 
|reqtraining=no
 
|reqtraining=no
 
|trainlink=Unknown <!-- If training is required, provide a link to training signup or contact page. Otherwise leave blank. -->
 
|trainlink=Unknown <!-- If training is required, provide a link to training signup or contact page. Otherwise leave blank. -->
|acnode=yes
+
|acnode=no
 
|owner=Unknown <!-- Provide a link to owners members page if other than LHS -->
 
|owner=Unknown <!-- Provide a link to owners members page if other than LHS -->
 
|origin=Unknown <!-- If via pledge, please link to the completed pledge page on the wiki -->
 
|origin=Unknown <!-- If via pledge, please link to the completed pledge page on the wiki -->

Revision as of 10:43, 30 May 2013

"The Beast" arcade machine
Thebeast.jpg
Model Unknown
Sub-category Audio/Visual
Status Good working order
Consumables Unknown
Accessories Unknown
Training requirement no
Training link Unknown
ACnode no
Owner Unknown
Origin Unknown

This is the big arcade machine that lurks in the space.

It has indie games on it, and emulators.

It runs Windows (sad face) for perfectly sensible reasons.

Keymappings

Don't change these, as it'll break all the indie games that rely on them.

Player 1

  • Directions: Left Arrow, Right Arrow, Up Arrow, Down Arrow
  • Buttons: Z, X, C

Player 2

  • Directions: J (left), K (down), I (up), L (right)
  • Buttons: N, M, B


Launcher software

This lives at http://github.com/v21/Boinger. Any improvements gratefully welcomed, although you will need a Pro version of Unity3D to compile it. I know, sorry. One improvement would be rewriting it to not require this.

Adding games to the launcher

All games should run fullscreen at 1024 * 768 resolution. They should also survive being exited abruptly, as the launcher software isn't particularly gentle when it quits things.

The launcher reads the games avaliable from a json file called local.json, which sits in the arcade_games folder linked on the desktop. If The Beast is plugged into the network, it should appear as a Windows fileshare on machine //INDIEBOX/

The format looks like this:

{"games" :

[
	{
		"name" : "game2", 
		"author" : "me" , 
		"filePath" : "C:/Users/Public/arcade games/SumoBOSSRace.exe",
		"splashScreenPath" : "file://C:/Users/v21/Documents/My Dropbox/Launcher/Assets/tex2.png"
	}
]
}


The splash screen is the screen that's displayed on the arcade machine when cycling through the games. This works best if it's a 1024 * 768 png. Ideally it'll be exciting and eyecatching, tell people what the game is and who made it, maybe tell them what keys to press and maybe exhort them to push start. But it's up to you.

Alternatively, you could load a splash video. This needs to be in ogg format, and goes in the "splashScreenPath" variable. You also need to set the variable "splashIsVideo" to true.

I've just been dumping all the games into the arcade_games folder, accessible via the public share.

Current state

  • The left joystick is now fixed, however the tabs on the new microswitch where too wide for the spade connector so a connection was bodged with a bit of wire
  • Sound dosn't work, i've not really investigated.
  • It could do with a through clean
  • The joystick to usbhid adapter board is loose inside the cabinet and needs to be screwed down.
  • In general better cable management would be nice.

Outings 2012

  • The Wild Rumpus Thursday, 2nd of February at 93 feet east. 18:30-23:00.
  • Bit of Alright: Indie focused game design conference at the BAC. 3rd of Feb. 25ukp.
  • GameJam at LSBU 4-5th February.