damageinc86

Thank you so much for the reply! I can absolutely wait for any subsequent versions, in order to be able the checkbox that.

Just on the off chance this is a beta issue: So I just had to import/add a new Arcade game into my Arcade platform, so I added my Override Default Startup Screen Settings, to duplicate what my entire platform has: So,...only on the freshly imported two new games I've added to the platform does it now completely fade out the start up screen (theme) all the way to black,...then wait for retroarch to start up, and retroarch takes over as usual. With EVERY other game that was existing and has these same exact override settings that I set about a year ago,...the start up screen (theme) remains up the entire time as it usually has done, all the way until retroarch takes over. So for some reason, on a freshly imported game, set to the same override settings,...it fades out to complete black wayyyy before retroarch takes over, and I have no idea how to fix it to behave like it should and has for every other game in the platform. I don't remember this happening before on any new imports,...Any help? Is this a new beta issue? i dunno. I'm at a loss. ****EDIT: Looks like Post-launch time is actually affecting the launch duration that the startup screen is being shown for. Which doesn't make sense, since that's what the Startup Load Delay should be affecting. If i set it to .02 seconds, it shows the startup screen that quickly, then fades to black,...and waits the allotted startup delay (7.125 seconds) duration and then shows the emulator. If I set the Post-Launch Display time to 5 seconds, then it shows the startup screen for 5 seconds, fades to black, and then waits for the emulator for the 7.125 seconds. It didn't behave like this before.

So I just had to import/add a new Arcade game into my Arcade platform, so I added my Override Default Startup Screen Settings, to duplicate what my entire platform has: So,...only on the freshly imported two new games I've added to the platform does it now completely fade out the start up screen (theme) all the way to black,...then wait for retroarch to start up, and retroarch takes over as usual. With EVERY other game that was existing and has these same exact override settings that I set about a year ago,...the start up screen (theme) remains up the entire time as it usually has done, all the way until retroarch takes over. So for some reason, on a freshly imported game, set to the same override settings,...it fades out to complete black wayyyy before retroarch takes over, and I have no idea how to fix it to behave like it should and has for every other game in the platform. I don't remember this happening before on any new imports,...Any help? Is this a new beta issue? i dunno. I'm at a loss.

heck yeah! that would be phenomenal. I'm not sure it will get upvoted much more,...it seems like one of those things people don't really know they need until they need it maybe? lol. In any event, sounds promising! I figure by now, so many big issues have been worked on, that maybe some of these small qol things finally get their time to shine! It's been a pinch point in my setup for over a decade now, so hopefully there is some light at the end of this tunnel. thanks for the response!

Well the over 10 year old bitbucket issue has disappeared because they moved from bitbucket to a new feedback system. But that issue is here: https://feedback.launchbox-app.com/p/individual-controller-mappings-for-lb-navigation/comment/67f8079f5317ae6b9c611469 In a nutshell, Button 1 for say "ENTER/SELECT", will not always be the same button on every controller you have plugged in (xbox, ps, switch, snes, nes, gamecube, n64 hori, etc.). So if you map button 1 to be able to select something in bigbox, e.g., "ENTER" to start the game after scrolling to it,...and you pick up the gamecube controller to do so, and you press what you feel should be the select button, say the A button,...but that's not button 1 on that controller,...it is button 2,...then that is unfortunate and annoying. So if they gave us the ability to keymap PER-controller mapping for navigating big box, we could then pick up any of our controllers and the buttons we mapped to button 1, will always be the "ENTER.SELECT" button no matter what. Launchbox can do this,...it just needs to be programmed. And no,...using joy2key on top of launchbox, JUST for navigation, is silly since it should really just be a quality of life function programmed into it.

can we map bigbox navigation controls per-controller yet? been over 12 years now. Please someone, anyone. get in there and add this QOL functionality.

oh cool, nice touch!

is this an imagining of what the bezel could be? or is this an actual facsimile of an existing bezel?

oh so you used the standalone then? I thought it was only for dragon's lair lol. Guess I should go investigate that again.

You mean the standalone Daphne emulator? The Daphne core in retroarch didn't even load the game.

well dang, this made me want to play the game, but mine is stuck on a start up screen with just the words "stand by" in the middle. It never loads anything though.

looks like it got taken down.

Is there per-controller big box navigation key-mapping yet? So for instance, if button 5 is start on one retro usb controller, the user can map that to Enter, and then if button 2 is start on another retro controller, the user can also map that to Enter. That way the user can pick up any of their usb controllers and have their respective start buttons all press Enter for Big Box Naviation. I think it has been almost 10 years since the first bitbucket issue posted on this lol.