New game import, override startup screen now introduces a fade out before emulator???

[damageinc86]

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.  

Edited October 26 by damageinc86

[JoeViking245]

11 minutes ago, damageinc86 said:

Is this a new beta issue?

Not sure either.  But if by chance it is, it'd probably be best to post this in the beta thread.

[Noah Thompson]

If the override is a direct duplicate of the platform settings, the fade timing shouldn't diverge just because the game is new — that points to something else in the chain (theme transition vs. emulator startup) rather than the override itself. In Denver I've seen similar one-off quirks clear up after re-saving the override, since a freshly imported entry may not have picked up every inherited parameter. Worth testing: duplicate one of the older games that behaves correctly and compare their config entries side by side. That should narrow it down before assuming it's a beta regression.

[JoeViking245]

48 minutes ago, Noah Thompson said:

In Denver I've seen similar one-off quirks

What exactly is "Denver" that you're referring to?

[damageinc86]

On 10/27/2026 at 10:16 AM, Noah Thompson said:

If the override is a direct duplicate of the platform settings, the fade timing shouldn't diverge just because the game is new — that points to something else in the chain (theme transition vs. emulator startup) rather than the override itself. In Denver I've seen similar one-off quirks clear up after re-saving the override, since a freshly imported entry may not have picked up every inherited parameter. Worth testing: duplicate one of the older games that behaves correctly and compare their config entries side by side. That should narrow it down before assuming it's a beta regression.

Turns out it wasn't a beta regression, but was an issue.  These quircky things sometimes end up only being noticed when someone like myself, hasn't had to import a new game in literally years, and then all of the sudden has to due to finding out about it during an artwork project. 

It has since, been addressed and I was able to get the newly imported game startup issue to get back to behaving as it did prior to when I posted about this issue.

Edited yesterday at 06:02 AM by damageinc86