Main Restorations Software Audio/Jukebox/MP3 Everything Else Buy/Sell/Trade
Project Announcements Monitor/Video GroovyMAME Merit/JVL Touchscreen Meet Up Retail Vendors
Driving & Racing Woodworking Software Support Forums Consoles Project Arcade Reviews
Automated Projects Artwork Frontend Support Forums Pinball Forum Discussion Old Boards
Raspberry Pi & Dev Board controls.dat Linux Miscellaneous Arcade Wiki Discussion Old Archives
Site News

Unread posts | New Replies | Recent posts | Rules | Chatroom | Wiki | File Repository | RSS | Submit news


  

Author Topic: Groovymame 0.197 64bit screen won't centralise  (Read 1718 times)

0 Members and 1 Guest are viewing this topic.

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Groovymame 0.197 64bit screen won't centralise
« on: June 26, 2018, 09:46:54 am »
Alright all

I have moved to windows 7 64 bit now and have updated most of my emulators to 64 bit and am using super resolutions 2560x224, 2560x240 60hz etc.

I have just tried groovymame 0.197 64bit and I get a 1cm border on left hand side - the screen is not centralised, in the GUI nor the games, everything is shifted to the right. my resolutions are all centralised in arcade OSD and is not happening on any other version of mame nor any other emulator

I tried slider controls when in game and the screen won't go left beyond the 1cm black border on left side. This is ONLY happening in groovy mame

it is highly annoying me as I can't get a version of mame that works properly, other versions of mame don't scroll smoothly and you get a frame jerk every few seconds.

I have windows 7 64 bit home basic installed with direct x 11 and I also have installed direct x 9
 I've tried both versions of groovy mame 0.197

Thanks for your help all

buttersoft

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 656
  • Is running at 15kHz
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #1 on: June 26, 2018, 07:50:23 pm »
GM/switchres will calculate timings using the crt_range0 line in mame.ini (or any sub.ini as setup by you). ArcadeOSD doesn't change the mame.ini file. So grab your timings from ArcadeOSD and write them into the mame.ini file crt_range0 line. Or write those changes into the monitor.ini file and run VMM again. I prefer the former as I find different modes like slightly different timings.

It's only happening in GM and not other versions of MAME because only GM recalculates video modes to match the original hardware and give perfect results :) Other versions of MAME and other emulators will just use the modes as they find them, i.e. as modified/centered by ArcadeOSD. (Though i have no idea where retroarch or mednafen are up to with modifying modes).
« Last Edit: June 26, 2018, 07:54:47 pm by buttersoft »

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #2 on: June 26, 2018, 10:00:16 pm »
Thanks a lot
Can I copy and paste them from arcadeOSD? If so where can they be accessed as normal text? Thanks a lot

buttersoft

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 656
  • Is running at 15kHz
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #3 on: June 26, 2018, 11:16:22 pm »
Well, can you can copy a modeline to the clipboard in ArcadeOSD, But that's a modeline not a range line. You should probably just read the three horizontal timings and drop them into the right places.

i do not know which preset you are using, but below is the generic15 one, as an example. Replace the 3 bolded values with yours from ArcadeOSD, ignoring the rest - in ArcadeOSD you go into the modeline, adjust horizontal geometry to be correct, then read the values.

crt_range0  15625-15750, 49.50-65.00, 2.000, 4.700, 8.000, 0.064, 0.192, 1.024, 0, 0, 192, 288, 448, 576

If you want to know what all the other values in the range line are (it's not a modeline, it's a range line) take a look at the monitor presets sticky up above.
« Last Edit: June 26, 2018, 11:19:51 pm by buttersoft »

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #4 on: June 27, 2018, 03:58:57 am »
Yes thanks

but i cant just "Replace the 3 bolded values with yours from ArcadeOSD, ignoring the rest" as my mame.ini has all CRT_range set to just "auto" so I need to enter the whole range line

I have CRT_range then 0 through to 9 lines, so that means I have to set different resolutions up on each line? Like 224, 240 heights etc. And different speeds like 60hz, 55hz etc etc.?
 
Isn't there an option in groovymame to read screen values from arcadeOSD / registry? If not I don't know why not. I've read the monitor presets sticky post and I can't understand it, it's so much information to take in, it's too much of a headache, I've turned my PC off now

Here are my modelines for MAME, how can I get GroovyMAME to use them?:

Modeline "2560x224_54 15.5KHz 59.9Hz" 53.340 2560 2712 3112 3440 224 234 245 259  -hsync -vsync   
Modeline "2560x224_59 15.5KHz 59.0Hz" 53.380 2560 2712 3112 3440 224 236 247 263  -hsync -vsync
Modeline "2560x224_60 15.5KHz 59.9Hz" 53.340 2560 2712 3112 3440 224 234 245 259  -hsync -vsync   
Modeline "2560x232_55 15.0KHz 55.0Hz" 51.930 2560 2784 3096 3472 232 240 252 272  -hsync -vsync   
Modeline "2560x232_60 15.8KHz 59.9Hz" 54.600 2560 2784 3064 3464 232 239 243 263  -hsync -vsync 
Modeline "2560x240_50 15.6KHz 50.1Hz" 52.750 2560 2831 3079 3376 240 269 272 312  -hsync -vsync   
Modeline "2560x240_57 15.3KHz 57.0Hz" 52.870 2560 2800 3032 3448 240 247 256 269  -hsync -vsync   
Modeline "2560x240_58 15.7KHz 58.0Hz" 53.820 2560 2776 3016 3424 240 249 252 271  -hsync -vsync   
Modeline "2560x240_60 15.7KHz 59.9Hz" 53.890 2560 2752 3056 3432 240 244 247 262  -hsync -vsync   
Modeline "2560x256_54 15.9KHz 54.0Hz" 54.540 2560 2776 3040 3424 256 266 269 295  -hsync -vsync   
Modeline "2560x256_55 16.1KHz 55.0Hz" 54.010 2560 2728 2992 3352 256 267 279 293  -hsync -vsync   

Thanks alot for your help
« Last Edit: June 27, 2018, 06:28:20 am by filevans »

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 6049
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #5 on: June 27, 2018, 06:23:54 am »
There is such option but you really want to avoid that since the point of GM is to match the game's refresh. By using your already adjusted modes in Arcade OSD you're ignoring the refresh rate of games.

You should already have the crt_range in mame.ini populated with values if you had followed the tutorial and used the option in VMMaker to export settings to GroovyMAME. This option was added to avoid the "hassle".

Since you still have it as "auto", just replace it with this (in mame.ini):

 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

Now, open Arcade OSD, go to one of your already adjusted modes, and select "Copy modeline to clipboard". Preferrably use a mode with 240p lines.

Then open notepad, and press CTRL+V. You will see two lines: one with a crt_range and one with a modeline. The one you're interested in is the one with the crt_range line.

Now copy the three bold values and replace the ones in mame.ini with them.

Post the modified crt_range here if you want us to double check it.
Important note: posts reporting GM issues without a log will be IGNORED.
Steps to create a log:
 - From command line, run: groovymame.exe -v romname >romname.txt
 - Attach resulting romname.txt file to your post, instead or pasting it.

CRT Emudriver, VMMaker & Arcade OSD downloads, documentation and discussion:  Eiusdemmodi

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 6049
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #6 on: June 27, 2018, 06:30:40 am »
Alternatively, if you want a super lousy arcade setup, you can turn off -modeline_generation. That way GM will use your installed modelines as "read-only", that's what you're asking for... but the method we explained above is the way to go.

Important note: posts reporting GM issues without a log will be IGNORED.
Steps to create a log:
 - From command line, run: groovymame.exe -v romname >romname.txt
 - Attach resulting romname.txt file to your post, instead or pasting it.

CRT Emudriver, VMMaker & Arcade OSD downloads, documentation and discussion:  Eiusdemmodi

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #7 on: June 27, 2018, 06:41:14 am »
Since you still have it as "auto", just replace it with this (in mame.ini):

 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

Now, open Arcade OSD, go to one of your already adjusted modes, and select "Copy modeline to clipboard". Preferrably use a mode with 240p lines.

thanks for your patience and help
this isn't going to suffice as I will need a lot more than just one line, games like R-Type need 256 high and refresh 55Hz. a lot of games need different refreshes like 57,58,59Hz

It's not really a lousy setup as I have created modelines that are the correct refreshes for most games as you can see in my modelines above

Well if I do the vm_maker option, the problem I foresee is that once it's generated all the modelines, they won't all be centralised will they? so I will still have to edit them in Arcade OSD, which then means still creating the modelines, editing them in ArcadeOSD and then copying and pasting them into mame.ini which is quite a lot of work when I pretty much have the modelines already set up and centralised?

one last question, does VM Maker have an option to only create super resolutions? 2560x.... as I don't want it to create a massive list of magic resolution modelines in my registry that I cannot use and don't need

thank you very much

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 6049
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #8 on: June 27, 2018, 07:11:38 am »
Wait wait.

You don't have to run VMMaker again. You'd overwrite your already centered modes that way.

What I'm telling you is to use your centering information to create a crt_range that produces infinite already centered modes.

Usually, you don't need several crt_range lines for each refresh. If you see this line:

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

It already covers from 49.50 to 65.00 Hz, and from 192 to 288 lines in progressive and 448 to 576 in interlaced. Basically all you need.

Several crt_range lines are only needed in special cases.

With regards to VMMaker, you can also put your modelines in a text file, e.g. modelines.txt, and import them from VMMaker, from the video card's tab, that way you can back up your modes, etc.

With VMMaker you can do super resolutions only, super resolutions mixed with normal resolutions, etc., it all depends on the mode list you use as input.

Keep in mind that most standalone emulators can't work with super resolutions.

The good thing about having a personalized crt_range, is that you can use it later in VMMaker so all modes you create after that are already centered for your monitor.
Important note: posts reporting GM issues without a log will be IGNORED.
Steps to create a log:
 - From command line, run: groovymame.exe -v romname >romname.txt
 - Attach resulting romname.txt file to your post, instead or pasting it.

CRT Emudriver, VMMaker & Arcade OSD downloads, documentation and discussion:  Eiusdemmodi

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #9 on: June 27, 2018, 07:37:45 am »


I'm arcadeOSD now and I've gone through every screen and can't see anything that says "Copy modeline to clipboard"?
« Last Edit: June 27, 2018, 08:50:49 am by filevans »

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 6049
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #10 on: June 27, 2018, 09:26:12 am »
It's in the "Edit mode" submenu.
Important note: posts reporting GM issues without a log will be IGNORED.
Steps to create a log:
 - From command line, run: groovymame.exe -v romname >romname.txt
 - Attach resulting romname.txt file to your post, instead or pasting it.

CRT Emudriver, VMMaker & Arcade OSD downloads, documentation and discussion:  Eiusdemmodi

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #11 on: June 27, 2018, 09:32:29 am »
Its not there, I must have an older version arcadeOSD. I am using v1.4b which came bundled with CRT emudriver 1.2 for windows 7 64bit on the crt emudriver homepage. Only downloaded it about a week ago so maybe page not updated

I found 2.0 beta now so am downloading
« Last Edit: June 27, 2018, 09:40:05 am by filevans »

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 6049
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #12 on: June 27, 2018, 09:40:06 am »
I guess you missed this note at the top of the download thread:

Note: this version of CRT Emudriver is obsolete. This version is only useful for Windows XP users. Windows 7 and newer users should check CRT Emudriver 2.0 instead (don't mind the "beta" in its name, it's a fully working release). Even if you're still using Windows XP, it's recommended that along with CRT Emudriver 1.2b, you use the new updated CRT Tools instead of the old ones, as these are synchronized with GroovyMAME, and will make your life much easier.
Important note: posts reporting GM issues without a log will be IGNORED.
Steps to create a log:
 - From command line, run: groovymame.exe -v romname >romname.txt
 - Attach resulting romname.txt file to your post, instead or pasting it.

CRT Emudriver, VMMaker & Arcade OSD downloads, documentation and discussion:  Eiusdemmodi

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #13 on: June 27, 2018, 10:17:05 am »
I've done everything you said and got my range line and put the CRT_range0 into mame.ini and I still have the border on left hand side in GUI and games

Modeline a few lines above is set to auto. Is that right? And CRT_range is set to auto. I've put the line on CRT_range0. Also monitor is generic_15
« Last Edit: June 27, 2018, 10:37:24 am by filevans »

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 6049
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #14 on: June 27, 2018, 10:27:30 am »
Set "monitor custom" in mame.ini, that's the missing bit.
Important note: posts reporting GM issues without a log will be IGNORED.
Steps to create a log:
 - From command line, run: groovymame.exe -v romname >romname.txt
 - Attach resulting romname.txt file to your post, instead or pasting it.

CRT Emudriver, VMMaker & Arcade OSD downloads, documentation and discussion:  Eiusdemmodi

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #15 on: June 27, 2018, 10:32:02 am »
Thanks, now it's saying:
SwitchRes: could not find a video mode that meets your specs

I used your one:
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

And changed the 3 values in bold and used those values from my 2560x224 60hz range line
« Last Edit: June 27, 2018, 10:41:08 am by filevans »

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 6049
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #16 on: June 27, 2018, 11:31:37 am »
That's because there's some problem with your configuration, mame.ini, etc. Check my signature in order to create a log, post it here so I can see what's going on. Also post your mame.ini with your modified crt_range.
Important note: posts reporting GM issues without a log will be IGNORED.
Steps to create a log:
 - From command line, run: groovymame.exe -v romname >romname.txt
 - Attach resulting romname.txt file to your post, instead or pasting it.

CRT Emudriver, VMMaker & Arcade OSD downloads, documentation and discussion:  Eiusdemmodi

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #17 on: June 27, 2018, 12:21:17 pm »
there you go mate, thanks

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 6049
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #18 on: June 27, 2018, 12:32:02 pm »
It looks like you have an extra line. Try deleting the one with "crt_range   auto" and leave the crt_range0 one.

Code: [Select]
crt_range                 auto
crt_range0  15625-16200, 49.50-65.00, 2.850, 7.499, 6.149, 0.064, 0.192, 1.024, 0, 0, 192, 288, 448, 576
Important note: posts reporting GM issues without a log will be IGNORED.
Steps to create a log:
 - From command line, run: groovymame.exe -v romname >romname.txt
 - Attach resulting romname.txt file to your post, instead or pasting it.

CRT Emudriver, VMMaker & Arcade OSD downloads, documentation and discussion:  Eiusdemmodi

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #19 on: June 27, 2018, 12:40:42 pm »
I've just done that and still get the same error message when starting GMAME and also again when launching a game, weird as you would think the GUI would settle for any resolution it finds as refresh rate doesn't matter for that

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 6049
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #20 on: June 27, 2018, 12:44:37 pm »
There must be some silly error in mame.ini I'm missing. I suggest to start from scratch, delete mame.ini, create it again (groovymame.exe -cc), then only replace these two lines:

Code: [Select]
monitor custom
crt_range0  15625-16200, 49.50-65.00, 2.850, 7.499, 6.149, 0.064, 0.192, 1.024, 0, 0, 192, 288, 448, 576

Anyway, I'd need your new log so I can see if the previous issue has been fixed.
Important note: posts reporting GM issues without a log will be IGNORED.
Steps to create a log:
 - From command line, run: groovymame.exe -v romname >romname.txt
 - Attach resulting romname.txt file to your post, instead or pasting it.

CRT Emudriver, VMMaker & Arcade OSD downloads, documentation and discussion:  Eiusdemmodi

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #21 on: June 27, 2018, 01:06:29 pm »
thanks a lot! working now!

just a few questions, I want create a second video mode for m72 games like r-type which use funny refresh like 55hz as to get them to display vertically centralized properly I use high Khz around 16.1 but this does not suit the normal 60hz games, it makes the top show a black border and some CRT flickering green lines, so I don't want to mess with the default one. I want M72 games to use its own range line and I'll set that to 14.9 +/- so can i paste my M72 range line in underneath on crt_range1? and will it automatically use it? as I had my resolutions set nicely in ArcadeOSD.

other question is there a way so I don't have to keep changing region (say to USA and type to console) for every neo geo game? do you know if i can set that to a default? as keeps reverting back to europe/avs every time

and last question is, some neogeo games are 304x224 and mame wrongly assumes all neogeo games are 320x224, which annoys me and never has been fixed, so some games like andro dunos and alpha mission II you get borders either side, and I have to use slider controls to stretch horizontal to 1.052.... (320 / 304) can I make these games automatically fill up screen? silly as when you go to video options in these games it recognises that the true resolution of these games is 304x224 if you notice, but in game information it says 320x224!

thanks a lot for all your help
« Last Edit: June 27, 2018, 02:17:37 pm by filevans »

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 6049
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #22 on: June 27, 2018, 01:24:42 pm »
With regards to m72 games, if you *only* want to use that crt_range for those games, it's easier to create a specific .ini for that driver, I'm not sure if it'd be m72.ini, check the game info screen for that and create an .ini accordingly, but remind to use an empty txt file for that and *only* put the crt_range0 line in it.

Alternatively you can use a raw modeline and put it in the driver's ini, as taken from Arcade OSD, as you only need a fixed video mode for those games. GM has a "modeline" option, that supports just standard modelines as input.

With regards to neogeo bios, I have never run into that issue, sorry. And GM works exactly the same as baseline MAME on that regard.
« Last Edit: June 27, 2018, 01:26:17 pm by Calamity »
Important note: posts reporting GM issues without a log will be IGNORED.
Steps to create a log:
 - From command line, run: groovymame.exe -v romname >romname.txt
 - Attach resulting romname.txt file to your post, instead or pasting it.

CRT Emudriver, VMMaker & Arcade OSD downloads, documentation and discussion:  Eiusdemmodi

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #23 on: June 27, 2018, 01:32:49 pm »
just edited my above post

yes regarding 256 height 55hz resolution, if it is not set up right it can have the number of scanlines as 60hz/NTSC and then it is far too big for the screen, it has to be made to have PAL 50Hz scanline height so it fits on the screen properly, and then use a high Khz number to centralize properly
« Last Edit: June 27, 2018, 03:04:19 pm by filevans »

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 6049
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #24 on: June 27, 2018, 01:49:05 pm »
It wouldn't work to simply add the other range as crt_range1 because it will overlap crt_range0, you'd need to split the vertical resolution intervals (e.g. 192-255 and 256-288), but instead of that it's easier to leave the general range alone and put the other one as crt_range0 in a driver specific ini file.

I've no idea about the neogeo region thing sorry, hopefully some folk can help.

With regards to the neogeo resolution, I believe Haynor666 build fixes that, if this issue bothers you. 320x224 with borders is accurate to the pcb, however.
Important note: posts reporting GM issues without a log will be IGNORED.
Steps to create a log:
 - From command line, run: groovymame.exe -v romname >romname.txt
 - Attach resulting romname.txt file to your post, instead or pasting it.

CRT Emudriver, VMMaker & Arcade OSD downloads, documentation and discussion:  Eiusdemmodi

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #25 on: June 27, 2018, 02:05:39 pm »
i tried doing exactly what you said and made an m72.ini (matches driver name i checked) and i put the range line and into the ini yet it doesnt use that modeline when launching an m72 game, not working

try going into video options on say andro dunos and  there you can it says 304x224, see? so must be a reason for that, most neogeo games definitely use 320x224 no question about it. well yes it bothers me as i hate redundant borders, there was an old version of mame which fixed it, i think it was 113 Plus or FX, maybe some others too

Im going to try to split the vertical resolution intervals (e.g. 192-255 and 256-288) instead

sorry M72 55hz 256 height needs a high Khz around 16.1-16.2
« Last Edit: June 27, 2018, 02:18:30 pm by filevans »

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #26 on: June 27, 2018, 02:35:21 pm »
Thanks for your help - sorry just tested again and isn't working. Using the following lines it always switches to 2560x256 @ 55hz, can you help me fix it?

Code: [Select]
crt_range0                15325-16102.76, 55.50-65.00, 2.850, 7.499, 6.149, 0.064, 0.192, 1.024, 0, 0, 192, 254, 384, 508
crt_range1                16102.77-16122.77, 48.50-55.49, 3.111, 4.888, 6.665, 0.683, 0.745, 0.869, 0, 0, 256, 285, 512, 571
« Last Edit: June 27, 2018, 05:08:22 pm by filevans »

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 6049
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #27 on: June 27, 2018, 05:39:00 pm »
Post log, you can't imagine how important it is for me to figure out the problems.
Important note: posts reporting GM issues without a log will be IGNORED.
Steps to create a log:
 - From command line, run: groovymame.exe -v romname >romname.txt
 - Attach resulting romname.txt file to your post, instead or pasting it.

CRT Emudriver, VMMaker & Arcade OSD downloads, documentation and discussion:  Eiusdemmodi

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #28 on: June 27, 2018, 05:49:12 pm »
Also now it keeps  selecting 320x240  @ 60hz for games that are 320x224 which isn't right is it?

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #29 on: June 27, 2018, 06:28:03 pm »
Here you are mate. Now they are switching to 320x240 instead of game resolution of 320x224

buttersoft

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 656
  • Is running at 15kHz
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #30 on: June 27, 2018, 07:28:12 pm »
Not replying with a fix, just for info - Switchres adjusts the timing and refresh of a modeline when you launch a game in GM, it doesn't change the resolution. So if you don't have a 224p mode, it's going to pick 240p and, with the right stretching options in GM, leave 8 black lines at the top and 8 at the bottom. This is probably going to look exactly the same as using a real 224p mode though, because to keep the sync rate within range you would need to increase the vertical blanking interval, shrinking the picture slightly. This leads us to the corollary that vertical picture size can only be corrected using the geometry controls of your monitor, it cannot be done within GM. The exceptions to this are few and far between.

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #31 on: June 27, 2018, 08:21:41 pm »
Yes but i do have lots of derivatives of 224p. @ 59 & 60hz etc. I posted my mode lines above
 Thanks

buttersoft

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 656
  • Is running at 15kHz
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #32 on: June 27, 2018, 10:05:59 pm »
Ah, i my bad. In which case, and forgive me for not reading the thread, it might be related to the crt_range line. You need one that can use the timings you enter, with the lines you want, but that still falls inside the sync range you specify.

Horizontal scan rate = total lines in video frame x frames per second

Noting that the total lines here would be 224 plus the blanking lines. I'm not sure what gives in favour of what - as in, if the vertical timings are specified, and the scan rate of a 224p mode is lower than the range limit, does Switchres just pick 240p instead?


EDIT: I don't count txt attachments as being part of the thread proper, lol. But that modeline you've posted doesn't look wrong, so I'll wait for Calamity :)
« Last Edit: June 28, 2018, 02:32:42 am by buttersoft »

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #33 on: June 28, 2018, 04:53:46 am »
The solution is probably simple but I was on it for 2 days  and combined with how hot my bedroom was my brain had hit critical overload and I had smoke coming out of my ears

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #34 on: June 28, 2018, 05:22:09 am »
Still cant get it working properly

If I run Rtype through the GMAME GUI it looks like this:



but if I run it from command line using the -v and output to text switches then it runs perfectly ok:


« Last Edit: June 28, 2018, 11:36:17 am by filevans »

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 6049
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #35 on: June 28, 2018, 12:23:53 pm »
Get a log when launching from the GUI too, launch it like this and then run rtype from the menu:

groovymame.exe -v >rtype_from_gui.txt
Important note: posts reporting GM issues without a log will be IGNORED.
Steps to create a log:
 - From command line, run: groovymame.exe -v romname >romname.txt
 - Attach resulting romname.txt file to your post, instead or pasting it.

CRT Emudriver, VMMaker & Arcade OSD downloads, documentation and discussion:  Eiusdemmodi

krick

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1897
  • Gotta have blue hair.
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #36 on: June 28, 2018, 12:53:52 pm »
and last question is, some neogeo games are 304x224 and mame wrongly assumes all neogeo games are 320x224, which annoys me and never has been fixed, so some games like andro dunos and alpha mission II you get borders either side, and I have to use slider controls to stretch horizontal to 1.052.... (320 / 304) can I make these games automatically fill up screen? silly as when you go to video options in these games it recognises that the true resolution of these games is 304x224 if you notice, but in game information it says 320x224!

The "true" resolution of those games in NeoGeo *IS* 320x224.  That's what the actual board outputs.  Some games just don't use all of the width.  So in a real arcade cabinet with a real NeoGeo board, the operator would adjust the monitor width to cut off the blank area (or in some cases garbage) on the edge(s) of the screen.

In baseline MAME, if you hit the tab key and go into the menu on a NeoGeo game, there's two additional layouts in the video menu that allow you to crop or stretch if you choose.  I believe that you can put those layout choices in a game-specific ini file and enable them on a case-by-case basis.

"Screen 0 Standard (4:3)"
"Screen 0 Cropped (304x224)"
"Screen 0 Stretched (304x224)"

Here's the neogeo.lay file from the MAME source for reference...
https://github.com/mamedev/mame/blob/master/src/mame/layout/neogeo.lay

Another option is to use one custom GroovyMAME builds from haynor666 that modifies a bunch of the NeoGeo games...
http://forum.arcadecontrols.com/index.php/topic,154799.0.html
Hantarex Polo 15KHz
Sapphire Radeon HD 7750 2GB (GCN)
GroovyMAME 0.197.017h_d3d9ex
CRT Emudriver & CRT Tools 2.0 beta 13 (Crimson 16.2.1 for GCN cards)
Windows 7 Home Premium 64-bit
Intel Core i7-4790K @ 4.8GHz
ASUS Z87M-PLUS Motherboard

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #37 on: June 28, 2018, 05:03:28 pm »
there you go mate

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #38 on: June 28, 2018, 06:02:26 pm »
What settings do I need to have set to just use my mode lines in the mean time? As I tried to set generate mode lines off and it still was using the CRT range, do I also need to set that back to auto? How about monitor, still custom? And anything else? Just want to enjoy some games using my own modes until I can fix the issues properly
 Thanks a lot

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 6049
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #39 on: June 29, 2018, 06:36:10 am »
there you go mate

It's so odd because in both cases the same modeline is being applied. Try the D3D9ex build, you should be using this one anyway if you're on W7. Are you sure the correct times aren't being applied, anyway? I mean, could it be that the TV is not noticing the different signal for some reason when launching from the gui?

There's an unrelated, interesting bit in the log:

Code: [Select]
Attempting load of source\m72.ini
This means it's indeed trying to read m72.ini, but it probably needs to be placed inside .\ini\source\

With regards to -nomodeline_generation, bear in mind GM always needs a crt_range even in that situation, in order for the resolution picking algorithm to work. So if you have some custom crt_range settings, it will use those. That shouldn't affect the intended behaviour however, because the modelines will still be read-only and the algorithm should account for that, e.g. assuming the refresh rates to be fixed in order to pick the closest one.

Important note: posts reporting GM issues without a log will be IGNORED.
Steps to create a log:
 - From command line, run: groovymame.exe -v romname >romname.txt
 - Attach resulting romname.txt file to your post, instead or pasting it.

CRT Emudriver, VMMaker & Arcade OSD downloads, documentation and discussion:  Eiusdemmodi

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #40 on: June 29, 2018, 07:13:37 am »
Just tried dx9 GMAME and exactly the same problem: rtype screen runs fine from command line but distorted and screen in wrong position ran from GUI!??

also tried now and removed the m72 range line from crt_range1 and put it into m72.INI and I've put that into source folder, that works now and is selecting the right resolution, but with exactly the same problem as above!

something isn't working right from the GUI is it

also it has gone back to picking 240p again for 224p neo geo games, which is also annoying me
« Last Edit: June 29, 2018, 07:40:56 am by filevans »

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 6049
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #41 on: June 29, 2018, 01:44:10 pm »
Are you by any chance still running the old CRT Emudriver 1.2b? It sounds like your running into an old issue regarding short modelists (equal or below 17 modes). This was fixed years ago in 2.0. Not sure if it's that, but you may try adding some dummy modes to your mode list to discard this issue. And please update to 2.0 if that's the case, nobody is using your current setup (1.2b + W7) so results may be random.

Quote
also it has gone back to picking 240p again for 224p neo geo games, which is also annoying me

As it was mentioned above, GM will pick either 224 or 240 for 224p games, indistinctly, because in terms of video signal they are the *same* video mode. Don't try to fight this behaviour because it's in the very core of the modeline engine. If you want to force 224 explicitely you may need to use specific ini options (e.g. -resolution 2560x224) for that.
« Last Edit: June 29, 2018, 01:59:38 pm by Calamity »
Important note: posts reporting GM issues without a log will be IGNORED.
Steps to create a log:
 - From command line, run: groovymame.exe -v romname >romname.txt
 - Attach resulting romname.txt file to your post, instead or pasting it.

CRT Emudriver, VMMaker & Arcade OSD downloads, documentation and discussion:  Eiusdemmodi

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #42 on: June 29, 2018, 03:37:12 pm »
Yes I am using 1.2a because I could only see that on the home.page, I found 2.0 in a post so I will update

krick

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1897
  • Gotta have blue hair.
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #43 on: June 29, 2018, 04:31:01 pm »
Yes I am using 1.2a because I could only see that on the home.page, I found 2.0 in a post so I will update

http://geedorah.com/eiusdemmodi/forum/viewforum.php?id=7
Hantarex Polo 15KHz
Sapphire Radeon HD 7750 2GB (GCN)
GroovyMAME 0.197.017h_d3d9ex
CRT Emudriver & CRT Tools 2.0 beta 13 (Crimson 16.2.1 for GCN cards)
Windows 7 Home Premium 64-bit
Intel Core i7-4790K @ 4.8GHz
ASUS Z87M-PLUS Motherboard

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #44 on: June 29, 2018, 05:06:27 pm »
I've just installed CRT emudriver 2.0 beta 13 and it has made my CRT TV the secondary display when I have nothing else connected, the other drivers never did that. And now I can't open windows or menus as its all coming up on display 1. Before my VGA to SCART to CRT TV was display 1. Now it's display 2, is that normal? Or will I have to uninstall
and reinstall the driver using a monitor?

Edit: just reinstalled everything from fresh using a monitor and after installation did a restart and blank screen no signal, so connected to TV and still no signal. Seems like it is automatically assigning the VGA port as the secondary display, never had these problems on the other drivers,  not sure what to do now as cant get a picture unless I go to safe mode
« Last Edit: June 29, 2018, 05:28:51 pm by filevans »

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 6049
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #45 on: June 29, 2018, 05:26:31 pm »
It's normal. Follow the tutorial linked in the download thread or just try to make the tv the main display from display properties.
Important note: posts reporting GM issues without a log will be IGNORED.
Steps to create a log:
 - From command line, run: groovymame.exe -v romname >romname.txt
 - Attach resulting romname.txt file to your post, instead or pasting it.

CRT Emudriver, VMMaker & Arcade OSD downloads, documentation and discussion:  Eiusdemmodi

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #46 on: June 29, 2018, 05:31:28 pm »
None of the other drivers did this. I notice it also said a dll file was missing during installation. Something from visual basic? Related to the debugger or something

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #47 on: June 29, 2018, 05:36:08 pm »
 OK found the tutorial now. Far complicated, was that really neccesary? Is there any older version of the 2.0 driver that doesn't require connecting through 2 displays at the same time? As I don't have all these adapters and leads which means I'll have my PC non working until next week until I get dvi adapter
« Last Edit: June 29, 2018, 05:59:21 pm by filevans »

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #48 on: June 29, 2018, 05:47:28 pm »
I made sure it was the main display after installing the driver and before I restarted there was only 1 display showing

Why after installing the new driver am I getting no signal through my anything I connect to the VGA port? This didn't happen before, are you telling me I have to go.through the hassle of connecting something to the dvi or HDMI ports jus to set things up to use the VGA port? I don't know why the process has been made complicated. I don't have a dvi lead nor HDMI one
« Last Edit: June 29, 2018, 05:49:09 pm by filevans »

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 6049
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #49 on: June 29, 2018, 06:10:27 pm »
Because previous versions caused endless problems with display detection of crts, so I had to shortcut the detection routine in the driver. Now the driver thinks there are always screens connected to the analogue outputs. This is normal, it only makes the installation process a bit cumbersome, but avoids lots of other problems, that's why I wrote a specific tutorial for it that all folks have followed succesfully.
Important note: posts reporting GM issues without a log will be IGNORED.
Steps to create a log:
 - From command line, run: groovymame.exe -v romname >romname.txt
 - Attach resulting romname.txt file to your post, instead or pasting it.

CRT Emudriver, VMMaker & Arcade OSD downloads, documentation and discussion:  Eiusdemmodi

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 6049
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #50 on: June 29, 2018, 06:13:59 pm »
BTW there are ways to do that with just one monitor, I do that all the time, but a fool proof method was required and it involves two screens.
Important note: posts reporting GM issues without a log will be IGNORED.
Steps to create a log:
 - From command line, run: groovymame.exe -v romname >romname.txt
 - Attach resulting romname.txt file to your post, instead or pasting it.

CRT Emudriver, VMMaker & Arcade OSD downloads, documentation and discussion:  Eiusdemmodi

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #51 on: June 29, 2018, 06:44:05 pm »
Give me the 1 monitor method, I'm no fool

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 6049
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #52 on: June 30, 2018, 04:48:04 am »
You need at least a DVI-VGA adapter.
Important note: posts reporting GM issues without a log will be IGNORED.
Steps to create a log:
 - From command line, run: groovymame.exe -v romname >romname.txt
 - Attach resulting romname.txt file to your post, instead or pasting it.

CRT Emudriver, VMMaker & Arcade OSD downloads, documentation and discussion:  Eiusdemmodi

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #53 on: June 30, 2018, 05:15:40 am »
Is there any older version of 2.0 that can be installed though VGA port like the other versions? So i can least have that in the mean time?

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #54 on: June 30, 2018, 05:38:06 am »
You could have still made it so it thinks there's 2 displays connected and leave VGA port as the primary display... So then dvi adapter not obligatory. Annoying how as VGA is secondary automatically, meaniningyou can't get resolution window up on the screen to change monitor order and layout
« Last Edit: June 30, 2018, 06:20:30 am by filevans »

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 6049
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #55 on: June 30, 2018, 05:52:10 am »
Is there any older version of 2.0 that can be installed though VGA port like the other versions? So i can least have that in the mean time?

No, you have to go back to 1.2b, sorry. The 2.0 version contains the detection patches from the beginning. The problem is 1.2b for W7 is unsupported now, there's no guarantee it works properly with GM. It was the first attempt to move everything to 7 and it had *lots* of issues.

The moral of all this is that W7 support for HD 4xxx is very poor (I mean official support, not Emudriver), those cards don't even support DX11. It's much easier to get things running with HD 5xxx+ cards, and once you do you wonder what the hell you were doing before.
Important note: posts reporting GM issues without a log will be IGNORED.
Steps to create a log:
 - From command line, run: groovymame.exe -v romname >romname.txt
 - Attach resulting romname.txt file to your post, instead or pasting it.

CRT Emudriver, VMMaker & Arcade OSD downloads, documentation and discussion:  Eiusdemmodi

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 6049
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #56 on: June 30, 2018, 05:56:44 am »
You could have still made it so it thinks there's 2 displays connected and leave VGA port as the primary display... So then dvi adapter not required

That's not easy to do. Each gpu has some internal order for its output connectors, I believe it comes from the bios, not sure. Starting from HD series, the DVI became first (default) output. This means that without more information, the OS will send the output automatically thought that connector. I've never had a problem with this because with any card I've bought there was a DVI-VGA adapter inside the box.

PD: Besides, usually it's better to use that DVI output anyway because it comes directly from the pcb rather than from the ribbon cable, some users have reported worse quality video due to the ribbon cable (VGA).
« Last Edit: June 30, 2018, 05:59:46 am by Calamity »
Important note: posts reporting GM issues without a log will be IGNORED.
Steps to create a log:
 - From command line, run: groovymame.exe -v romname >romname.txt
 - Attach resulting romname.txt file to your post, instead or pasting it.

CRT Emudriver, VMMaker & Arcade OSD downloads, documentation and discussion:  Eiusdemmodi

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #57 on: June 30, 2018, 06:49:27 am »
I went slightly briskly through the guide and ended up with my CRT TV as display 1 through dvi, rather than 2 like says in the guide. Everything is working though

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #58 on: June 30, 2018, 07:37:10 am »
Unfortunately still exactly the same problem with running rtype though, got to be a gui issue as game runs fine from command line

I didn't see anything in the guide how to add a range line to your mame.ini, is that a separate guide? I followed the vm maker instructions and generated all the super resolutions. But am still using the range line I added before. Could you look at the range lines I gave you and see if you could tweak them so rtype works OK? Well I'll try adding the 240p and 256p range lines that  VM maker generated to see if that will do it

I must disagree when you both say 240p and 224p are the same. As to fit more or less on the screen you tweak the kHz. If you set 240p at around 16-16.2khz you get some more scan lines on the screen than if it was 15.5 say, handy for games like puzzle bobble you can see more. And 224p I would set at 14.9-15.4 which makes that resolution vertically bigger. This way if you adjust the vertical in your TV service mode you can get 224 and 240 to display better using this method. If they both use 240 then you can't do this

Second reason it is just wrong to use 240p for 224p and is inaccurate. Having that extra spare over scan annoys me. Plus you can't see the top and bottom edges then to centralise it and would have to guess or do by trial and error when aligning it in arcadeOSD

I think this should be put right.

« Last Edit: June 30, 2018, 08:02:40 am by filevans »

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 6049
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #59 on: June 30, 2018, 08:00:46 am »
There's an option in the MAME tab in VMMaker "Export settings to GM". This exports your current monitor definition in VMMaker to GM. You need to edit the monitor definition in VMMaker, make a custom one by editing monitor.ini, and create a new monitor definition using the crt_ranges you now have in mame.ini . It's not really necessary to do that, it's just convenient to have both VMMaker and GM using the same definitions.

The only think I can think of now is if you're not running GM with admin rights when you launch from GUI. I mean, results should be identical running from command line or from GUI.

And... why do you run things from GM's gui anyway? Isn't more practical to use a frontend?
Important note: posts reporting GM issues without a log will be IGNORED.
Steps to create a log:
 - From command line, run: groovymame.exe -v romname >romname.txt
 - Attach resulting romname.txt file to your post, instead or pasting it.

CRT Emudriver, VMMaker & Arcade OSD downloads, documentation and discussion:  Eiusdemmodi

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #60 on: June 30, 2018, 08:11:50 am »
Well I've only just got groovyMAME so when I first get an emulator I just use the GUI as it's easier to play around with and test everything and make sure everything is working right. Then after that's done I would set it up on command line through attract mode front end

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #61 on: June 30, 2018, 08:26:44 am »
Quote
If you want to force 224 explicitely you may need to use specific ini options (e.g. -resolution 2560x224) for that.

Will that only force 224p games to run in 224p and 240p games will still choose 240p?

I want 224 games to use 224p and 240 to use 240p, can you please explain the best way to do it? Even if its using my own mode lines if necessary and not generated ones
« Last Edit: June 30, 2018, 08:29:29 am by filevans »

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #62 on: June 30, 2018, 08:42:16 am »
You were right, that did it: run as administrator I ticked it in compatibility and now rtype runs perfectly in GUI! I'm getting everything resolved gradually! Thanks for help and patience

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #63 on: July 01, 2018, 07:22:43 am »
Please can I run arcadeOSD from command line? As RetroArch won't switch back to desktop resolution when exiting, and stays in 2560x224 so I would like to use a command line upon exit, or if not maybe there is another resolution switcher that uses command line? Thank you very much

filevans

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 74
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #64 on: July 01, 2018, 02:29:28 pm »
do you please know how to force a resolution in GMAME mess, by command line? you said  -resolution 2560x224 and how about refresh rate?
« Last Edit: July 01, 2018, 03:31:02 pm by filevans »

krick

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1897
  • Gotta have blue hair.
Re: Groovymame 0.197 64bit screen won't centralise
« Reply #65 on: July 01, 2018, 07:34:46 pm »
Please can I run arcadeOSD from command line? As RetroArch won't switch back to desktop resolution when exiting, and stays in 2560x224 so I would like to use a command line upon exit, or if not maybe there is another resolution switcher that uses command line? Thank you very much

I think you can use NirCmd to switch the resolution from the command line...

http://www.nirsoft.net/utils/nircmd.html

http://nircmd.nirsoft.net/setdisplay.html
Quote
NirCmd Command Reference - setdisplay

setdisplay {monitor:index/name} [width] [height] [color bits] {refresh rate} {-updatereg} {-allusers}
Changes your display settings. The [width] and [height] parameters represents the number of pixels on your screen. The [color bits] parameter represents the number of colors shown on your screen (8 - 256 color, 16 - 16bit color, 24 - 24bit color, and so on). {refresh rate} is an optional parameter that specifies the monitor refresh rate. If you specify the {-updatereg} parameter, the new settings will be saved in the Registry. If you specify both {-updatereg} and {-allusers} parameters, the new settings will be saved in the Registry for all users.
If you have multiple monitors, you can use the optional monitor parameter, which specifies for which monitor you want to change the display settings. You can specify the monitor by index (0 for the first monitor, 1 for the second one, and so on) or by specifying a string in the system monitor name. The monitor name can be found in the Device manager of Windows: Right click on the monitor item, and then choose 'Properties'. The string displayed in the 'location' field is the monitor name.
Example:
setdisplay 800 600 24 -updatereg
setdisplay 1024 768 24 90
setdisplay 1024 768 8
setdisplay monitor:1 1024 768 24 90
setdisplay monitor:name1 1024 768 24 90

If you search these forums for "nircmd" you'll find other posts about how to use it.
Hantarex Polo 15KHz
Sapphire Radeon HD 7750 2GB (GCN)
GroovyMAME 0.197.017h_d3d9ex
CRT Emudriver & CRT Tools 2.0 beta 13 (Crimson 16.2.1 for GCN cards)
Windows 7 Home Premium 64-bit
Intel Core i7-4790K @ 4.8GHz
ASUS Z87M-PLUS Motherboard

  
 

Sitemap 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31