Aimtrak and mouse not working in Nestopia UE core as Zapper

RetroArch Windows devices
#1

Hi All

I’m hoping someone can help me out. I’m using Retroarch 1.6.7 with the latest Nestopia UE core. This is running fine on Windows 7 64bit. I’m trying to get Duck Hunt et al working with my mouse (and ideally my AimTrak guns). I have the NstDatabase.xml file in my system folder.

When launching RetroArch and firing up Duck Hunt (World) I get no reticle either from my mouse or my guns. If I fire up Nestopia 1.40 my mouse and guns are instantly recognised and I get a reticle - all is well - but not in RetroArch.

I have tried running the different drivers, e.g., the raw driver and tried selecting various mouse indexes for User1 and User2 but to no avail. Outside of RetroArch, the guns drive my cursor like they should and I can click on things etc. I also have a trackball.

According to the AimTrack config software, my guns are set to DEVICE7 and DEVICE8. When firing up RetroArch with the following switches with the raw driver I get this info:

[INFO] [WINRAW]: Initializing input driver … [INFO] [WINRAW]: Mouse #0 \?\HID#VID_062A&PID_4101&MI_01&Col01#7&2e54f0dd&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}. [INFO] [WINRAW]: Mouse #1 \?\HID#VID_D209&PID_0420&MI_02#7&3c5b89&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}. [INFO] [WINRAW]: Mouse #2 \?\HID#VID_D209&PID_1607&MI_02#8&1251832d&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}. [INFO] [WINRAW]: Mouse #3 \?\HID#VID_D209&PID_1608&MI_02#8&27c6b727&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}. [INFO] [WINRAW]: Mouse #4 \?\HID#VID_D209&PID_15A1#6&1d4bf781&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}. [INFO] [WINRAW]: Mouse #5 \?\Root#RDP_MOU#0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}.

Can anyone who might have gotten this working be able to give some clear instructions as to where I might be going wrong? Or even just some clarity as to whether it is at all possible so I’m not wasting any more time?

Thanks in advance for any pointers (no pun intended)! :slight_smile:

1 Like
#2

Sounds like you’re missing the NstDatabase.xml, which needs to be in your ‘system’/BIOS directory for Nestopia to automatically recognize zapper games.

#3

Thanks for the suggestion but I do have that file in the system folder. I’ve just dropped it in there. Does it need a sub folder or anything? The file does seem to be in use as I can’t delete it whilst I’m running RetroArch and playing a NES game.

#4

Hmm, no, that should be it. Maybe try switching to the xinput driver temporarily and see if the reticle comes up with it.

#5

when on winraw, try to play with the mouse index in controls section and see what works. it would be easier if you only have 1 mouse or similar pointing device connected, i have never got 2 mouse/pointer thing work properly on winraw when i was testing it before.

#6

You need to use the latest nightly RetroArch build – not 1.6.7 – and you need to use the “raw” Windows input driver for this to work.

Please then refer to this guide to understand how to set up your mouse and lightgun devices: Configuring RA for multi-mouse (spinners, lightguns, tackballs)

1 Like
#7

Thanks for the help guys. A little more testing carried out:

  • I downloaded and installed the latest Windows nightly from this URL:
  • http://buildbot.libretro.com/nightly/windows/x86_64/RetroArch-2017-10-23-x64-setup.exe
  • Fired her up, downloaded the Nestopia UE core, set driver to RAW
  • Exited
  • Added the NstDatabase.xml file to the system folder
  • Tried the game - no mouse support
  • Set maximum players to 2
  • Device type for Player 1 and 2 is RetroPad
  • Device Index is set to Wireless Controller #1 (there is an option for Xinput controller or disabled)
  • Set Mousing binding for Player 1 and Player 2 from 0 to 1
  • Tried the game - no mouse support
  • Repeated until mouse index was set to 8 - no joy. I didn’t restart the content before each switch.
  • I fired up retroarch with the verbose switch - it tells me:
  • [INFO] [WINRAW]: Initializing input driver…
  • [INFO] [WINRAW]: Mouse #0 \?\HID#VID_062A&PID_4101&MI_01&Col01#7&2e54f0dd&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}.
  • [INFO] [WINRAW]: Mouse #1 \?\HID#VID_D209&PID_0420&MI_02#7&3c5b89&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}.
  • [INFO] [WINRAW]: Mouse #2 \?\HID#VID_D209&PID_1607&MI_02#8&1251832d&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}.
  • [INFO] [WINRAW]: Mouse #3 \?\HID#VID_D209&PID_1608&MI_02#8&27c6b727&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}.
  • [INFO] [WINRAW]: Mouse #4 \?\HID#VID_D209&PID_15A1#6&1d4bf781&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}.
  • [INFO] [WINRAW]: Mouse #5 \?\Root#RDP_MOU#0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}.
  • Other useful information (?):
  • [INFO] [Autoconf]: 46 profiles found.
  • [INFO] [Autoconf]: selected configuration: D:\Emulators\RetroArch\1.6.7 Nightly\autoconfig\xinput\DUALSHOCK_4.cfg
  • [INFO] [DINPUT]: Device #1 PID: {0420} VID:{D209}
  • [INFO] [Autoconf]: 46 profiles found.
  • [INFO] [DINPUT]: Device #2 PID: {0420} VID:{D209}
  • [INFO] [DINPUT]: Device #3 PID: {0420} VID:{D209}
  • [INFO] [DINPUT]: Device #4 PID: {0420} VID:{D209}
  • [INFO] [DINPUT]: Device #5 PID: {0420} VID:{D209}
  • [INFO] [Autoconf]: no profiles found for I-PAC 2 (53769/1056).
  • [INFO] [Autoconf]: 46 profiles found.
  • [INFO] [DINPUT]: Device #6 PID: {1607} VID:{D209}
  • [INFO] [Autoconf]: no profiles found for I-PAC 2 (53769/1056).
  • [INFO] [Autoconf]: 46 profiles found.
  • [INFO] [DINPUT]: Device #7 PID: {1608} VID:{D209}
  • [INFO] [DINPUT]: Device #8 PID: {FACE} VID:{FEED}
  • [INFO] [DINPUT]: Device #9 PID: {FACE} VID:{FEED}
  • [INFO] [DINPUT]: Done enumerating joypads …
  • [INFO] [Joypad]: Found joypad driver: “dinput”.
  • [INFO] [Autoconf]: no profiles found for I-PAC 2 (53769/1056).
  • [INFO] [Autoconf]: 46 profiles found.
  • [INFO] [Font]: Using font rendering backend: freetype.
  • [INFO] [Autoconf]: no profiles found for I-PAC 2 (53769/1056).
  • [INFO] [Autoconf]: 46 profiles found.
  • [INFO] XAudio2: Requesting 64 ms latency, using 64 ms latency.
  • [INFO] [Autoconf]: no profiles found for I-PAC 2 (53769/1056).
  • [INFO] [Autoconf]: 46 profiles found.
  • [INFO] [Autoconf]: no profiles found for ATRAK Device #7 (53769/5639).
  • [INFO] [Autoconf]: 46 profiles found.
  • [INFO] [Autoconf]: no profiles found for ATRAK Device #8 (53769/5640).
  • [INFO] [Autoconf]: 46 profiles found.
  • [INFO] [Autoconf]: no profiles found for VJoy Virtual Joystick (65261/64206).
  • [INFO] [Autoconf]: 46 profiles found.
  • [INFO] [Autoconf]: no profiles found for VJoy Virtual Joystick (65261/64206).

No joy I’m afraid. I’ve looked at the guide listed in the link, but even when trying indexes 1-8 no change. Do I need to restart between each attempt?

Any other thoughts?

#8

Is there any way you can try your equipment with the MAME 2003 core and Area 51 as the game? That is the configuration used during testing for the multi-mouse and the lightgun testing.

#9

I will give it a go.

Not that it’s relevant but I do have MAME running outside of RetroArch and the Aimtrak guns work correctly in Area 51.

As it happens, I’m not necessarily after multi mouse support per se, most NES and SNES games etc. we’re single player - who had more than one Zapper? But I appreciate having multiple ‘mice’ on my system might mean I need multi-mouse support working to get it going even for single player games.

I’ll post back as soon as I get chance to try the MAME core.

Thanks again.

#10

Regrettably, I cannot get MAME 2003 to run with Area 51 within RetroArch. I’ve tried launching all of the zip files I have for it and it either just fails to load or RetroArch just crashes out. I have:

area51.zip area51a.zip area51mx.zip area51t.zip area51ta.zip

The CHDs are in the appropriate folders. Area 51 (3000) launches when I run it in MAME 64 1.80, complete with reticle and light gun working. But nothing in RetroArch.

So I’m a bit stumped. Does anyone have a specific version of RetroArch and config where even the normal mouse works in Duck Hunt in the Nestopia core?

Thanks again for any thoughts.

#11

Have you ever figured this out? I am having the exact same problems