It's awesome when people set up their own rig to run this stuff. I don't set it up on windows for the rigs I build, so I didn't have the details for a step by step like this.

Added this to the wiki - Thanks much Brian!

The position of the window has to be controlled in software because it's frameless (nothing to grab & drag), since it doesn't quite cover the full area in view. So the settings are in the service menu in the standard settings. The default offsets for the recommended setup (15.6" LCD, 1280x720 resolution, 10 pixel dots) are just about perfect for the mounts I send mine out with, if you're rigging your own you may have to adjust.

Regrettably pygame doesn't allow for moving the window once it's created, so after adjustments you have to reload the game to see the new position. With my setup, it does that when you exit the service menu. You might need to exit and restart depending on how you set things up. Just keep in mind that whatever you have the pixel size set for is how many pixels will move the display over one row of dots - so if you're using 10 pixel dots and it looks like it should move about 2 rows over, move it 20 pixels and see how it looks.

Edit: I should mention that you can do this from the keyboard if you have a proper keymap in place, as you can run the game with "fakepinproc" to get the window and then adjust it with the menu using the keys. However you wouldn't really know where your position should be until you get it behind the speaker panel anyway.

Keymap goes in the config.yaml in your ~/.pyprocgame directory.

The part you need for using the service menu is:

keyboard_switch_map:
# enter, up, down, Exit
7: SD8
8: SD7
9: SD6
0: SD5

Then you can use the numbers to use the service menu.

Edit: Note, the spacing is important in the yaml file - the forum kills the spacing. Each of the map lines should be indented 4 spaces. The "keyboard_switch_map:" line is not indented.

Edit edit: http://soldmy.org/pin/ccc/keymap/

You need the altered dmd.c - not just updating the date on your copy. You have that, right?

http://soldmy.org/pin/ccc/files/dmd.c.zip

it's dying because it can't find the audio asset on the last line of that dump, so either you're missing that one, or you're missing all of them. The "No audio device found" thing is often a false error.

Oh, my bad - that's not a missing sound file problem. It's an actual code problem. The base.py is looking for an asset named quote_beerMug and it's not finding one.

This isn't a bug, something is wrong in your setup. Something didn't copy right, or isn't set up right. Working fine for everybody else with current code.

For anybody playing along at home .. or finding this thread on a search later because they're having problems ...

It turns out the problem MightyGrave was having was exactly the one stated by the output -- the mixer init failure. I was incorrectly remembering that on some setups pygame throws a "no sound device found" (or similar wording) error that is different than the mixer init which is not a show stopper. The mixer init is an actual problem, and once he worked that out, now he's running the game. I don't know the details of what he needed to do to fix it, maybe he'll post that followup.

http://soldmy.org/pin/ccc/index.php/Recompiling_PyPinPROC_for_CCC_Color_Support

If you're going to run it on a stock DMD, that's not needed. Only the LCD output for color display requires the recompile.

Yeah, that big whitewash is NOT what the DMD re-compile fixes. I'm not sure what's up there. Could try clearing the dmd file cache in your .pyprocgame folder (just delete it)