Hamburglin

Ok yeah I saw that one. It seems like platform and playlist selection still beeps though.

I like leaving attract mode running with low volume so people can hear the games video's gameplay. However the "select" ping sound is really annoying when it's switching through platforms and playlists. It's louder than anything else. How do I disable this sound when attract mode is running?

Same. It's a multi layer mess of mapping mame controls -> retroarch controls -> xinput so I just gave up. There must be an easier way to map this.

I finally found them in case anyone else ever needs this: C:\Emulation\LaunchBox\Images\Playlists\Arcade 2-Player Games I kept looking in themes.

I made a custom platform category with custom playlists below it. I want to set some of them up with the banners and clear logos from the Default theme. However, I can't find the image files anywhere in the launchbox folder. Where do these image files exist? I remember that I could manually save the images by right clicking them in the edit menu from categories and playlists (like the auto generated Arcade ones) but I deleted those before we had the option to ignore categories and playlists in big box.

I had the same problem and the image cache was the issue. Thank you!

I honestly have no idea what happened but I restarted for the 4th time about 2 hours later and they were back.

Anyone one know what's going on? The playlists exist but the gray boxes (in the default theme) are empty. The games themselves exist as well, but the gray box is empty too.

Please ignore. I had something underneath my control board constantly pushing a button 😁

I just confirmed that it is an issue with the way the Pacto 4000 xinpit board interacts with big box's input mapping. I used an 8bitdo xinput controller to remap my bindings.

Ok, I'm thoroughly confused. My Xbox controllers are working in big box and in all of my emulators as xinput. However, when I go to change Big Box's controller mappings, nothing is read from my controllers. If it matters, I'm using a Pacto 4000, which allows joysticks and buttons to natively become Xbox 360 controllers. The Cobtroller in big box is set to my.xbox controller "player one" Again, this works fine everywhere else. 😕

I can't map buttons/input codes to my LED Blinky ports because it expects direct input and I'm using xinput. I wouldn't have gotten LED buttons for my arcade cab if I knew this. For now, I just want to turn all of the LEDs on and to white. How can I achieve this in big box? Or is there a simpler way to turn them all on in LED Blinky's config? I haven't seen a way besides animations, and those don't run by themselves.

The problem is that the overlays are part of the save and override system at all. That's besides how confusing the override system is in the first place for the end user. Just imagine if they decided to add a message alongside the failure message of "... because you are using a game override". Doesn't seem hard to do. The code is already there to check for the issue. They just need to change the message when it fires.

Ok! Thanks for your hunting guys. Suffice to say I'm not iincredibly surprised given retroarch's already-confusing options hierarchy and *various* "save" settings and overrides.

Dare I say this is almost a bug with the override implementation then. It's an unintended consequence at best. How does standalone retroarch implement overlays? Is this a LB issue + retroarch issue only?

I made sure my user has full control over launchbox and my Emulation folders

Interesting. I thought the behavior felt erratic but I didn't test. I was hoping it was just a bug in the latest betas.

Yeah, makes sense now. I did try setting the resolution of supermodel3 down from 2560x1440 to 1920×1440 and in windowed mode but that didn't Work either

Yeah, demulshooter with sm2 for dual light guns. So demulshooter knows what's up when it comes to this stuff.

The crosshairs don't go into the bezel area. That part's fine. The problem is that having gun4ir set to content aspect ratio of 133 (4:3) for those games makes the crosshair offset from your actual line of sight the closer you get to the edges. The crosshair is in the wrong position. It's the same effect when you have gun4ir on 133 but go to the test screen and aim towards the sides of the screen, and there's no way to fix this in supermodel and flycast. You're forced to use fullscreen aspect ratio in gun4ir which is a pain because mame and sm2 in their regular aspect ratios (and getting the cool bezels!) uses content aspect ratio of 133. Anyways, I'll look into switching with additional apps!

Yeah that's exactly what I'm saying. Mame and sm2 does the 4:3 aspect ratio mouse restriction well but flycast and super model 3 don't. They let the mouse go to the widescreen edges even when the game screen is only in 4:3 which means um forces to used fullscreen aspect ratio for thise emulators. I'll look into using LB to set those with additional apps. I guess the problem with that approach is that the mouse devices and com ports might change order at some point.

Man, I finally figured it out... I needed to: Set the resolution to match my monitor: 2560x1440 Right click supermodel, go to properties, compatibility and check "Disable fullscreen optimizations" "Change High DPI Settings" -> "High DPI Scaling Override" set to Application Wow, that was frustrating! Secondly, I can't figure out how to get gun4ir to work in 4:3 content aspect ratio of 133 with this, just like flycast. It's like they don't report or send 4:3 coordinates even if the game is always in 4:3. They send 16:9 coordinates which warps the aim the closer to the edges of the screen you are. But both emulators does work when the aspect ratio is set to fullscreen in gun4ir (which I don't want because I don't stretch the 4:3 games to 16:9).

Thanks. Need to get some rest but will try this tomorrow.

I switched the gun mode over but it's still having the same exact issue. I'm at a loss. There must be something super obvious I'm missing, or something unique with gun4ir I missed. Here are all of my settings: https://ibb.co/ZHZns39 https://ibb.co/p1L9167 https://ibb.co/hC0jqYK https://ibb.co/fG81973 https://ibb.co/gz9Y9VK And this is what it looks like in game when I try to calibrate: https://ibb.co/cgCjN5V Where red cursor and blue in game dot is WAY OFF from where my gun is pointing, but aligned with each other. Something else I just noticed is that the blue dot for the in-game coordinates will not go anywhere but the top left quadrant after calibrating to the middle of the screen: https://ibb.co/PM8MwSM https://ibb.co/xJPVJtw Even stranger, if I point my gun to the top left corner, my gun's physical sights and the red cursor align, and if I calibrate that point as if it was center, then the blue square is actually centered! So yeah, any of the lightgun guns work perfect if I'm only aiming at the top left corner. By the time I aim down-right towards center, the actual crosshair is already at the bottom right of the screen. It's like the coordinates are getting multiple somehow. This problem exists in dinput too when using MOUSE. HOWEVER, if I use my real mouse, it does not have the weird acceleration/offset issue that my gun4ir guns do....... https://ibb.co/zP8RzmZ And just to prove that my gun4ir is setup correctly, here is the test screen with the aspect ratio set to fullscreen: https://ibb.co/m9Jnw2c And demulshooter's dsdiag: https://ibb.co/wLbwCKN Notice the physical sights aligns with the drawn crosshairs.

Thank you! I'll try this later.