GroovyMAME/GroovyUME 0.149 SwitchRes v0.014b

[lettuce]

Do you have a download link for Arcade OSD, cant seem to find it anymore

[rCadeGaming]

Use version 1.3 at the bottom of the list here:

http://mame.3feetunder.com/windows-ati-crt-emudriver/

[lettuce]

Yeah it has loads of resolutions in the video mode list

[lettuce]

Any ideas?, game loads fine until I go into Mame.ini and change the display type to 'lcd' then if will give me the above error

[Calamity]

Hi lettuce,

The log you posted yesterday said your monitor was set as "custom", not "lcd". Can you post the one that reflects the problem with the lcd setting?

[lettuce]

Ahh sorry heres the correct one....

[Calamity]

Ahh sorry heres the correct one....

Ok, the issue may be you've been messing with the "screen" option in mame.ini. Try restoring its value to "auto". If you prefer, start with a fresh mame.ini by using the -cc command.

[lettuce]

Ok, have tired that but still the same issue..........

[Calamity]

Ok, now at least it's reporting the modes, so the problem is different. Is hlsl enabled? Try disabling it for testing.

[lettuce]

No nothings enabled, its a vanilla mame.ini, the only thing i changed was the monitor to 'lcd'

[Calamity]

Have you tried forcing the screen option like this:

-screen \\.\DISPLAY2

[lettuce]

Ah that appeared to work. Why am i needing to force the display?

Also what settings should i enable in mame.ini for the HP LP2065 monitor considering it can do low refresh rates? Will be trying to get an authentic arcade CRT look on it with the help of HLSL

[lettuce]

Ok enabling HLSL causes the same problem even if i force the display?

[Calamity]

Hlsl is broken in last version of MAME, well it works as long as you launch a single game, but if you use the internal menu for launching games it will crash. Damn hlsl (sorry). If it just crashes whatever you do then possibly you need to update DirectX

[lettuce]

Yeah i have the latest version of DirectX. Does it even if im launching 1 game........

[Calamity]

Do you have the full hlsl folder available with the fx files in it? The log is complaining about notfinding that.

[lettuce]

yeah it was, had to delete the folder and install it again, seems to work now

[Haggar]

Hi.
With groovymame 148u2 (windows) I have problems with vertical games (with horizontal games all is perfect).

When I run a vertical game it seems that groovymame enters a loop where it tries continuously to change the resolution (the screen blinks).

I created a fresh new mame.ini: the problem appears when I put "-modeline" option to 0.
I have "-modeline" setted to 0 because with "-monitor" option (pre-defined or custom made) I can't obatain correctly horizontal stretched resolutions (I get some res. ok and some other narrow) so I'm ok with my custom made resolutions.

With 147u3 all was ok.

Any help appreciated and thanks for the great job.

[Calamity]

Hi Haggar,

Please post a log of this, I need to see what's happening for a possible fix. I never use GroovyMAME without the -modeline option so I don't detect these issues myself.

As I have explained many times, disabling the -modeline option also disables the pick_best_mode logic built in GroovyMAME and all the throttling decisions are made based on that. The -modeline option should never be disabled, it's just there for testing purposes. You'd better find the right specs for your monitor.

It's funny that the most experts users are the more reluctant ones to using the built in modeline engine 

BTW, the 0.147u3 and the current patch are just the same, you shouldn't see different behaviour actually.

Future versions will have this -modeline thing redesigned so people can use their own custom modelines without compromising the normal behaviour.

[Haggar]

Please post a log of this, I need to see what's happening for a possible fix. I never use GroovyMAME without the -modeline option so I don't detect these issues myself.

Sure, I'll post it this evening.

As I have explained many times, disabling the -modeline option also disables the pick_best_mode logic built in GroovyMAME and all the throttling decisions are made based on that. The -modeline option should never be disabled, it's just there for testing purposes. You'd better find the right specs for your monitor.

I know that, but after many failing attempts to find a right monitor spec I decided to go through the dirty standard way.

Future versions will have this -modeline thing redesigned so people can use their own custom modelines without compromising the normal behaviour.

That sounds promising. 
You are always the n.1

[Calamity]

I know that, but after many failing attempts to find a right monitor spec I decided to go through the dirty standard way.

But when you say some games are too narrow, do you mean horizontal games or just vertical-rotated games?

[Haggar]

I mean horizontal games.

For example:
384x224 games (like capcom SF) are ok
288x224 games (like splatterhouse) are narrow

I've tried many custom monitor specs but there were always resolutions too narrow or too large so I've decided to stay with my "fine tuned" custom resolutions.

PS: I have a standard 15KHz Intervideo "VP series" arcade monitor.
From the manual:

Code: [Select]

Horizontal scan freq.: 15.625KHz +/- 500Hz
Vertical scan freq.: 50Hz

[Haggar]

Here the logs.

In fact with 147u3 I have the same problem. 146u4 worked fine.

The rom i've used is "wiz".

[Ansa89]

Patch updated for MAME 0.148u4.
Please test it before upload on the official site.

[Calamity]

Here the logs.

In fact with 147u3 I have the same problem. 146u4 worked fine.

The rom i've used is "wiz".

Hi Haggar,

Sorry for the late answer. Yes, I see the problem. You can probably fix it by disabling the -changeres option in mame.ini

(This is not required when using the -modeline option)

[Calamity]

Patch updated for MAME 0.148u4.
Please test it before upload on the official site.

Thanks a lot for the update. Are any major changes of the patch needed for this u4 update?

[Ansa89]

No, just some "hunk succeeded at ...", a "fuzz 1" and one hunk that was failing due to a new piece of code added to "sdlmain.c" (section "global variables").
So in the end no big changes.

[Rockman]

Thanks Ansa89!

[lettuce]

Ok have just compiled a 0.148u2 version of groovymame, and am interested in trying out the other console emulators. Do i have to compile UME aswell or is that already in the GM diff file?

[Calamity]

Ok have just compiled a 0.148u2 version of groovymame, and am interested in trying out the other console emulators. Do i have to compile UME aswell or is that already in the GM diff file?

You just need to create the UME binary, no need for more diffs. Read on the other thread.

[Haggar]

Sorry for the late answer. Yes, I see the problem. You can probably fix it by disabling the -changeres option in mame.ini

(This is not required when using the -modeline option)

Thanks, it works. Sadly that option is useful for many titles like strider 2, etc, so I have to disable it for all vertical games and I don't know how to do it automatically...

now triplebuffering is automatically triggered when the refresh difference if higher than specified by the -syncrefresh_tolerance option. As this is set to 2.0 Hz by default, it means that for 288-line resolutions, which usually won't run higher than 52-54 Hz on arcade monitors, -syncrefresh is turned off and -triplebuffer is used instead. This is great for non scrolling games like pacman. You can play with the -syncrefresh_tolerance option in order to decide how off the refresh must be for enabling this behaviour.

One question. Triple buffer introduces massive lag, so how can I be sure that groovymame doesn't use it? Someting like "-syncrefresh_tolerance 999"?

[lettuce]

Is it possible to send Groovymame to 2+ monitor at once, so they show the same display. I know you can setup the monitors to do duplicate displays in windows, but is there a way to do this through groovymame to duplicate the display?

[lettuce]

Mame was fine yesterday but today im getting.....

s224b.1a WRONG CHECKSUMS:
EXPECTED: CRC..blah blah blah
    FOUND: CRC.....blah blah blah
Warning: the game might not run correctly.

I have attached the log file

[yakk11]

Hi Calamity,

I am setting up my Taito Egret II for Groovymame and would like it to stay in 15khz mode.  How would I enter this line using new setup guidelines?  I have entered the info in vmmaker, but i am unsure how to enter it in mame.ini using new setup method.  Thanks for the help!

NANAO MS9-29 (retrorepair)
monitor_specs0    15450.00-16050.00, 55-65, 3.91, 4.70, 6.85, 0.190, 0.191, 1.018, 0, 0, 288, 448

[Calamity]

Hi yakk11,

Use this line:

crt_range0 15450-16050, 50-65, 3.910, 4.700, 6.850, 0.190, 0.191, 1.018, 0, 0, 192, 288, 448, 576

Make sure to also set 'monitor custom' in mame.ini for it to have effect.

[Ansa89]

I can't update the patch for MAME 0.148u5 due to heavy changes into mainline code (for example: "src/osd/windows/drawd3d.c").

@Calamity: I attach a "half-broken" patch (I fixed some hunk and fuzz problems) so you can concentrate only on the major update.

[Calamity]

Hi Ansa,

Thanks for this. Yeah I checked the git this morning and they're doing some bulk changes to the d3d source files. I haven't had the time to look through the code, but I suspect they are going to be modifying quite a lot of things during the next releases. This probably means we'll have to work hard if we don't want to go the way of AdvanceMAME.

[Ansa89]

Just one question: d3d is only for windows, right? If so, the patch should still working on linux...

BTW I agree with you when you say that for this (and probably next) release there will be a lot of work to keep the patch sync'ed with mainline source code.

[Dr.Venom]

Are the D3D changes the result of the HLSL updates (by Ryan Holtz) causing the incompatibility?

Do you gather it mostly needs "reshuffling" the existing GM code into the new code, or would it involve rewriting things?

[Ansa89]

I think that it needs the things to be rewritten.
For what I see a lot of functions have been renamed and/or heavily changed into d3d mainline code.