Headrush69

You don't need it. You just have to make sure that the your mame.ini rompath variable points to where your roms (BIOS) are AND where the root directory is for your software list software. (in there should be a folder cdi with your CHDs) If you are having issues, if you start mame from a command prompt or powershell with the verbose option it should tell you the issue. If using software lists: Or you can directly start a CHD without using software lists like any other rom: You still need your rompath set in mame.ini so it can find the cdi bios file. I prefer the second method in most cases. I keep my bios files in the rom directory in the mame directory which is on my SSD. On my HD I have folders for each platform and store the CHDs. It's easy to import that folder into LB and in general if I have a CHD or image that doesn't match the one mame's software lists wants, I can still run it.

If you have it working that's what matters, but I think you are confusing several things. I have xbox controllers, light guns and several other controllers and I use them all without enabling raw input in emulator.ini When you are using Demulshooter, it handles the raw input, not the m2emulator itself. Demulshooter injects/patches the support into the emulator as needed. You can leave your xbox controllers working without changing anything and just run Demulshooter when needed for light gun games.

I guess I don't understand your issue at all then. I thought in your original post that you meant you needed to enabled rawinput in emulator.ini for model2 light gun games, and turn it off to use xinput for other model2 games.

You're essentially doing the same thing but using BAT commands rather than AHK. Short of writing it for you, I think if you have issues with the AHK, using the BAT will be the same.. If you don't want to get Demulshooter working, I think Koroth's suggestion of using two instances of m2emulator might be the easiest method for you. Also, be aware that even though m2emulator has native raw input support, there are reports of issues using it including changing devices numbers, something that isn't an issue with Demulshooter.

No you do not enable raw input in EMULATOR.ini (Demulshooter for m2emulator doc)

You are correct Koroth, there are several ways to do this, including directly with a bat file and avoiding AHK. (Much like how many start Daphne games) I think the easiest approach is probably just using Demulshooter as an additional application and you can avoid needing multiple inis since raw input doesn't have to be enabled in EMULATOR.ini I use Demulshooter. This was just adapted from scripts I use with devreorder to hide and order specific devices when needed, but the approach is workable.

AHK can handle spaces in file paths. You need to download the full AHK (free) and it includes a small compiler application that converts your ahk script to an exe. You can of course run your AHK scripts (.ahk files) manually to make sure they do what you want before compiling them.

Not exactly. All it is doing is copying a specific ini file and over writing it to the default EMULATOR.ini That last option ,1 means to overwrite the current EMULATOR.ini file. You may want to restore your default ini after running as well. So you might have these inis in your emulator directory: EMULATOR.ini default.ini lightgun.ini So before the emulator starts you use the compiled script to over write EMULATOR.ini with the contents of lightguns.ini. After running the emulator you over write EMULATOR.ini with default.ini. The names you use are arbitrary except for EMULATOR.ini which is what the m2emulator will read on starting. Edit: This is just a general way to handle unique controller set ups. With the m2emulator you may want to check out Demulshooter so you don't have to use raw input directly in the EMULATOR.ini.

For situations like this I create all the ini files I need and than create a simple AHK script to copy each script to the default ini location. I compile the AHK script to an exe and than use LB's additional apps feature to run and wait for that to finish before starting the emulator. Here's an example:

I’ve not heard of FreePIE, but UCR provides that functionality and is quite popular. Maybe give that a try.

The only way you'll get it to work is if you use some remapping software to map the Spintrak (mouse) to a virtual joystick. Additionally, if you are using a steering wheel and pedals, m2emulator needs separate pedals, not combined.

Teknoparrot is the only system I still use RocketLauncher for since the Teknoparrot module has active monitoring for windows which is very helpful for clean startup screens and starting and stopping secondary applications. You can manually do similar things using AHK with LB, but not worth reinventing the wheel for just those games.

That was my biggest issue with the Sindens, setting up the software and of course the border. Not that is was overly hard, I just didn't want to go through every game and set it up. Having my cabinet running on just an i3 CPU, that all the processing is done on the gun and not the computer was a plus as well. The responsiveness of this gun is incredible.

The SIndens work better than the Aimtraks for me as well, but even better, if you are into a simple DIY project, check out JayBee's GUN4IR.

What format are your CD images in and was it working previously or is this a new setup?

If using Retroarch directly or through LB works, than it had to be a RL issue. Are you sure that Retroarch is the default emulator for Sega CD In RL? Also, in RL is the emulator patch for Retroarch correct and not pointing to an older version that may not have had CHD support yet?

Did they say why? I don't see how it would matter much. I can think of more disadvantages of using 2 over 1. Are you using in keyboard or joystick mode?

Start Retroarch Load the PUAE core Pick Information in Retroarch menu Pick Core Information All the BIOSes it uses should be listed and it should say whether you have the correct one or not. If your Bioses are correct, your issue is something else.

The hardware is going to be based more on the games you want to play more so than the gun itself. Having said that, I have a lowly 7th gen i3 that I can play all the light guns game with no issues. If you are looking to play more of the modern light gun games on Teknoparrot, you'll save yourself a lot of hassle if you have an NVidia based GPU. (My cabinet has an i3-7100 and a Nvidia 970 GTX)

We need more information: Retroarch version? Cores updated? Which video driver in Retroarch? Are you using any shaders? Do other cores have this issue?

Would you be willing to share that? I still use RL for a few systems and I also use devreorder. Currently I have compiled AHK scripts that copy the appropriate devreorder.ini into place as needed and use the Additional Apps feature of LB to run them as needed.

Joystick support varied greatly on Apple II games, that is for sure and sometimes takes a little trial and error and looking at the original manual. If I remember correctly when I was testing Archon, I think player 2 button was actually uses the player 1 second button. Try mapping that way and see if it works. (P1 Button 2 -> The button you want to use for Player 2 Button 1)

Some of the games need you to enter the game service menu and set specific options. (Which get saved to a nvram file) I can't remember the exact issue for swtrilogy (I'm sure it's on the supermodel3 forums), but I'll see if I can find it again.

Only thing I could suggest would be making the matching part of your device entries smaller. Maybe just try the instance part for each entry. (27bd7f40-a85c-11eb-8001 for example)

It remaps on each launch of MAME only. If you launch MAME using the -v option from a command prompt, you will see output for all devices and then any remapping it does, if any.