|
|
| Line 21: |
Line 21: |
| This is the big arcade machine that lurks in the space. | | This is the big arcade machine that lurks in the space. |
|
| |
|
| It has indie games on it, and emulators. | | It has MAME and a large amount of ROMs, with a relatively easy to use front-end. |
|
| |
|
| It runs Windows (sad face) for perfectly sensible reasons. | | It runs Windows (sad face) for perfectly sensible reasons. |
|
| |
|
| == Keymappings == | | == Current state == |
| | |
| 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 === | | === TL;DR === |
| * Directions: J (left), K (down), I (up), L (right)
| | The machine is currently operational, turn on the wall socket switch in the hall path and give it a go! Report to the mailinglist when something breaks down, or contact [[user:Yvanj]] |
| * Buttons: N, M, B
| |
|
| |
|
| | === Elaborated version === |
| | The machine currently consist out of a Dell i5 desktop running Windows 7. |
|
| |
|
| ==Launcher software==
| | It has the following software installed: |
|
| |
|
| This lives at [http://github.com/v21/Boinger http://github.com/v21/Boinger]. Any improvements gratefully welcomed, although you will need a Pro version of [http://unity3d.com/ Unity3D] to compile it. I know, sorry. One improvement would be rewriting it to not require this.
| | * TeamViewer (for remote hands, or, hands next to it without digging for a KB/mouse) |
| | * MaLa frontend [[http://malafe.net/]] |
| | * MAME [[http://mamedev.org/]] |
| | * Windows 7 |
| | * Google Chrome |
|
| |
|
| ==Adding games to the launcher==
| | A connected keyboard has been hidden behind the coin door for emergency purposes; the cable should be long enough to pull it and use it. |
|
| |
|
| 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 hardware is fully working now, however: |
|
| |
|
| 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/
| | * It has a cheap crappy PC speaker ruining gameplay |
| | * We don't have enough inputs to use all of the options in the menu system :sadface: |
|
| |
|
| The format looks like this:
| |
|
| |
| <pre>
| |
| {"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"
| |
| }
| |
| ]
| |
| }
| |
| </pre>
| |
|
| |
|
| |
| 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 ==
| |
|
| |
| * New, more powerful machine would be good, core2due+. (currently Pent4)
| |
| * Jacks for headphones on the underside need installing so people can play without distracting the rest of the space
| |
| * <strike> Wiring harness for LEDs needs finishing </strike>
| |
| * <strike> Shuttle PC power supply dead, needs replacing </strike>
| |
| * <strike> New buttons and joysticks installed, side art trimmed and cleaned, parts resprayed </strike>
| |
| * <strike> Both joysticks broken again, needs replacing, CRT replaced with LCD, new sound system installed </strike>
| |
| * <strike> 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 </strike>
| |
| * <strike> Sound dosn't work, i've not really investigated. </strike>
| |
| * <strike> It could do with a through clean </strike>
| |
| * <strike> The joystick to usbhid adapter board is loose inside the cabinet and needs to be screwed down. </strike>
| |
| * <strike> In general better cable management would be nice. </strike>
| |
|
| |
|
| == Log == | | == Log == |
| Line 93: |
Line 57: |
|
| |
|
| The logitech 2.1 system that is installed in the cabinet has a busted amp/sub unit. The satellites work (just) but are naff without amplification. Have installed the old Google TV speakers temporarily, removing the old ones will involve taking the cabinet apart. One of the (mains!) cables that feeds the neons has been yanked out and is hanging loose. Unplugged. Fixing this will involve taking the cabinet apart, too. Tidied all the cables in the back, removed unused stuff. Currently running by the hackspace front door for opening evening. --TimRTerrible 13/08/2013 | | The logitech 2.1 system that is installed in the cabinet has a busted amp/sub unit. The satellites work (just) but are naff without amplification. Have installed the old Google TV speakers temporarily, removing the old ones will involve taking the cabinet apart. One of the (mains!) cables that feeds the neons has been yanked out and is hanging loose. Unplugged. Fixing this will involve taking the cabinet apart, too. Tidied all the cables in the back, removed unused stuff. Currently running by the hackspace front door for opening evening. --TimRTerrible 13/08/2013 |
| | |
| | Updated the Wiki page with the current situation --[[User:Yvanj|Yvanj]] ([[User talk:Yvanj|talk]]) 21:41, 20 March 2015 (UTC) |
|
| |
|
| == Outings 2012 == | | == Outings 2012 == |
