Main > Software Forum
New ControllerRemap utility, 7/11/13 update available (Version 0.0.11)
lemonflavoured:
I've just a quick question on the way this utility works. I have 2 trackballs in my cab which love changing ID so for instance trackball 1 is showing as mouse 4 in mame and on reboot it becomes mouse2. Does this utility simply rebind everything that was mouse 4 to mouse2 and just keeps the mame bindings up to date or does it perform some other kind of trickery where make still sees trackball 1 as mouse 4?
Connorsdad:
--- Quote from: MydknyteStyrm on November 26, 2013, 02:22:56 pm ---I was wondering if this utility was necessary if I was planning my cab to NOT have any control unplugged. Everything I put in is staying. Does Windows change my ID's on powering up and down? Thanks!
--- End quote ---
I have each aimtrak and my spinner/trackball plugged into different USB ports/USB Controllers on the MB, as long as I don't unplug them the id's stick, most of the time. Roughly 1 out of every 5 boots, at least one of the id's has changed but if I reboot, the id's return as before. If you plan on using mame only then by all means this app is the best option, but, if you plan on also running model3/model2 emulators I would suggest trying out the different port trick.
eustonr:
Hi,
I've had the issue with Mame, and USB controllers that ControllerRemap is designed to fix - My system consists of:
2 Ultra Sticks
2 Aimtrak lightguns
1 UTrak Trackball
1 MinI-PAC Board
I dont use the UTrak controller for the trackball - to save USB ports, I wired the trackball into the Mini-PAC board. The MiniPAC has an onboard mouse controller (designed for Trackballs), so a separate board becomes unnecessary.
The issue I have is :
ControllerRemap identifies the 2 Ultra sticks, and also the 2 Aimtraks - but it doesnt see the Mini-PAC.
That would be fine, but all 3 are USB controllers, and all 3 register as mouse controllers to Mame.
When I first installed ControllerMap and configured it, it worked ok for a while. Then after a few reboots Gun 1 stopped working, and Gun 2 was being seen by Mame as Gun 1. Drove me nuts for a while - until I realised that the Mini-PAC was being seen by Mame as the 3rd mouse controller. The 2 Ultra Sticks were being seen first (and always seemed to be) The lightguns were being seen as the 4th and 5th controllers.
But controllerremap ./list only shows the 2 sticks and 2 guns. ControllerRemap was therefore mapping (correctly) stick 1 and 2 to controller 1 & 2 - but incorrectly remapping the guns to controllers 3 and 4. (instead of 4 and 5). It worked at first because the trackball (MiniPAC) was being seen last on those reboots where the setup worked..
After a few frustrating hours, I finally worked it out - and put in a temporary work around. I am able to force the MiniPAC to being seen last by windows on every reboot, by plugging the MiniPAC into a USB hub, and plugging that hub into the last numbered USB port on my motherboard. It works for now, but it would be nice not to have to use a hub in my Cabinet!
I could rewire the whole cabinet, and start using the seperate UTrack Trackball controller instead of the MiniPAC (and disable the onboard Trackball controller) - but there's no guarantee that will work either (as ControlerRemap may not see the UTrack controller either)
Any ideas?
thanks
stigzler:
Hmmm, this looks great but cannot get working...
The DOS error:
The ctrlr cfg file:
--- Code: ---<!--
Configuration Remap file
-->
<mameconfig version="10">
<!--
############################################################
Define controller aliases, This just makes the controller names
a little easier to deal with for the rest of the file.
############################################################
-->
<controlleralias>
<id>HID#VID_D209_PID_1603_MI_02#7_27d3a5f8</id>
<alias>Lightgun1</alias>
</controlleralias>
<controlleralias>
<id>HID#VID_D209_PID_1604_MI_02#7_37a156</id>
<alias>Lightgun2</alias>
</controlleralias>
<!--
############################################################
This is the System Default section
It generally should be the FIRST system section in the cfg file
############################################################
-->
<system name="default">
<!-- put a controller element here to have it copied into ONLY this particular
system element
-->
<controller id="Lightgun1">
<input>
<port type="P1_LIGHTGUN_X">
<newseq type="standard">
GUNCODE_XAXIS
</newseq>
</port>
<port type="P1_LIGHTGUN_Y">
<newseq type="standard">
GUNCODE_YAXIS
</newseq>
</port>
</input>
</controller>
<controller id="Lightgun2">
<input>
<port type="P2_LIGHTGUN_X">
<newseq type="standard">
GUNCODE_XAXIS
</newseq>
</port>
<port type="P2_LIGHTGUN_Y">
<newseq type="standard">
GUNCODE_YAXIS
</newseq>
</port>
</input>
</controller>
<!--
###################################################
ACTUAL INPUT MAPPING STARTS HERE
DO NOT actually put anything in this section.
It is completely cleared and regenerated!
###################################################
-->
<input>
<port type="P1_LIGHTGUN_X">
<newseq type="standard">
GUNCODE_3_XAXIS
</newseq>
</port>
<port type="P1_LIGHTGUN_Y">
<newseq type="standard">
GUNCODE_3_YAXIS
</newseq>
</port>
<port type="P2_LIGHTGUN_X">
<newseq type="standard">
GUNCODE_5_XAXIS
</newseq>
</port>
<port type="P2_LIGHTGUN_Y">
<newseq type="standard">
GUNCODE_5_YAXIS
</newseq>
</port>
</input>
</system>
<!--
###################################################
This is a GAME specific section
Add additional <controller> sections here
to define how those controllers should map for this
particular game
###################################################
-->
<system name="ribbit">
<!-- This would be stupid to actually use, but as an example
For this game ("Ribbit"), reverse the UP and DOWN directions
on the joystick -->
<controller id="U360 Player1">
<input>
<port type="P1_JOYSTICK_UP">
<newseq type="standard">
JOYCODE_YAXIS_DOWN_SWITCH
</newseq>
</port>
<port type="P1_JOYSTICK_DOWN">
<newseq type="standard">
JOYCODE_YAXIS_UP_SWITCH
</newseq>
</port>
</input>
</controller>
<!--
###################################################
ACTUAL INPUT MAPPING STARTS HERE
DO NOT actually put anything in this section.
It is completely cleared and regenerated!
###################################################
-->
<input></input>
</system>
</mameconfig>
--- End code ---
Command line:
C:\Emulators\Mame0149b\mame64.exe ptblank -rompath "J:\roms" -joy -skip_gameinfo -nowindow -video d3d -noswitchres -triplebuffer -ctrlr MyArcade2
:dunno Any ideas??
nick3092:
--- Quote from: stigzler on April 10, 2014, 04:48:28 pm ---Hmmm, this looks great but cannot get working...
The DOS error:
The ctrlr cfg file:
--- Code: ---<!--
Configuration Remap file
-->
<mameconfig version="10">
<!--
############################################################
Define controller aliases, This just makes the controller names
a little easier to deal with for the rest of the file.
############################################################
-->
<controlleralias>
<id>HID#VID_D209_PID_1603_MI_02#7_27d3a5f8</id>
<alias>Lightgun1</alias>
</controlleralias>
<controlleralias>
<id>HID#VID_D209_PID_1604_MI_02#7_37a156</id>
<alias>Lightgun2</alias>
</controlleralias>
<!--
############################################################
This is the System Default section
It generally should be the FIRST system section in the cfg file
############################################################
-->
<system name="default">
<!-- put a controller element here to have it copied into ONLY this particular
system element
-->
<controller id="Lightgun1">
<input>
<port type="P1_LIGHTGUN_X">
<newseq type="standard">
GUNCODE_XAXIS
</newseq>
</port>
<port type="P1_LIGHTGUN_Y">
<newseq type="standard">
GUNCODE_YAXIS
</newseq>
</port>
</input>
</controller>
<controller id="Lightgun2">
<input>
<port type="P2_LIGHTGUN_X">
<newseq type="standard">
GUNCODE_XAXIS
</newseq>
</port>
<port type="P2_LIGHTGUN_Y">
<newseq type="standard">
GUNCODE_YAXIS
</newseq>
</port>
</input>
</controller>
<!--
###################################################
ACTUAL INPUT MAPPING STARTS HERE
DO NOT actually put anything in this section.
It is completely cleared and regenerated!
###################################################
-->
<input>
<port type="P1_LIGHTGUN_X">
<newseq type="standard">
GUNCODE_3_XAXIS
</newseq>
</port>
<port type="P1_LIGHTGUN_Y">
<newseq type="standard">
GUNCODE_3_YAXIS
</newseq>
</port>
<port type="P2_LIGHTGUN_X">
<newseq type="standard">
GUNCODE_5_XAXIS
</newseq>
</port>
<port type="P2_LIGHTGUN_Y">
<newseq type="standard">
GUNCODE_5_YAXIS
</newseq>
</port>
</input>
</system>
<!--
###################################################
This is a GAME specific section
Add additional <controller> sections here
to define how those controllers should map for this
particular game
###################################################
-->
<system name="ribbit">
<!-- This would be stupid to actually use, but as an example
For this game ("Ribbit"), reverse the UP and DOWN directions
on the joystick -->
<controller id="U360 Player1">
<input>
<port type="P1_JOYSTICK_UP">
<newseq type="standard">
JOYCODE_YAXIS_DOWN_SWITCH
</newseq>
</port>
<port type="P1_JOYSTICK_DOWN">
<newseq type="standard">
JOYCODE_YAXIS_UP_SWITCH
</newseq>
</port>
</input>
</controller>
<!--
###################################################
ACTUAL INPUT MAPPING STARTS HERE
DO NOT actually put anything in this section.
It is completely cleared and regenerated!
###################################################
-->
<input></input>
</system>
</mameconfig>
--- End code ---
Command line:
C:\Emulators\Mame0149b\mame64.exe ptblank -rompath "J:\roms" -joy -skip_gameinfo -nowindow -video d3d -noswitchres -triplebuffer -ctrlr MyArcade2
:dunno Any ideas??
--- End quote ---
Unfortunately MAME doesn't differentiate between "could not load file" and "file not found". Most likely you are experiencing the latter. Make sure you have the file in your ctrlr folder. If it is, maybe you have the ctrlr directory set wrong in your mame.ini file. Should look something like this (which btw, you can shorten your command line by setting options that don't change in here):
--- Code: ---#
# CORE SEARCH PATH OPTIONS
#
rompath roms;chds
hashpath hash
samplepath samples
artpath artwork
ctrlrpath ctrlr
inipath .;ini
fontpath .
cheatpath cheat
crosshairpath crosshair
--- End code ---
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version