GroovyMAME 0.289 - Switchres 2.22f

[arc11]

Last year while I was searching for a workaround, I found odd in the lines :

    // determine the scale factor
-   float scale_factor = target_font_height() * scale / one_to_one_line_height;
+   float scale_factor = std::min(target_pixel_height / float(raw_font_pixel_height) / options().font_rows(),
+                        target_pixel_width / float(raw_font_pixel_height) / options().font_rows());

that a division is made between
 target_pixel_width
and raw_font_pixel_height

if I understand correctly this expression the second line should be
target_pixel_width / float(raw_font_pixel_width) / options().font_collumns()

I don't know if  raw_font_pixel_width and font_collumns exist, i just put meaningful names

just an idea....

[Calamity]

Hi arc11,

Last year while I was searching for a workaround, I found odd in the lines :

    // determine the scale factor
-   float scale_factor = target_font_height() * scale / one_to_one_line_height;
+   float scale_factor = std::min(target_pixel_height / float(raw_font_pixel_height) / options().font_rows(),
+                        target_pixel_width / float(raw_font_pixel_height) / options().font_rows());

that a division is made between
 target_pixel_width
and raw_font_pixel_height

if I understand correctly this expression the second line should be
target_pixel_width / float(raw_font_pixel_width) / options().font_collumns()

I don't know if  raw_font_pixel_width and font_collumns exist, i just put meaningful names

just an idea....

Yes I understand why the code looks wrong. But it is right. There's no such thing as font pixel width (neither font columns). The only property that's defined for fonts is their pixel height.

The problem is this code in GroovyMAME is meant for integer scaling of bitmap fonts (.bdf fonts). Currently MAME defaults to a true type font that doesn't work so well when integer scaled, specially at extreme pixel aspects as the one you're using for the menu (768x240).

So probably I should make uismall.bdf the default in the provided mame.ini to avoid this problem in the future.

I took some time to replicate (sort of) your setup here, this is how GroovyMAME looks when -uifont uismall.bdf is used. The mode on screen is 768x240 (portrait / rotated).

[arc11]

Thanks for the reply

with this way of launching mame, the font is readable, but the menu is not as good as with the original mame code

[Calamity]

Hi arc11,

The picture should look exactly like the one I posted (I configured my system with your resolution to do the test). If it doesn't, there must be something else broken with your configuration.

EDIT: Make sure to set font_rows 30 in ui.ini.

[Calamity]

GroovyMAME 0.288 is out!

What's new in Switchres 2.22d (June 2026)

  - Lockless latency-optimized audio buffer enabling very low latencies with PipeWire on Linux, and lower latencies overall on Windows [intealls].

  - Set a default refresh for Switchres when no screen device exists (fixes hardlock on KMS).

[RobeeJ]

Thanks Calamity!

[JPetersen]

Thanks for 0.289! 

[Calamity]

Groovymame 0.289 is out (we had 2 releases this month, use the latest one):

What's new in Switchres 2.22f (August 2026)

- [intealls] Audio latency reduction and code fixes/simplifications:

    * For games not using VIDEO_UPDATE_AFTER_VBLANK, shave off vblank time for audio latency
    * Register minimum count buffer count across both audio updates for emusynclog
    * Update audio at m_vactive_ratio instead of 1.0, pushes audio earlier and reduces end-to-end latency, but maintains non-negative latency without -afd
    * Reduce minimum buffering latency to 0.1 ms, increase skip duration to 1 second, decrease minimum adjustment to 0.25 ms, only really matters for PipeWire
    * Fix XAudio2/WASAPI available() calculation
    * Add mutex for sink registration
    * Fix out-of-bound read resulting from fractional audio updates, fixes gyruss (and maybe others)

What's new in Switchres 2.22e (August 2026)

 - Properly store the current mode in the -nomodesetting case. Fixes redundant mode changes happening when the new mode is equal to the previous one (like with super-resolutions) and the mode change is delagated to the renderer (like with Windows d3d).