LCD_Range Glitch

[DJO_Maverick]

So I've found an odd edge case that seems vaguely related (maybe) to the AMD timings limitation previously discussed...

So as a workaround to that limitation, I've been setting GM to use the highest aspect-appropriate resolution that doesn't cause GM to freak out and give up.  Previously I used the older manual custom range for LCD (which you can see in there still), but then I shifted to the LCD_Range method when it became available.  Recently (not sure what build), that developed an issue where the first time I launch any game with MAME (on a given power cycle), it launches with incorrect timings and causes slow-motion, audio-tearing, unplayability.  If I exit GM...  then relaunch the exact same game (or any other game), it works exactly as intended.  That will be the case until I shut the cabinet off.

This happens 100% of the time for me, consistently and predictably.  Doing the exact same launch command twice in a row causes inconsistent results, and inconsistent logs.

With the two attached logs, paperboy1 is launching it as the first use of GM for a power cycle.  I closed it, then ran it again, and that generated paperboy2.  Absolutely no changes were made to configuration of GM, displays, system, or anything. 

And for clarity, it's not limited to paperboy; same thing happens regardless of what the first game launched is.  Seeking guidance, please.

Thanks,

[Calamity]

Hi DJO_Maverick,

By looking at your logs, I can see a difference between both. On the first log, the desktop is at 2560x2880, on the second one, the desktop is at 1920x2160. I don't understand why this is the case, maybe as a consequence of launching GM the first time, the desktop is left at 1920x2160, although this should not be the case.

Whatever it is, in the first log adding the custom mode fails due to the high pixel clock of the higher resolution, while on the second case it works because the resolution is lower.

With the lcd preset, GroovyMAME always picks whatever is the current desktop resolution and locks all others.

[DJO_Maverick]

Setting aside a moment the mystery of why it thinks the desktop resolution was altered when it wasn't-

My prior workaround has been to set the desktop to 1920x2160 full-time, which dodges the pixel clock issue.  It's desirable to have it set to the native resolution (2560x2880) for things on the cab other than mame, however.  Is there a setting in the ini that would work with LCD Range to limit it to 1920x2160, overriding the desktop resolution?  Or is the custom range method the only way to accomplish that?

Thanks,