Aimtrak Guns Switching ID's in Model 2 Emulator - Remap not a solution

[lisowskikevin]

Hey guys,

my PC keeps re-assigning the Aimtraks from gun1 to gun 2 etc etc after reboot. I am going to install Controller Remap to address the issue in MAME but what about Model 2? Does anyone have any ideas how to remedy this for model 2?

[romshark]

I hooked my guns up to my workstation PC, different USB ports than I used last weekend. I got bad assignments too. My Gun 1 controlled player 2, and Gun 2 had no effect. Going into TroubleShooter and configuring Device #1 as 1 and Device #2 as 2 (they were originally 0 and 1 respectfully.) However, I have been messing with TroubleShooter to work with the latest Model 2 Emulator by using Cheat Engine values, so my configuration of TroubleShooter has been reinstalled and modified (also, no luck getting it working on the latest.  There's fields for disabling certain values, and I don't know how to find those. But that's another story.) So my results may not be correct in this instance.

One thing to try: Have you used the Aimtrak configuration utility from Ultimarc.com? In it, you can set the device ID of each gun. I have Gun 1 set as Device 1 in both Aimtrak and TroubleShooter, and 2 for the other gun. Maybe both your guns are the same ID, and that's causing confusion in your PC? Just something to check.

I'll keep and testing my guns periodically, and let you know if I come across anything.

[lisowskikevin]

I hooked my guns up to my workstation PC, different USB ports than I used last weekend. I got bad assignments too. My Gun 1 controlled player 2, and Gun 2 had no effect. Going into TroubleShooter and configuring Device #1 as 1 and Device #2 as 2 (they were originally 0 and 1 respectfully.) However, I have been messing with TroubleShooter to work with the latest Model 2 Emulator by using Cheat Engine values, so my configuration of TroubleShooter has been reinstalled and modified (also, no luck getting it working on the latest.  There's fields for disabling certain values, and I don't know how to find those. But that's another story.) So my results may not be correct in this instance.

One thing to try: Have you used the Aimtrak configuration utility from Ultimarc.com? In it, you can set the device ID of each gun. I have Gun 1 set as Device 1 in both Aimtrak and TroubleShooter, and 2 for the other gun. Maybe both your guns are the same ID, and that's causing confusion in your PC? Just something to check.

I'll keep and testing my guns periodically, and let you know if I come across anything.

Thanks! I just tried it today and somehow they work! But I now have an issue with Controller Remap in MAME. I erased something I shouldn't have ugh. I posted the error message under the Software Forum.

Any chance you could take a look? I'm pretty pissed off right now, I have Model 2 sticking but MAME isn't and Controller Remap seems to be my best option but now I have run into this stupid error that I caused.

Frustrating! But thanks for any advice

[romshark]

I just looked at the other topic, but I haven't used Controller Remap yet (though it looks like I'll have to in the future). Hopefully someone else can answer it.

[lisowskikevin]

I just looked at the other topic, but I haven't used Controller Remap yet (though it looks like I'll have to in the future). Hopefully someone else can answer it.

Spoke too soon, my model 2 aimtraks work about every third time I reboot the computer.

Aimtrak utility and ts2 have them set for gun 1 and 2.

Sigh

[drventure]

Just noticed this thread. Sounds like you did end up looking into ControllerRemap after all.

Yeah, what you describe is pretty typical on Win machines, esp if you plug and unplug usb devices very much, or if you move a USB device from one port to a different port.

ControllerRemap should resolve the issue, once you get it squared.

[lisowskikevin]

Just noticed this thread. Sounds like you did end up looking into ControllerRemap after all.

Yeah, what you describe is pretty typical on Win machines, esp if you plug and unplug usb devices very much, or if you move a USB device from one port to a different port.

ControllerRemap should resolve the issue, once you get it squared.

Can it also work for model 2? I though controller remap was only for mame?

[drventure]

Doh. Nevermind. I can't read post titles well, apparently. 

[romshark]

Did some testing on my spare time (I'm on 10-hour work days, so my time to test is limited.) I tested using Model 2 (House of the Dead. Using TroubleShooter 2) and MAME (Area 51. Not using controller remapping utility.) Here's what I've found so far:
The device setting in the Aimtrak utility has no affect on other programs. The emulators worked the same (I set P2 gun to device 8. The emulators still saw it as gun 3). Most likely it's just for selecting each gun for configuration within the utility.
Completely shutting down and unplugging, adding a mouse, and turning on: Model 2 still worked with the guns in correct order. MAME got thrown off by one gun (p2 gun now showing up as gun 4 instead of gun 3 in MAME.)
Completely shutting down and unplugging, removing mouse, moving the guns to different USB ports, and turning on: MAME went back to working the same as when I started testing. Model 2 went off by one (on gun controlled the opposite player, and the other gun had no affect.)

So it looks like Model 2 is more resistant to change than MAME. Good thing we have the controller remapping software to keep MAME in line.
I'll do more testing as time permits.
(These results are based on limited testing, and may prove to be inaccurate as time goes on.)

[lisowskikevin]

Did some testing on my spare time (I'm on 10-hour work days, so my time to test is limited.) I tested using Model 2 (House of the Dead. Using TroubleShooter 2) and MAME (Area 51. Not using controller remapping utility.) Here's what I've found so far:
The device setting in the Aimtrak utility has no affect on other programs. The emulators worked the same (I set P2 gun to device 8. The emulators still saw it as gun 3). Most likely it's just for selecting each gun for configuration within the utility.
Completely shutting down and unplugging, adding a mouse, and turning on: Model 2 still worked with the guns in correct order. MAME got thrown off by one gun (p2 gun now showing up as gun 4 instead of gun 3 in MAME.)
Completely shutting down and unplugging, removing mouse, moving the guns to different USB ports, and turning on: MAME went back to working the same as when I started testing. Model 2 went off by one (on gun controlled the opposite player, and the other gun had no affect.)

So it looks like Model 2 is more resistant to change than MAME. Good thing we have the controller remapping software to keep MAME in line.
I'll do more testing as time permits.
(These results are based on limited testing, and may prove to be inaccurate as time goes on.)

Hmm, interesting thanks! Have you set up control remap with your MAME? Also do you use Hyperspin?

[stigzler]

This is on my to-do list at some point as run S2 and 2 aimtraks. Will knock something together when I get a round Tuit.

[romshark]

Hmm, interesting thanks! Have you set up control remap with your MAME? Also do you use Hyperspin?

I haven't yet messed with controller remapping software for MAME. When I have a large block of time, I'll try them out (I see versions from drventure and stigzler). I'll give them both a try on two other copies of my MAME folder on my test unit. I also want to get Supermodel (model 3 emulator) in there for testing also (Lost World game). So that would be 5 different programs to get readings on. As long as I make a spreadsheet in Excel to keep track of the programs behavior during the tests, I should be able to get useful data.

As for the front end, I use MALA on my cabinet. Maybe I should give Hyperspin another look though, as everyone seems to like it. However, these tests are being done with regular shortcuts on my test units desktop. I'm not loading any front-end for these.

I'm too burned out from work for any real testing, but I fired it up and checked Model 2 and MAME. Devices I have plugged in are the same as when I first started the tests yesterday. The guns are showing up properly in both. So that means, if some mouse or something is plugged in before powering on, the guns may be off a device number. But if nothing is changed in the settings, the mouse unplugged, and the PC rebooted (maybe turned off and on again), the guns might be assigned properly again. I think you mentioned about a wireless keyboard/mouse combo possibly affecting things when no USB items were changed, so I don't know how that works into the problem.

[stigzler]

Had a quick look at this on my test rig. There're some settings in EMULATOR.INI which may be relevant to this. Online docs regaridng settings here:

https://docs.google.com/document/d/1KiKUFqyLXt-HcVD_3drWIy9xI-aIcdQsY07bPiy7T2g/edit

Relevant bit:

Code: [Select]

UseRawInput
0 - Normal operation of mice for shooting games.
1 - Enables use of dual mice for shooting games. Will capture any mouse devices using low level inputs and prevent the screen from exiting whilst in fullscreen mode. When using this option, you need to press alt + tab to restore your mouse for normal windows operation. To control your emulator, activate its window again then use the alt key to activate the menu and execute commands accordingly.

RawDevP1; RawDevP2
(value can be 0, 1, 2, 3 etc)
These entries are only required if you experience trouble with dual mouse functionality. If you have other devices installed on your computer that may emulate as a mouse device (EG: Logitech G25 Racing Wheel), you may need to use these entries. If player 1 mouse functions, you will only need to add a value to RawDevP2. If the player 2 mouse functions, then you will only need to add a value to RawDevP1. Start by setting the value to 0, save and test the game, then raise the number by one each time until the cursor moves for both players in the game.

However - I'm not sure how you can use this to keep Gun 1 as Player 1 and Gun 2 as Player 2. A working setup for two mice in my Ini is this:

UseRawInput=1         ;Read mouse through Rawinput, allowing 2 mice
RawDevP1=0         ;Assign specific RawInput devices to players. If you have more than 2 mice
RawDevP2=1         ;set which one is assigned to each player (0-based)

Lets say, in above, this turns out as:
Where Mouse1 = Gun2 and Mouse2 = Gun1

So - I tried swapping to this to, in theory, swap the guns back over (simulating your difficulties with device renumeration on hotswap/restart etc):

UseRawInput=1         ;Read mouse through Rawinput, allowing 2 mice
RawDevP1=1         ;Assign specific RawInput devices to players. If you have more than 2 mice
RawDevP2=0         ;set which one is assigned to each player (0-based)

Then only one mouse worked!!??

So - it's all a bit mysterious really. Not beat yet - will tinker some more...

[stigzler]

Can't find a way to get it working, however - really - how much of a problem is this?

Let's say you have 1 Gun (Gun1) plugged in only - This registers as player one with the red sights

Now plug in the other Gun - Gun1 now becomes Player 2 (blue sights) and Gun2, Player 1.

Unless I'm missing something?

[romshark]

Our setup for Model 2 is a bit more complicated. The Emulator itself does not work with two Aimtraks. So Howard Castro wrote brilliant software that reads the Aimtrak data, and "hacks"  it into the Emulator using Lua scripts and stuff (probably more complicated than that, but it's the General idea.) So we don't mess with the controller settings in the ini file. Also the program (Troubleshooter 2,it should be on the front page of the Software forum) only works with Model 2 version 1.0. (I attached a copy of 1.0 in another topic. Just search my posts if you need it).
The problem is the guns changing device id on boot. Having a gun not working can be annoying, especially in a cabinet without a keyboard or mouse to help edit settings. In theory, if everything stays plugged into the same ports at all times, everything should stay the same. But I think some of us are seeing assignment changes, and want to fix that if possible.

Sorry if this post is hard to follow or if I misunderstood the "how much of a problem us this" thing. I'm typing this on my cell phone on my dinner break at work.

[lisowskikevin]

Our setup for Model 2 is a bit more complicated. The Emulator itself does not work with two Aimtraks. So Howard Castro wrote brilliant software that reads the Aimtrak data, and "hacks"  it into the Emulator using Lua scripts and stuff (probably more complicated than that, but it's the General idea.) So we don't mess with the controller settings in the ini file. Also the program (Troubleshooter 2,it should be on the front page of the Software forum) only works with Model 2 version 1.0. (I attached a copy of 1.0 in another topic. Just search my posts if you need it).
The problem is the guns changing device id on boot. Having a gun not working can be annoying, especially in a cabinet without a keyboard or mouse to help edit settings. In theory, if everything stays plugged into the same ports at all times, everything should stay the same. But I think some of us are seeing assignment changes, and want to fix that if possible.

Sorry if this post is hard to follow or if I misunderstood the "how much of a problem us this" thing. I'm typing this on my cell phone on my dinner break at work.

Ok so BREAKTHROUGH......I followed someone's advice about using the Aimtrak Utility to change my Aimtrak gun ID's from 1 and 2 to 3 and 4. Once I did that I have had no problems with Windows switching ID's in MAME or Model 2. I've rebooted 5 times and every time the Guns work perfectly in both Emulators! Holy crap I hope this isn't just a fluke!

I tried this before with negative results but somehow it seems to work now....maybe temporary, only time will tell!

[what2be]

Not sure why that fixed your problem as it really shouldn't make any difference other than when you changed the ID windows assigned it new mouse ID's to your guns that were higher than the previous ones and most likely now that those old id's are freed any new USB devices you plug in will use those earlier numbers and your aimtraks will stay the same higher numbers. Im kind of confused why people are having issues with mame and having to use controller remap. If this is a dedicated arcade cab then you most likely arent unplugging/plugging in your lightguns (or any other USB devices) so everything should stay the same. However, you will have issues if your lightguns are something you plug/unplug often as well as other usb devices.

[lisowskikevin]

Not sure why that fixed your problem as it really shouldn't make any difference other than when you changed the ID windows assigned it new mouse ID's to your guns that were higher than the previous ones and most likely now that those old id's are freed any new USB devices you plug in will use those earlier numbers and your aimtraks will stay the same higher numbers. Im kind of confused why people are having issues with mame and having to use controller remap. If this is a dedicated arcade cab then you most likely arent unplugging/plugging in your lightguns (or any other USB devices) so everything should stay the same. However, you will have issues if your lightguns are something you plug/unplug often as well as other usb devices.

That's just it though....I never unplugged ANYTHING but Windows still reassigned the guns. Every time I rebooted and opened MAME, my guns would switch. It's crazy because I left everything plugged in and every reboot my MAME Aimtrak settings and MODEL 2 would be messed up. Weird.