Main > Software Forum

CPWizard v2.63 Released

Pages: << < (42/145) > >>

TheShanMan:

Doh! I forgot the attachment.

headkaze:


--- Quote from: TheShanMan on June 15, 2008, 11:58:53 am ---Hey headkaze, I noticed that my simpsons panel wasn't "enabling" some of the buttons so I did some investigation this morning, and it appears that any of the "pad" keys (e.g. keycode_0_pad) aren't enabling in CPW, and I'm using 1.78. Can you confirm? I've spent a good deal of time investigating my mappings within mame, looking at the cfg files themselves, and examining my layout in CPW and I can't come up with any explanation other than a bug in CPW. Here is my default.cfg and simpsons.cfg files. I'm running mameui .125.

Also, I'm still holding out hope that at some point we can figure out that pause problem I'm having. I don't blame you if you don't want to expend more energy on it, but I don't suppose there is ANY more debug logging that could be added to help track it down? I got to thinking about it more last night because I was playing around with saving and loading states in mame, and whenever you hit save state, it simultaneously pauses mame. In that case, CPW came up EVERY time, yet it doesn't when I pause with "P" (except for the very 1st time). So that made me think maybe it's caused by my ipac using P as the shift key. I disabled that but it made no difference with CPW. What do you think? Does that save state pausing spark any ideas for you? I would still prefer live CPW over bezels, so I won't let my hope for that die. :)

--- End quote ---

I think I found the problem with the key pad not working. In your simpsons config you have KEYCODE_0PAD, KEYCODE_1PAD, KEYCODE_2PAD etc. But in CPWizard I have them defined as KEYCODE_0_PAD, KEYCODE_1_PAD and KEYCODE_2_PAD. I've changed the keycodes in CPWizard so that should be fixed for next version. For now you could edit your layout file in a text editor changing the keycodes should fix it.

I'm still interested in your pause problem, but can you try using my bezel patch from the website and compile a new version? Since you created your own patch manually it might be a problem related to that. So if you can confirm using my bezel patch if the problem still occurs at least we can rule that out.

I'm looking at adding some extra debugging that will output which window is foreground (kinda like the foreground plugin you wrote for MaLa).

TheShanMan:


--- Quote from: headkaze on June 16, 2008, 10:31:44 am ---I'm still interested in your pause problem, but can you try using my bezel patch from the website and compile a new version? Since you created your own patch manually it might be a problem related to that. So if you can confirm using my bezel patch if the problem still occurs at least we can rule that out.

--- End quote ---

I'd be glad to, but what do you mean "created your own patch manually"? I use the hiscore patch and your bezel patch, but I use Mame Compiler to apply them and build mame. I am using mameui32, so if you think that could be a factor I will build straight command line mame.

ddrtist:

Sorry if I sound like a complete noob, but I have not seen this question asked in this thread.

CPWizard looks awesome for all of it's features, but does it support GUI MAMEs?  I use MAMEPlus .122 currently with it's accompanying romset.

u_rebelscum:


--- Quote from: headkaze on June 16, 2008, 10:31:44 am ---I think I found the problem with the key pad not working. In your simpsons config you have KEYCODE_0PAD, KEYCODE_1PAD, KEYCODE_2PAD etc. But in CPWizard I have them defined as KEYCODE_0_PAD, KEYCODE_1_PAD and KEYCODE_2_PAD. I've changed the keycodes in CPWizard so that should be fixed for next version. For now you could edit your layout file in a text editor changing the keycodes should fix it.

--- End quote ---

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'.

Pages: << < (42/145) > >>

Go to full version