Headrush69

Are you cores up to date? My config items are different. If you have Retroarch 1.8.4, it now has built in core updating.

As Neil9000 said there is no correlation between LB and the emulators when it comes to controllers. (I assume when you say works in LB, what you mean is Dolphinbar controls worked in Dolphin emu when launched from LB)

Sounds like it was the wrong file then as that can't be possible. MAME standalone uses the default.cfg in the cfg folder, not the root MAME folder. If you are using Retroarch, that changes everything. I only use standalone MAME because it has much better multi device handling. The only advantage for me with Retroarch MAME core would be shaders, but I use Lordmonkus HLSL settings which I am happy with.

Yes the software core does up scaling of internal resolution which does help graphic fidelity. SilverDragon81, maybe post the options you have set for the core. Seems your spec should be able to handle either PSX core fine. Edit: You could start the Task Manager and switch to the performance tab and see your CPU utilization as you run PSX and that might help narrow down where the bottleneck is. (If you right click the graphin task manager you can switch to a per logical core view)

By chance are you controllers dynamic? (Can be unplugged sometimes) If so, MAME erases mappings for controllers that aren't attached. The simplest solution is once you set your mappings up, make the file read-only.

Which exact Vice64 are you using? There are a ton of different versions. I use the Retroarch Vice64 core almost exclusively and it has work well.

Since Neatmouse has several key options for enabling, why not just set it to run at startup, and than in WiniPac set a shift key to one of those activation keys? I don't use Neatmouse myself, but I'm guessing you will need to set fairly high acceleration if available to make using a joystick instead of a mouse feel somewhat decent.

Another option is running the old PC version too. It works great on Windows 10 and I have that one integrated into LB as well. Although I do like the feel of the PS2 version better, they are close visually. (With enhanced graphics from using PCSX2) YouTube comparison Seems like a lot more features in PS2 version as well (Different developer for PS2 version)

It's very map dependent for sure. Sucks about your AMD not supporting AVX2.

That is just a copy and paste of the instructions from the Ultimarc web site. From my testing I was able to see some of the issues you stated as well. Without going into great detail, seems to me that's it's best to pick a mode (keyboard, Dinput, Xinput) and stick with that. I don't think mode switching is a good idea when using from a front-end like LB. The issue is Windows can take time to see the changed device, which doesn't make for a good end user experience. Having said that, loading a gamepad profile using the command line works, and the iPac will change modes, but often I'm left with gamepad controls that do not work. (They do appear as Dinput or Xinput controls though) I'm sticking with staying in Keyboard mode. Loading profiles from command line while in keyboard mode still seems to work perfectly. As noted above, I found using AHK remapping easier than needing to change profiles though. Is there a specific emulator you HAVE to use gamepad or keyboard mode only?

Seems odd. I could understand a firmware upgrade causing problems if not done right, but downloading a profile seems strange to crash the computer. i just upgraded to the multi-mode 1.52 on my iPac Ultimate and it doesn’t appear to apply the profile without forcing board reconfigure as well. Currently doing some more testing. PS I don’t change iPac profiles anymore, replaced it with using AHK key remapping.

Are you running WiniPac as Administrator as per Ultimarc's web site instructions?

Can you be more specific? Do you mean flashing a custom profile on that iPac model requires the forcing the re-configure to the board or you mean the script doesn't work? If it's related to the new multi-mode firmware is it possible to downgrade back to 1.49 or 1.39 versions? I tried the multi-mode firmware and I remember I had a specific issue, can't remember exactly what it was but maybe try manually installing the older version and see if it works after that.

Did you go into Manage Emulators screen and add the newly changed name to associated platforms for the emulator?

It runs slower on my Nvidia system too. To be consistent I had to use native resolution, which isn't nearly as nice. Edit: I switched the GS plugin to GSdx-x32_AVX2 (was GSdx-x32-AVX before) and ran a few races and so far pretty good. Sun, smoke, light boxes are gone, only thing I notice so far is very minor issue in HUD. There might be a fix for that too. Edit 2: Turning on those HW Hacks I mentioned above, fixed the HUD issues. Only other issue I see is the massive slowdown problem when you get busted. (I got busted on purpose, they can't catch me ? ) Apparently this issue only happens when using 3x or higher upscaling. I set upscaling to 2x and no problems. Visually I didn't notice that much difference during gameplay.

I just made the changes yesterday, so I haven't completely had a chance to see check everything, but many of my gfx issues where resolved using the following HW Hacks: Edit: Seems it's very map dependent. I tried that map you posted images of above and the boxes are still there on that map. Software mode might be the only perfect way right now. Edit 2: Just switched to the OpenGL HW driver and it fixed the sun boxes on that map. The problem is it created different issues on another map.

Saw the same video I believe and in the comments it looks like the OP disabled some of the features in HW hacks so basically turned off those features so you don't see them.

Can you post the command line you are launching with? Just tested with my CHDs and they mostly do run, but console is flooded with cd buffer errors and it runs a lot slower than other options.

If you are looking to play Saturn games, MAME is far from your best option, and some games just won't work. Look at using or Mednafen or the Retroarch Mednafen core. (Beetle core) If you have .bin files, you might need to make cue file for them to load. It is quite easy. You also need to make sure you have the needed BIOS files. More info is here: Libretro Docs for Saturn core

As long as you remap any emulators that by default already have a mapping for the Enter key first, it shouldn't be a problem. (Specifically in MAME) (I don't know if LB uses Enter by default for anything. in BB you can set your keyboard mappings, so no issue there)

If you edit the game in the emulation you can set game specific command options. Just add -L cores/nameOfcoreYouWant

Have you checked the static IDs rebooting after having all 4 devices connected? I asked because according to this Microsoft Doc, that device instance variable is suppose to be persistent across reboots as well. You might be able to maintain static device mapping IF they all remain plugged in at least. (Even across reboots) Pricier option, but you could always upgrade to a better USB encoder as well. I can vouch for the iPac line.

Unfortunetaly it's seems a problem with these cheaper Chinese encoders and although they work OK on their own, when you get into situations with multiple devices you sort of get what you pay for. Having said that, I see people using Linux using udev rules to help with naming these, but that only helps them if the USB port is constant. We are limited in MAME by the input information it gives us, so not sure there is anything on that level that will or can help us. I don't know if this will work, but a thought was carefully using a hex editor on the Windows device driver file and change the name slightly for each and in device manager force it to use the modified driver. (The driver itself is the same, just the name we would change) I really don't know what protections Windows enforces on drivers and if it will work, but might be worth a try.

Just to be clear, these aren't real GameCube controllers using an adapter? They look to be PC TWIN SHOCK Gamepads which is made by Dragonrise which also makes Zero Delay controllers. This may be an issue with their controllers/products and how they report to Windows, not Windows itself. If they all report the same product (basically USBJoy) to Windows, this may be a problem.Doing some searching for you, see if I can find more out.

How are you GameCube controllers connected? Through some adapter or through the EasyGets as well. Is what you posted above the full Mame -v output in regards to input devices? If not can you post the full log.