Main > Software Forum
CPWizard v2.63 Released
DCsegaDH:
--- Quote from: TheManuel on October 05, 2011, 09:03:44 am ---Perhaps you are using MAME defaults for P2 and have remapped P1?
If so, make sure you have created input labels for P1 controls in your layout. You have to specify input labels that match your physical controls and mapping. Let's say you have a keyboard encoder and have programmed it this way:
P1 Up: I
P1 Down: K
P1 Left: J
P1 Right: L
In that case, you have to create a label for each joystick direction and place them in the appropriate places around the picture of the P1 stick in your layout. For each of the above, under properties, you have to select "Key Code" under "Code Type" and then KEYCODE_I, KEYCODE_K, and so forth.
Then, you would link your joystick picture to one of those Key Codes, as explained before.
You might already be beyond these basics but I'm throwing it out there, just in case. I'll try to help you get it running as much as I can.
--- End quote ---
Thanks so much for telling me this, I'm trying this on just on my office computer. I'm probably going to wait until my Mame cabinet is done to do this, but I think I got it.
headkaze:
Thanks for helping out Manuel.
For the users who have reported HiToText crashing please report the bug to this thread.
Also to the guy who asked for more GROUP codes, check CPWizard\Data\InputCodes\GroupCodes.txt. It should be fine to add in more groups there.
TheManuel:
Feeding from the other discussion, and in an effort to keep things organized and easy to find, I've compiled here a list of the issues, potential bugs or feature suggestions that I've identified (some might be my ignorance of how CPW works), for whenever you find time again to look into them. Again, not an attempt to prod you on, simple trying to save you the time of going through all the threads.
Possible issues:
1) Mame screenshot feature as background when CPW displays, not working for everybody.
Background info in this post and the 4 that follow it.
2) CPW showing default control layout, rather than neogeo layout when there is a neogeo entry in the ctrlr file but individual NeoGeo game entries in the controls.xml file
Back ground info here, and attached ctrlr.cfg and controls.xml files two posts after that.
3) CPW can't pause MAME when multithreading is enabled in the MAME ini file.
MAME ini file entry:
#
# WINDOWS PERFORMANCE OPTIONS
#
multithreading 1
4) When a game does not have an entry in the controls.xml file, CPW shows buttons with generic labels but does not show anything for joystick directions, so joystick fades, unless linked to PLAYER_1_JOYSTICK.
Linking to PLAYER_1_JOYSTICK has the undesired effect that if MAME has joystick entries for a game that is all buttons, like phoenix or asteroids, then the joystick will be shown by CPW, even if only buttons are mapped in MAME ctrlr or cfg.
Background info here and in the few posts before that one.
5) If easy to implement, please consider adding some sort of key-repeat code for non-USB keyboard users. I have an old iPac through PS/2, and holding down the down direction in the joystick does not scroll down the lists in CPW's info screens (history.dat, etc.). However, it works fine in HS. I've noticed that CPW does not take action on key presses, until the key is let got, which pretty much kills that functionality.
I hope this helps.
headkaze:
Yes thanks it does! :cheers:
TheManuel:
At the risk of incurring your Mitsurugi Damascus Sword wrath, I've added yet another request to the list above.
Regards.