Doing wierd hacks to get interlaced resolutions working???

[emubastard]

I can't be sure if I'm doing this right, but it seems the only way to get interlaced resolutions to work on my setup was to specifically make a 482i resolution.  If I have both 2560x480@60 and a 2560x480@30 listed in user modes, only the 480p is generated (or possibly whichever one was seen first).

It seems that groovy mame will not switch to 480i, but will switch into 480p.  So how I've hacked around this, and I don't know if this is right, is creating special resolutions for 482i (480i), 514i (512i) etc so that interlaced and progressive resolutions don't share the same resolution.

Not sure if this is how I am suppose to do it,  My monitor can do both 480i and 480p resolutions and I have roms that do either as well.

I'm attaching my files and hopefully someone can tell me if this is insane, or the only way to get 480i and 480p resolutions at the same time.

What I did was on the few games I know are interlaced, I set up an ini for them and told them to use 2560x482i so they wouldn't display in progressive, although I'm not sure if it's being scaled correctly in interlaced mode as it looks a little off....

Otherwise this seems to actually work other than I have to make ini files for the interlaced games to force them to the slightly off interlaced resolutions (and there aren't many).

-Bastard

[haynor666]

I have similiar problem - many interlaced resolutions shows up as native modes and groovymame wont pick them up for use. Please run ArcadeOSD and see if those modes are native or custom.

[Calamity]

I have similiar problem - many interlaced resolutions shows up as native modes and groovymame wont pick them up for use. Please run ArcadeOSD and see if those modes are native or custom.

Different issue.

[emubastard]

Well 480p show up as custom and do work...

I'm wondering if this is just a windows limitation, as in 2 identical resolutions can't be both interlaced and progressive.

And since this works, and if that's the case, maybe Calamity can make a little bit more graceyful way to deal with it.

[Calamity]

When you use a multi range monitor preset, the modeline generator always tries to get the best quality mode, so if the mode is possible in the progressive ranges the interlaced version will be discarded.

You don't need to create two instances of the mode, one interlaced and one progressive. You can just create 480p and GM will convert it to interlaced if required.

The problem is if you use the same multi range preset in GM, it will do the same thing as VMMaker. So what I'd do is, use an ini file for the game you want to force to interlace, and copy in it the 10 crt_ranges, but set the upper ones to "auto", so it will be force to use the lower one.

[Calamity]

I'm wondering if this is just a windows limitation, as in 2 identical resolutions can't be both interlaced and progressive.

The way they did it for W7 was to label interlaced as 30 Hz and progressive as 60 Hz, so they can coexist indeed.

[emubastard]

So let me get this traight, get rid of my 482, 514 and 575 interlaced specific crt modelines from my monitor.ini and then force interlaced through the ini files (which I am doing but can use 2560x480@30 proper instead) ?

And what do you mean "labeled them".  How is that done?

-Bastard

[Calamity]

Using these presets as an example, because they are simpler, say you have this:

      crt_range0  15625-16200, 49.50-65.00, 2.000, 4.700, 8.000, 0.064, 0.192, 1.024, 0, 0, 192, 288, 448, 576
      crt_range1  24960-24960, 49.50-65.00, 0.800, 4.000, 3.200, 0.080, 0.200, 1.000, 0, 0, 384, 400, 768, 800
      crt_range2  31400-31500, 49.50-65.00, 0.940, 3.770, 1.890, 0.349, 0.064, 1.017, 0, 0, 400, 512, 0, 0

If you make it calculate 480, it will do it progressive, using the range 2.

If you want GM to calculate it interlaced, instead of specifying a resolution, specify a custom preset like this:

      crt_range0  15625-16200, 49.50-65.00, 2.000, 4.700, 8.000, 0.064, 0.192, 1.024, 0, 0, 192, 288, 448, 576
      crt_range1  auto
      crt_range2  auto

And what do you mean "labeled them".  How is that done?

The os does, it's beyond our control.

[emubastard]

And i finally figured it out...

I had

resolution 2560x512@30

In my journey.ini but it only worked if I did

resolution 2560x512@0

It did not like 30.... is that normal?

I've been touching up my crt_ranges continously but here is my journey.ini file now...  I just happen to like my aspect ratio better for this game...

resolution 2560x512@0
aspect     3:2
crt_range0 15000-16000, 54.80-62.00, 3.632, 3.374, 10.291, 2.116, 1.786, 0.066, 0, 0, 192, 192, 0, 0
crt_range1 16001-17800, 54.80-62.00, 1.950, 9.400, 2.368, 1.370, 0.526, 0.894, 0, 0, 224, 246, 448, 492
crt_range2 17801-19100, 54.80-62.00, 1.887, 8.491, 2.462, 1.370, 0.526, 0.894, 0, 0, 248, 264, 496, 528
crt_range3 auto
crt_range4 auto
crt_range5 auto
crt_range6 auto
crt_range7 auto

[Calamity]

You shouldn't need to add the resolution option to the ini at all.