Arcade OSD, super resolutions and porch values

[jimj]

First, I apologize for asking something I'm sure has been asked before, but with Google as my witness I can find a post on this... 

Second, when running Arcade OSD with a non-super mode I see a cross hatch display with a white border around the entire display and a white X that's centered on the screen as is seen in this picture (I'm to able to post my own pictures in this forum):

...

But when I edit a super mode there are only white lines on the top and bottom of the screen and the diagonal white lines no longer form an X through the center of the screen, instead they make squished white triangles on the left and right side of the screen as shown in this picture:

I assume not having an X or white lines on the side is a normal/expected side-effect of using super resolutions?

Third, I've seen many posts about changing the front and back porch values to change the horizontal positioning of the screen.  However I can't change porch values for super resolutions.  I assume this is a normal/expected side-effect of using super resolutions?

[xbrunox]

If u use groovymame super resolution are generated at the moment using crt0 settings in yours mame. Ini

So for change porches in groovymame u must edit that line in mame. Ini

[makya]

The white lines and cross you describe are the same for me, I assume this is normal.

Modifying super resolutions porches works the same as for any resolution. What makes you think it's not possible?

Well if you are trying to change your current desktop resolution however it will look like your changes have no effect.

[jimj]

The white lines and cross you describe are the same for me, I assume this is normal.

Modifying super resolutions porches works the same as for any resolution. What makes you think it's not possible?

Well if you are trying to change your current desktop resolution however it will looks like your changes have no effect.

Thanks for confirming what I see is normal.  You also prompted me to figure out my porch problem.  It was a user error of course.    For some reason with my super resolution modes I went into the "Edit modeline" menu when the porch settings are actually in the "Horizontal geometry" menu.

Now maybe I'll have chance of following the instructions here to use the porch settings to shrink my screen horizontally a couple centimeters to avoid the right side horizontal linearity issue (squeezed right side issue) with my KT-2914 Betson-Kortek 27" multisync monitor.

Another thing I'm not clear on yet are the pros/cons of using proch values to shrink my display horizontally versus just using the Betson monitor's OSD controls to achieve the same thing.  I assume if I had a good understanding of how to correctly use modelines, that by using porch values I could shrink the display for just the games that are affected by the linearity issue whereas using the Betson OSD controls would affect all games.

[makya]

The "edit modeline" menu allows to modify porches as well, just another way to do it.

Anyway be aware that modifying modelines in arcadeosd should not have any effect into groovymame, assuming you installed crtemudriver in dynamic mode.

The way I  use customized modelines is, like you are assuming, to avoid constant tinkering with monitor osd or pots.

[jimj]

Anyway be aware that modifying modelines in arcadeosd should not have any effect into groovymame, assuming you installed crtemudriver in dynamic mode.

Thanks for the reminder.  I'm using super resolutions and my understanding is that Arcade OSD's "Save changes" option doesn't affect GroovyMAME.  Instead I need to "Copy modeline to clipbard" and then use those values in Video Mode Maker.

For example, if I want to create a new "2560x238_58" modeline I believe could:

• Edit an existing modeline (for example 2560x240_59) with Arcade OSD
• Choose "Copy modeline to clipbard"
• Paste the modeline into notepad, should look something like this:
• • modeline "2560x240_59 15.40KHz 58.78Hz" 47.43 2560 2568 2808 3080 236 243 246 262 -hsync -vsync
• The first value is just a label.  Because I edited my "2560x240_59" mode it still has that label.  Therefore I'll update the label to "2560x238_58" so it now looks like this:
• • modeline "2560x238_58 15.40KHz 58.78Hz" 47.43 2560 2568 2808 3080 236 243 246 262 -hsync -vsync
• Open Video Mode Maker and enter these commands to install the new modeline:

Code: [Select]

>>modelist import
>>modelist list
>>mode add "2560x238_58 15.40KHz 58.78Hz" 47.43 2560 2568 2808 3080 236 243 246 262 -hsync -vsync
>>modelist list
>>modelist install

Or if I wanted to edit an existing modeline I believe this method would also work:

• 1.  Edit an existing modeline (for example 2560x240_59) with Arcade OSD
• 2.  Choose "Copy modeline to clipbard"
• 3.  Open Video Mode Maker and enter these commands to export the existing modelines to a file:

Code: [Select]

>>modelist import               
>>modelist export modelist.txt     


• 4.  Open modelist.txt in Notepad and paste in the new modeline from Arcade OSD over the old modeline I edited
• 5.  Open Video Mode Maker and enter these commands to import and install the new/modified modelines from modeline.txt:

Code: [Select]

>>modelist import modelist.txt
>>modelist list
>>modelist install


[makya]

Well, I don't know about this method, what does it do? It looks like it does not affect gm to me, does it?

[jimj]

Well, I don't know about this method, what does it do? It looks like it does not affect gm to me, does it?

No, it doesn't affect GM.  I'm obviously missing a big piece of understanding.  However I got my original questions answered, so I'll keep reading and start yet another new thread if I can't figure this part out.  Thanks for your help.

[makya]

To have an effect in gm you can use crt_ranges. These use timings instead of lines so you have to convert your modelines accordingly (timings can be found in arcadeosd).

[Calamity]

@jimj

GM calculates its own modelines on the fly, that's why Arcade OSD changes won't affect it. GM uses its own crt ranges as reference for geometry and timings. Current use of Arcade OSD is to FIND the correct values in order to build a crt range that GM can use, not to modify the modelines directly.

[jimj]

Thanks for the replies makya and Calamity.  I now understand that it's the crt_ranges that affect GM.  Unfortunately I more questions now.  In the STEP 3 - SETTING MAME UP instructions its last two steps are to generate and install modelines.  Since GM creates its own modelines are these last two steps necessary?  What uses these modelines?

[makya]

I do not use "Export settings to GroovyMAME" so I would say it's not necessary. I my understanding, it will copy VMM settings to mame.ini.

Otherwise, I see resolutions/modelines in arcadeosd as windows resolutions for your desktop and any other full screen software that does not create their own.

[mrchrister]

The way I use custom modelines is per game or system in GM. I believe in the ini dir you can create for example neogeo.ini or dkong3.ini and copy your custom modeline (crt_range) in there.
I use static mode because I had some trouble with dynamic mode btw.

[makya]

@mrchrister, what kind of issue did you get with dynamic mode?

[mrchrister]

I believe Retroarch didn't work with dynamic modelines... TBH can't remember, was so long ago. But all of my 3 setups are running with static modes now, seems to work well. I just added all modes I know are compatible with my specific CRT.

[makya]

Oh ok thanks.

@jimj, do you still have issues/things you do not understand?

[jimj]

@jimj, do you still have issues/things you do not understand?

I don't think there's enough space here to list all of my issues and things I don't understand! 

However, regarding Arcade OSD, VMMaker and GM I think I'm good now, thanks.  I appreciate all the help you gave me (and Calamity too).