Headrush69

Why unzip them? The Retroarch gambatte core will load the zips directly.

I thought you said in the first post that you did that already? I'm glad you got it working. Light guns sure are the way to play these games but as you're finding out, each emulator/game has it's quirks and procedures that require some up front configuration.

I have Guncon2s for my Gun4IRs so I haven't needed to do this but it sounds like what you want is an AHK to remap some keystroke to the right and middle mouse clicks which in PCSX2 would be what the Nuvee plugin uses for A and B.

I don't suggest trying to edit it manually. set your mappings in the PCSX2 app and it should get saved to PAD.ini

Can you run the supermodel3 emulator from either a Powershell or command prompt and post the beginning of the log it generates? Of course change the path to your rom location. If you've set the resolution to match your desktop resolution, this might help show us why it's still changing it. (Maybe it doesn't support that high, I don't know. Just 1080p for me)

If you aren't running the multi_cpu version you have to change that script to emulator.exe instead. You may have to re do the in game calibration after switching modes, I don't know.

Can you stat what hardware you are using (especially GPU) and your desktop resolution? You need to provide more details when you tell us what you have tried. For example "I tried to match the resolution and it made the game unplayable", which emulator specifically, how did you set resolution, what options, etc. Screenshots are very helpful as well.

I believe their idea is that if you hot plug a device in you probably want to use that device and it makes it ready to run if you move it to the first device. I would check out Tur Controller Order Utility. It has a daemon that actively makes sure controller stay in a set order.

Add this to the running script option under Edit Emulator Those games are natively 4:3 aspect ratio. Are you running at this ratio and not stretched? Have you switched the Gun4IR aspect ratio to content mode by default or used the gun mode button to switch to that mode? Are you using Demulshooter with m2emulator? It's needed to get both guns running. Was it running before starting the emulator?

What reload option did you set as default in the Gun4IR utility? Are you running Supermodel3 emulator at the same resolution as your desktop? I find this is a Windows issue in general and the easiest option is to make sure you run at the same desktop resolution. The Gun4IR guns should be much better than wiimotes. (I have both as well) You shouldn't use any of that software needed with the wiimotes for Gun4IR. Supermodel3 emulator has raw input support and works natively with the guns. What revision of Supermodel3 emu are you using? You are setting the analog components and not the digital equivalents? Specifically in Lost World, are you using gun or analog_gun for input type? (Settings

Some games require in game calibration. I know Jurassic Park Lost World is one of those games in SM3. Once I did that my Gun4IRs are perfect in game.

Did you delete the roms as well? Can't you just restore the specific platform XML from the Launchbox/Backups/Platforms folder?

I’ll check when I get home but I don’t use an emulator either. Sounds like just a misconfiguration. LB passes the platform and game name to LedBlinky, nothing about the emulator. Edit: Looks like the same issue as here: LB not passing LedBlinky game name

You can also use ClrMamePro to build a system specific platform from any rom set as well. It's as simple as only enabling the platform in Set Information dialog. This way you also know that your set is complete and contains all required roms in each zip.

What exactly mean by you can't edit individual games? So under Laser DIsc platofrm in LedBlinkControlsEditor, you can't pick NEW, you can pick NEW but can't edit the fields? I would suggest turning on Debugging in LEDBlinkyConfig and we can see what LaunchBox is telling LEDBlinky, where's it grabbing information and other info on your button mappings. (Just remove your email from the top of file before posting.)

Do mean just the ones you converted? My entire library is in CHD and launch fine with Redream.

Highly unlikely. I have converted my entire library to CHD also and every time I had an issue with one it was a "bad" dump. Finding another version always solved the issue. It seems weird as the original format would work (BIN/CUE or CDI/GDI), but the CHD format may be more specific and since it's a lossless format, these less than 100% rips cause issues.

What version of Retroarch are you using? What driver are you using for Controllers in Retroarch? I have a similar set up but with more controllers and using the latest version of Retroarch and XInput for controllerdriver and Dinput for input driver in Retroarch, my Xbox controllers always jump to #1 and #2 unless I use some controller ordering tool like Tur Game-Controller Order or devreorder.

Edit: Thread on Phoenix Launcher

That emulator is a little different than most and it's not as simple. There are some threads dedicated in this forum for getting these running more easily, just search for them. (Sorry don't have link handy)

Yes, purchase a copy of LEDBLinky.

So all those WIndows games you have to configure your buttons within each game to your XBOX controller. Some will not allow you to use analog input (Xbox triggers) for digital buttons. In these cases you would have t use a third party piece of software to do some remapping. I still don't understand how this is related to LEDBlinky. LEDBlinky doesn't have anything to do with gamepad configuration. Need more detailed information for me to be more helpful.

I am still confused. My guess is you are talking about mostly Retroarch. You want to map your arcade panel buttons to match the buttons on the XBOX controls. (So buttons A, B, X, Y, L1, L2, R1, R2) If that is true, this is done within Retroarch, not sure how LEDBlinky fits in here.

I'm confused about what you are trying to do here. LEDBlinky for the most part is used for lighting LED buttons but you are talking about XBOX controllers. Can you explain more what you are doing or your set up? The reason Quick Input doesn't see them is because they are analog inputs and button presses are digital. Some software will let you convert between them, but need to know your set up first.

The name length shouldn't be a problem. When you have any issues with LEDBlinky, should should enable debugging and look at the log file after. It is really verbose and clearly will tell you what information LB is sending to it and if it has a corresponding match in your LEDBlinkyControls file. Most of the time it's usually a mismatch in platform or rom names. P.S. If you post part of your debug log from LEDBlinky, make sure you remove your email address from it.