Le bartop que je fabrique est pour 2 joueurs avec 2 joysticks, 6 boutons chacun, 2 boutons players et 2 boutons de contrôle hyperspin.
Je me suis retrouvé confronté au problème d'Hyperspin qui ne gère pas bien les Joystick (dès qu'on veut changer de jeux, la roue s'emballe et ne s'arrête quasiment jamais).
J'ai vu sur le site officiel que le moyen de régler ça était d'utiliser un Keymapper comme xpadder. J'ai réussi à arranger Hyperspin, à faire des profils différents pour chaque émulateur sauf MAME.
Comme vous pouvez le voir, il est tard et ça fait des heures que je cherche un moyen de faire fonctionner xpadder avec MAME et Hyperlaunch 2.25c (le dernier).
J'ai suivi le tuto officiel que voici :
HOW TO USE KEYMAPPER:
ONLY Xpadder (2012 versions) and JoyToKey (v5+) and Autohotkey scripts are supported options for keymapper functionality. Will not work with JoyToKey v3 or below.
Create a folder in Hyperspin\ called "Keymapper Profiles" (this can be changed in Settings.ini). This will be where you place your keymapper profiles. The folder structure works like this (using MAME as the example system):
Hyperspin\Keymapper Profiles\ - place your Hyperspin profile here (ex. Hyperspin.xpadderprofile) - This profile is only "needed" if you have to remap controls while browsing in Hyperspin.
Hyperspin\Keymapper Profiles\ - place your default profile here (ex. default.xpadderprofile) - This will be your main profile and used for all systems you don't make system-specific profiles for.
Hyperspin\Keymapper Profiles\MAME - place your system MAME profile (ex. MAME.xpadderprofile) here and any MAME rom-specific profiles here. (ex. 88games.xpadderprofile).
The profile chosen when you launch a game works like this: It will first look for a rom profile, if not found, it looks for a system profile, if not found, it looks for the default profile for all systems. Lastly, if no default profile, it will load the Hyperspin profile. If no profiles are found, it will error out.
So to recap, the order profiles are loaded are:
- Game specific profile
- System specific profile
- Default profile
- Hyperspin profile
On exit of emu, HyperLaunch will close or unload your keymapper if no Hyperspin profile is found. If you have created a Hyperspin profile, it will load it.
Xpadder Setup:
- Run it and follow the initial setup prompts.
xPadder multi-player support:
If you want to load multiple profiles, one for each player (up to 4), you simply have to add another profile with the same name, but add a [p#] after it. For example, you would load Mame.xpadderprofile to player 1 and Mame [p2].xpadderprofile to player 2. Don't forget the space. For 4 players you would have "Mame" "Mame [p2]" "Mame [p3]" "Mame [p4]". This works for all 4 profiles in the hierarchy above.
If you want to install one of the keymappers, use whatever one you like, but xpadder is a better choice.
JoyToKey Setup:
- Start JoyToKey in a minimized mode
- Hide icon from taskbar when minimized
Autohotkey Setup:
- Create a new ahk file and place your remaps you want to use in ahk code. You can find more info about how to remap via ahk here. A list of support ahk keys can be found here.
- Save the file as the game, system, hyperspin, or default profile you want HyperLaunch to load it for.
- So let's say you want to remap a to b and c to d using ahk for the rom "Mario" for Mame. You would create a "Mario.ahk" in "Keymapper Profiles\Mame\" and in it you would find the following remaps:
Code:
[ltr]a::b
c::d[/ltr] - You would also have to set keymapper=ahk either as your global setting in Settings.ini or only specifically for Mame in the Mame.ini.
INI Setup:
In order to turn on the keymapper support, we use a 2-part system to enable either global, or system specific, user settings. HL2 will add these default settings to your Settings\Settings.ini:
Code:
[ltr][HyperLaunch]
Keymapper_Path=
Keymapper_Profiles_Path=%A_ScriptDir%\Keymapper Profiles\[/ltr]
Note: The Profile Path will get translated to read out to your Hyperspin folder when you look at it.
It will also create these in Global Settings.ini file like so:
Code:
[ltr][HyperLaunch]
Keymapper_Enabled=false
Keymapper=[/ltr]
Finally, it will add these system-specific ini keys to the systemname.ini:
Code:
[ltr][exe info]
Keymapper_Enabled=use_global
Keymapper=use_global[/ltr]
What this does is, as long as you have "use_global" set in any of your system.ini's, it will use the value from your Settings.ini. If you want a specific system to have its own setting, just change "use_global" to a same value type as found in the Settings.ini.
Definitions:
- Keymapper_Enabled - Iif true, enables keymapper support for all systems that have "use_global" set in their systemname.ini
- Keymapper - Default is blank, but choices are "xpadder" or "joytokey" or "ahk"
- Keymapper_Path - Default blank, this is the path to your keymapper exe, for example C:\Hyperspin\Utilities\xpadder\xpadder.exe
- Keymapper_Profiles_Path - The path all your keymapper profiles are stored, default is Hyperspin\Keymapper Profiles\
Note: If you have Keymapper enabled for a system, you need to make sure you have one of the 4 profiles from above located in your Keymapper_Profiles_Path for all games. So lets say you have xpadder enabled for Mame and made only a Mario Profile, but don't have a default, hyperspin, or Mame profile and you decide to play Gradius, you would get an error that you have Keymapper enabled, but could not find a valid profile. If you don't want to remap any keys for any other Mame games, you can just create a blank profile called Mame.xpadderprofile and you won't get the error anymore.
Tips for those having issues working with Keymapper support:
- Remove any profiles you have saved in the folder that xpadder.exe resides in.
- Make sure xpadder it is set to load the last used profile on Windows startup (which will always be Hyperspin unless you load up a different one after exiting HS).
J'ai lu sur plusieurs forum que MAME ne reçoit pas les commandes virtuelles telles que celles de xpadder. Pourtant le tuto officiel détaille explicitement comment ajouter un profil pour MAME, c'est que ça DOIT marcher!
J'ai remis en cause la vétusté de mon MAME et téléchargé la dernière version de MAME Plus (0.149). J'ai retéléchargé les bios au cas où et remapper mes contrôles dans MAME.
Hyperlaunch commande correctement Xpadder, quand je lance un jeu MAME, je fait ALT TAB pour aller voir sur quel profil il est, je fais même des tests dans un bloc note, tout est bon! Mais ce fichu MAME refuse de recevoir les commandes qui marchent elles au clavier.
Que faut il faire pour que ça fonctionne? Y a-t-il une autre solution, plus simple, toute bête que je ne connais pas?
Merci d'avance de votre aide
