Headrush69

1) Your rom files are all in RAR archives? I didn't think Retroarch supported RAR decompression. 2) Pick a game and right click and select EDIT. Does the filename and path listed there still match the actual location of the rom? If you edit that line and re-pick the rom, does it work now?

No waste, it's all good. Glad you got it working. Having a mix of arcade controls, flight stick, spinner, trackball, Xbox controllers, light gun, steering wheel and wii remotes, I know first hand the issues of dealing with multiple devices and emulators that all handle them differently.

We need more detailed explanations as it’s hard to follow otherwise. Those cfgs in Mame and LB should not matter. Good to delete. i need to know if you tried the steps I listed above with key commands only, to find out if the remapping is working correctly first, or whether the issue is you static mappings.

The cfg files should always be in the MAME -> cfg folder. Not sure how you got one just in the MAME folder and the LB folder

Let’s narrow down the issue. Forget your controller for now. Delete the default.cfg and any game specific cfg. Start a game and set custom keyboard commands. 1) Quit Mame. Was a Mame specific cfg for the game created? 2) Start the same game from LB. is the changed mapping still there? Are you 100% sure you are point to the same Mame executable in LB. Edit: Sounds from your added info that your static device ids are setup correct. Can you post you ctlr file and the output from running Mame with the -v option from a command line.

Make sure you don’t have a game specific file in the MAME -> cfg directory as it will override the default config. Also, did you use the LB full MAME set importer? If so, make sure you are launching the exact same game from LB. it could be you are running a different variant of the same game. if you right click a game and pick edit, under the additional application a tab you can see all the variants.

If you used the MAME importerm right click on game and select edit. Go to additional Apps tab and all the versions are there. Pick the one you want and hit make default button.

True, but I think for noobs seeing that can likely be more confusing, especially when it comes to USB devices, as a lot have generic names and it’s not alway so easy to see which is which.

Google for USB Device Tree Viewer, it's a free, good program for finding device IDs.

Try it, you won't hurt anything. I can't speak for every game, but a lot depends on individual games/emulators and the support for different resolutions and whether they will allow window mode sizes to be changed. It will work whether starting from LB or BigBox if it works. It will be looking for the game exe, (Infinos Gaiden), not where it started from.

You need to give us more information, like exactly what you mean by light gun. WHat device do you have? It's unlikely you need a ctrl file, as most light guns are just seen as mouse devices in MAME. (Unless you have a old light gun with a CRT)

Universal Controller Remapper. yes, that is what they do.

You probably my need to use something like Xpadder or UCR if Steam doesn’t have this built in yet. This may help, but I cant’t verify, I don’t use my iPac controls in Stream (yet): Xpadder and Steam

That’s what I am doing now also. I’ll check out Monkey Hero on this new BIOS and let you know if it helps.

On what system are you talking, steam?

This isn't entirely accurate. When you use a filename alone, MAME looks in its hash file for corresponding media and uses it as needed. Sometimes systems use the same cart/floppy images you would normally use, on other systems it might directly map cartridge data in memory. This is MAME software list usage. When you use a complete file path, MAME starts using the media you supply, it ignores any information in it's hash file. The big difference is the system you are passing to MAME. When you use intvoice, whether using software lists method or explicit file path, that causes MAME to automatically load the Intellivision Voice cart into slot 1. So these two line should work the same: If you were to run You would not get voice support even using software lists. It's the system passed that enables it. (intvoice) Just for completeness, this is also an option: (cart and cart1 are equivalent)

Sure does clean up some games, but it also comes with a heavy performance hit if your hardware isn't up to snuff. Does this core have any other changes? (other than that and widescreen options) Never mind, found the original Retroarch announcement and detailed explanation.

The Mesen core can be downloaded directly within Retroarch. Just start Retroarch, go to Load a Core, than at the bottom of the list there should be a Download a Core option. All you have to do after is in LB -> Tools -> Manage Emulators and under Retroarch -> Associated Platforms, add Nintendo using Mesen core. (same as you did you Snes9x) I don't think you can go wrong with Mesen-S, Higan or Bsnes. Higan is the most demanding., I use bsnes-mercury-accuracy just because for me Higan doesn't add much I need and it's well established. I've played with all three and never saw any difference. (for me)

Mesen is the newest and the current popular choice as it has covers the most NES mappers, but the others also cover all the mappers used for commercial games. I switched from Nestopia to Mesen, but nestopia was fine as well. Snes9x isn’t as accurate as the other SNES emulators, but it’s serviceable and better for lower end hardware. Yes you can upgrade a yearly license to a lifetime later.

Is there a mechanism for submitting additions/changes without needing to use git and PRs? I've modified a few layout files like Star Castle to add color overlays within the bezel, so it's not just an either or option like now.

First step, make sure you set up your devices so they have statics IDs and don't change: MAME Static Device Mapping Once done, set your controls in MAME as you like. You can set up both joysticks for the same controls. (For example button 1 on Joystick 1 to action A, and button 3 on joystick 2 to action A) Now go into your MAME -> cfg folder and find the cfg matching the rom you set. Right click on that file and change the properties to read only. I'm assuming your joysticks are different. If they are the same or the button order on both is reported the same, these steps shouldn't be needed. If joystick 1 is missing, Joystick becomes Joystick 1 and same button order would work.

You can't tell from the photo, but the original tray is angled now so the steering wheel is very comfortable when sitting. (A few touches left to do, like enclosing analog flight stick under panel.)

They both look impressive but as always specs alone never tell the entire story and it will come down to other factors, exclusives for each, pricing, real time performance. The push for ray-tracing is great, but if performance suffers using it, it might change some people's opinions not understanding the differences. Since both systems are suppose to offer good backwards compatibility to previous systems, my guess is for the most part those in MS camp will stay with MS, and the same for the Sony camp.

I'm really conflicted on which I prefer. Even the software core at 2x internal resolution with a shader looks pretty good. If you go nuts with the hardware settings, you loose the feel for the real PS1 experience and you might as well run the PS2 version of the game. (Seems so many were done on both) I'll probably end with a mix of running different games with different renderers using beetle_hw_psx. At this point in my build it's more about reducing the number of cores/emulators for long term maintenance. It seems from the libretro github pages for those cores that the software only core is a stripped down version as they do share common commit and issue pages.

I've tried to find answers on Retroarch's forums and discord several times but never got any concrete answers. Anyone know 100% sure that the beetle_psx core is exactly the same as using the beetle_hw_psx core with the software renderer? Why maintain 2 cores then? Only thing I would summize would be that the beetle_psx core might be lighter on resources with the other renderers removed for more restricted hardware like the Pi. Also, anyone have experience using the PSX bios from the PSP with their emulators? From what I've read this Sony tweeked BIOS has improvements which helps and optimizes many games under emulation.