Software Support > GroovyMAME

Groovymame, Linux, Super Res and Scaling

(1/2) > >>

As the subject states, I am trying to get a handle on groovymame in Linux with super resolutions and scaling. I just want to confirm if I am missing something before proceeding with a work around.

The details:
Goovymame: 0.227
Linux Kernel: 5.13.0-27-generic
Video: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)

Super resolutions do not work with 'super_width 2560' set in mame.ini
If I set 'resolution 2560x0' then it will use that width but everything is squished.
So I compensate with 'intscalex 10' to fill the screen.
Works great and plays great for games that are 256 width.
Once I run a game that is not 256 width then the scaling is all wrong. I can change the resolution and scaling to work with the different width games, but obviously not a smooth way to launch games.

Just wondering if anyone has some thoughts on what I maybe missed. Otherwise I will script a work around.


Oh my ... You're giving too little information. Please tell more about your GPU, it's the main point of Linux CRT gaming.

Super resolutions do work, and you don't need to set any scaling parameter. The only ones that matter are monitor and modesetting.

But as you're on linux, why bother with super resolutions ? Don't transpose windows habbits on Linux, it doesnt work the same way. Linux can run at native resolutions (depending on your GPU, hence my very first question). If you must use super resolutions (this happens for GPUs that can't do low dotclocks : Intel and Nvidia mostly, AMD/Radeon do low dotclocks just fine), just set the min_dotclock to 25.0.

Now I'd recommend using the collaborative GroovyArcade OS. All of this is mostly automatically handled, and the bare minimum required patches are applied (Linux, SDL2). Otherwise, you need to compile your own kernel with some patches here and there, you're stuck with never updating, when GroovyArcade always has updated packages.

Thanks for the reply, Substring.

GPU chip set above, in this case is Intel, so yes, no low dotclock.

The goal of the project in question is to have a centralized launcher/frontend to remotely launch games on my various cabinet/CRT configurations. I am not overly concerned with kernel patching as I only power on the CRT (remotely) once the game has successfully launched in a 15khz res (No boot or native frontend needs to display).

I have a windows box with an ATI GPU for testing and generating different mode lines. But I want to stick to Linux as it makes tinkering easier. Being able to have a Linux box spun up, emulating games or playing videos on a CRT quickly is key.

I will set the min_dotclock as suggested.

I follow the GroovyArcade project on discord and am excited about the KMS work. I'll take a look at incorporating GA into my project once I get the automation kinks ironed out and setup is pretty turn key.

Thanks again!


--- Quote from: OverRide on January 26, 2022, 11:44:47 am ---The goal of the project in question is to have a centralized launcher/frontend to remotely launch games on my various cabinet/CRT configurations.

--- End quote ---
Sounds like an interesting project, I hope you share more details when you have it finished.

the kernel patches are not just for 15kHz "boot" (well rather kernel load time) resolution, but also to fix a speed problem with interlaced.

We've also had successful  test of powering on and off a monitor using a USB relay. Looks like it could work great for you so you could remotely turn on and off your tv/monitor


[0] Message Index

[#] Next page

Go to full version