Main > Software Forum
CPWizard v2.63 Released
TheShanMan:
Thanks headkaze! I have it running as we speak. Not sure if I'll get a chance to check the results before I leave for work, but I'll definitely get back to you. Initial check (1942/88games) looks good though. And I'm using the Skip Clones option. :)
TheShanMan:
Looks like that's working great. One minor UI thing and one bug:
- The bezel progress bar only seems to increment on created bezels. It ought to increment when it skips a bezel too (due to the skip clone or skip existing options). It looks like it has a LONG way to go when it actually doesn't due to skipping so many. This is very minor of course.
- Remember the KEYCODE_0_PAD vs. KEYCODE_0PAD issue? I've converted mine over to the newer format (kind of forced to by CPW anyway). Well it seems to work great if the definitions are coming from a .cfg file, but for an unaltered keymap where it comes from the built in definitions (i.e. not a game cfg and not the default.cfg), it doesn't seem to work. Specifically, player 4 uses a lot of "PAD" keys but they're all appearing dimmed in games with unaltered keymaps, but games that do have an altered keymap they work fine (in one game I swapped P1 and P3, P2 and P4). Hope that makes sense. If you're confused just say so. :)
EDIT: for now I went into the default key mappings for player 4 and set them to... the default key mappings to get them to appear in default.cfg (i.e. I didn't change the mappings, just re-entered them). That solved the problem with the "PAD" keys. Still needs to be fixed though. :)
And other than that, this version did a tremendous job of creating bezels. I checked a bunch of them and they all look great! Fabulous work, headkaze! :cheers:
This actually has me thinking of creating a bunch of alternate "mini-layouts" to export as images. I think I'd rather see the CPW output than real CP's in my FE. Much more useful for swappable panels since it would give you a preview of which panel you need to install to play the game.
headkaze:
I'll fix the progress bar next release. That keycode issue is a tough one. I actually looked into that and found out the defaults in inpttype.h are defined the same as how I have them in std.ini for CPWizard. I would like to keep the backward compatibility, but according to u_rebelscum
--- Quote from: u_rebelscum on June 17, 2008, 12:04:22 pm ---Note that this change was made in 0.117u3, so for older versions of mame, the two '_' is the way to go. (I don't know how backward compatible you want CPWizard to be, headkaze.) Reason for change, now the '_' marks which keyboard (if more than one is mapped), the the number had to be moved next to the 'pad'.
--- End quote ---
So why do they still have the two '_' in inpttype.h but only one when you create a cfg file in 0.0126? How should I deal with the two different types of keycodes?
TheShanMan:
Sorry headkaze. Not sure what to suggest on that one... whether it's technically a bug in the mame source or not, it will be perceived as a CPW bug as it's ultimately your issue to deal with :(.
On a more positive note though, I created a patch to unpause the game immediately before exit which prevents the CP bezel from being left on if you pause, then exit, then restart the game. It should be easy to merge with your bezel diff. See attachment.
headkaze:
No worries, when I get some time I'll set up a CP using the keypad and install 0.117 to test both versions. Shouldn't be too hard to figure out. I guess I'll just have two key lists one for each version.
Thanks for the diff file, I've combined it with the current bezel patch and will put it on the website soon.
Glad you got the bezels working the way you like, I think it was worth it in the end :)
Can you check something for me as well, go into Options->Profiles and check for any enabled profiles that are enabled that have exe's that could be running while you run Mame. I had a user that had added a mame profile and it caused a conflict as all the Mame functionality is built in. After he removed his "mame" profile it worked again. Just thought you might have been having the same problem. I have very few reports about CPWizard having problems minimizing/maximizing Mame now, so perhaps it's just a config issue afterall.