Headrush69

You can use MAME stable controller IDs to help with the issue: MAME stable controller IDs One problem is the IDs between the same Xbox controllers aren't unique (unless the situation has improved), so you could set up 2 xbox controller to specific IDs, but you can't make sure a specific xbox controller is the first or second xbox controller . For example you can map 2 xbox controller to MAME joystick 7 and one to MAME joystick 8. Which ever one is scanned or attached first will be assigned to MAME joystick 7 and the next one as MAME joystick 8. So within MAME you can map controls to joystick 7 and 8 for player 1 and player 2, but you don't know for sure which Xbox controller will be which.

Just to clarify, I was referring to a fixed Pitfall rom. Starts and plays perfectly for me with the a5200 core.

Are you using an actual trackball? What values did you end up with for sensitivity? I have a Hi-Rez encoder wheels on my trackball, so my values are different than most people, but I never played Marble Madness on a real cabinet, so I don't know exactly how it should feel.

WOW those are some tight controls in that video. Have you adjusted the analog controls within MAME? Every once in a while MAME devs makes corrections and adjustments to control values if better information becomes avaliable. Whenever I have a random issue with MAME for a game that previously worked perfectly, I extract a clean MAME folder and run the game there as well. Helps narrow down whether it was a MAME change or possibly a faulty or corrupt older cfg, ini, etc.

Still working fine for both. (I used ReshadeManager) I switched to using better lua scripts for widescreen support so don't use bezels for most m2 games now. I did have per game bezels, but if I remember correctly, finding the model 2 games bezels was tough. It wasn't a complete pack and I got them individually all over. I take a look and see if I still have them.

What exactly was the issue? (Also what are your machine specs and were you using standalone or Retroarch core) Maybe it's just a configuration issue. I use both Melon and Desmume in Retroarch and both work well.

Maybe I'm missing what your looking for, but you won't get the collapsable part until you add another item that has the upper category set as a parent. If you highlight a category and choose new category, it should preset the new items parent as the currently highlighted category,

I'm on version 1.7.4721 and it works, so I don;t know. Just SSX1 and Tricky apparently.

So installed Stella to try and using the command line argument -f seems to be the issue. Don't use it and it starts but in windowsed mode, with it it is unrecognized and goes to Stella menu. Edit: Use this command line option

Do you have the same issues when run in windowed mode?

It looks like you might have got your answers on the Retroarch forum, but you are mixing overlays and full screen Mega shaders. These shaders HAVE to be in full screen scaling, not core provided. If you want to use some overlays, you have to add them and manually override them in a slang override. For example, I use Duimon's shader, but prefer my overlay images, so for the bsnes ocre I have a core slang override that has the following: Basically all that does is use my image and make the frame a bit smaller. The result looks like this:

Without knowing the exact settings and shader you are using it's hard to say, but I can say that sometimes with the larger screen size it can look closer to right but it isn't. Could you post a picture of a 4:3 game and exactly the settings for Video -> scaling, the overlay you are using (from where, bezel project), and the exact shader used?

Most games are 4:3 or 3:4 aspect ratio and when set to core provided that is normally the game size that is set. When you enable overlays, it draws these bezels outside that play area. Using the Mega shaders, they expect to have your full screen size to work. (This has nothing to do with the game resolution) Within that full screen, they create the fancy effects and they also create the frame and bezel and than embed the game playfield as well. Hope that makes sense and helps. (look at your first image and see how its drawing a frame and game inside that smaller 3:4 aspect)

Yes the Mega shader expects the scaling to be set to full. What it appears you have, is it is set to 3:4 or core provided. So the core thinks the game area is that small size, and then the shader is expecting the full screen size and it creates it frame, with what it expects is the full screen ibut it is being forced into the smallwe core provided size. Addionally I'm not sure you can use the normal Retroarch overlay method with the full screen shaders, without an override for the game that points the shaders bezel image to your image of choice.

Two things: Are you sure you don't have overlays on as well Do you have scaling set to full in the video options when using the Mega bezel shaders? (I can get the same behavior by setting those)

There's also a fixed version that works perfectly with that core.

Some devices can have multiple entries in Device Manager. I try to keep my matching ID as short as needed. Although rare, I've seen a windows update that slightly changed the longer ID info. As an example, I just match the following for my Logitech wheel Glad you got it working.

If it's matching correctly it should show the number you assigned to it. Running from a command prompt or from Powershell with the verbose option (-v) should show if it remapping correctly.

I've been back and forth as well and finally settled on the following: Thies shows all Arcade games in the top level (which most people only need, especially when browsing), but gives me the By system for easier media scanning or specialized tools I need for those platforms.

Who hasn’t wasted time on simple syntax errors like that? I guess it the same reason writers have editors, you read what you know it should be and not what you wrote. 🙂 As a habit I don’t trust copying and pasting in web browsers, (At least on Windows), unless the paste as plain text option is available. I don't think it's right in the original post either... so you are forgiven. ☺️