Software Support > GroovyMAME

Radeon HD 2400 - Multiple resolutions in game ini?

(1/5) > >>

retrorepair:
I've come across an issue with my setup, ST-V games use at least 3 different resolutions. While it's interlaced resolution of 704x448 works fine, both 320x224 and 352x224 are a garbled mess.

I had a similar issue with Mortal Kombat though one resolution was enough in the ini. What do I do when I need to replace one or more resolutions while leaving the others?

I thought of adjusting them with arcade_osd but 320x224 doesn't appear since my dotclock won't do lower than 7.3 (Radeon HD 2400) and 352x224, while a mess in groovymame just bluescreens in arcade_osd.

Any ideas?

retrorepair:
I've actually just noticed when I go through the test menu (by memory, I can't see a thing) and select CRT test, it comes up and looks great, but according the switchres' output, it's the same 320x224@59.76 resolution that shows up as a scrambled mess when it first loads  ???

Interestingly enough, when I force it to 320x224 in the game ini like so:


--- Code: ---mode          1
resolution    320x224

--- End code ---

the first screen comes up ok (albeit slightly squashed in the middle) and the CRT test screen looks great again ???

I guess switchres is doing something it's not telling me about?

Calamity:
Hi retrorepair,

There's definitely something odd with your setup there, you shouldn't need to use inis at all if everything works as it's supposed to, even with games that switch resolutions.

I'd like to see some logs in order to find the issue. That will show us the list of available modes installed in your system.

Just run some of the problematic games like this:

groovymame romname -v -md 4 >romname.txt

and attach the file here, that will help us to see what's happening.

retrorepair:
Oh that's odd then. Nearly all games work great aside from those attached (they represent the drivers whos resolutions are screwing things up).

So even with a Radeon HD 2400 I should get all resolutions? I thought that due to the high dotclock it wasn't possible?

Calamity:
Thanks for the logs!

I think I know what's happening. However the fact that mk resolution doesn't work would mean that you probably should set the dotclockmin value to a higher safe value like 8.0

Follow these steps:

- Recalculate modelines with VMMaker, dotclockmin = 8.0, monitor GENERIC (wasn't it?)
- Restart
- Edit mame.ini and set the same values for the dotclockmin and monitor type options used in vmmaker.ini (8.0 and GENERIC, this is what probably was missing before).

Navigation

[0] Message Index

[#] Next page