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
Lightguns Arcade1Up Try the site in https mode Site News

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

  

Author Topic: Clarification on using GroovyMAME on a LCD  (Read 36950 times)

0 Members and 1 Guest are viewing this topic.

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 7414
  • Last login:April 10, 2024, 02:02:31 pm
  • Quote me with care
Re: Clarification on using GroovyMAME on a LCD
« Reply #120 on: February 04, 2019, 04:15:46 pm »
You mean I have to disable freesync for it to work correctly? Can't do that via the monitor, only via the radeon graphics panel that I don't seem to have on crt emudriver ^^".
Guess I have to find out how to install the panel standalone or do it via registry or an external tool.

Probably your best option is to install the whole official ADM package version 18.5.1, then once installed overwritte the display driver with the Setup from CRT Emudriver.

I'll see if I can rip off the Radeon Settings installer, and avoid having to provide the huge full package.
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 of pasting it.

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

retrogamer123

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 26
  • Last login:April 11, 2021, 04:06:23 am
  • I want to build my own arcade controls!
Re: Clarification on using GroovyMAME on a LCD
« Reply #121 on: February 05, 2019, 04:42:16 am »
Thanks for helping me with the configuration, but sadly it is still not working
I installed the official 18.5.1 package and replaced the driver.
Under monitor settings I disabled freesync and I also made a custom profile for mame and disabled freesync there. The games still have speedup for me.
Maybe the control panel settings don't work? I'm on windows 7 btw.
Refreshrate switching itself seems perfectly fine, when looking at the log and machine information ingame.
Even when bfi is not enabled. The game has no framelimit at all and just goes max speed for me.
Is there anything else I can try to debug this?
Code: [Select]
Attempting load of mame.ini
Parsing mame.ini
Attempting load of mame.ini
Parsing mame.ini
Attempting load of vertical.ini
Attempting load of arcade.ini
Attempting load of raster.ini
Attempting load of source\cave.ini
Attempting load of esprade.ini
Attempting load of mame.ini
Parsing mame.ini
Attempting load of mame.ini
Parsing mame.ini
Attempting load of vertical.ini
Attempting load of arcade.ini
Attempting load of raster.ini
Attempting load of source\cave.ini
Attempting load of esprade.ini
SwitchRes: v0.017n, Monitor: custom, Orientation: horizontal, Modeline generation: enabled
SwitchRes: Monitor range 54900.00-158112.00,50.00-144.00,0.074,0.098,0.246,0.019,0.032,0.063,1,1,1080,1080,0,0
SwitchRes: \\.\DISPLAY15: Radeon RX 570 Series (PCI\VEN_1002&DEV_67DF&SUBSYS_E3431DA2&REV_EF)
SwitchRes: Device key: System\CurrentControlSet\Control\Video\{8F9A0BDB-2668-4078-A82C-085B0BBBB91C}\0000
ATI/AMD ADL init
AMD driver version 18.5
ADL functions retrieved successfully.
Switchres: Searching for custom video modes...
Switchres: [  1]  640x 480 @ 59 : system mode
Switchres: [  2]  640x 480 @ 60 : ATI ADL timing "640x480_60 31.462000KHz 59.927620Hz" 25.170000 640 656 752 800 480 490 492 525   -hsync -vsync
Switchres: [  3]  640x 480 @ 67 : ATI ADL timing "640x480_67 33.437000KHz 66.607567Hz" 26.750000 640 656 720 800 480 483 487 502   -hsync +vsync
Switchres: [  4]  640x 480 @100 : system mode
Switchres: [  5]  640x 480 @120 : system mode
Switchres: [  6]  640x 480 @144 : system mode
Switchres: [  7]  720x 400 @ 59 : system mode
Switchres: [  8]  720x 400 @ 60 : system mode
Switchres: [  9]  720x 400 @ 70 : ATI ADL timing "720x400_70 29.296000KHz 69.752380Hz" 26.250000 720 744 808 896 400 403 413 420   -hsync +vsync
Switchres: [ 10]  720x 400 @100 : system mode
Switchres: [ 11]  720x 400 @120 : system mode
Switchres: [ 12]  720x 400 @144 : system mode
Switchres: [ 13]  720x 480 @ 59 : system mode
Switchres: [ 14]  720x 480 @ 60 : ATI ADL timing "720x480_60 31.468000KHz 59.939049Hz" 27.000000 720 736 798 858 480 489 495 525   -hsync -vsync
Switchres: [ 15]  720x 480 @100 : system mode
Switchres: [ 16]  720x 480 @120 : system mode
Switchres: [ 17]  720x 480 @144 : system mode
Switchres: [ 18]  720x 576 @ 50 : ATI ADL timing "720x576_50 31.250000KHz 50.000000Hz" 27.000000 720 732 796 864 576 581 586 625   -hsync -vsync
Switchres: [ 19]  720x 576 @ 59 : system mode
Switchres: [ 20]  720x 576 @ 60 : system mode
Switchres: [ 21]  720x 576 @100 : system mode
Switchres: [ 22]  720x 576 @120 : system mode
Switchres: [ 23]  720x 576 @144 : system mode
Switchres: [ 24]  800x 600 @ 56 : ATI ADL timing "800x600_56 35.156000KHz 56.249599Hz" 36.000000 800 824 896 1024 600 601 603 625   +hsync +vsync
Switchres: [ 25]  800x 600 @ 59 : system mode
Switchres: [ 26]  800x 600 @ 60 : ATI ADL timing "800x600_60 37.878000KHz 60.315285Hz" 40.000000 800 840 968 1056 600 601 605 628   +hsync +vsync
Switchres: [ 27]  800x 600 @100 : system mode
Switchres: [ 28]  800x 600 @120 : system mode
Switchres: [ 29]  800x 600 @144 : system mode
Switchres: [ 30] 1024x 768 @ 59 : system mode
Switchres: [ 31] 1024x 768 @ 60 : ATI ADL timing "1024x768_60 48.363000KHz 60.003723Hz" 65.000000 1024 1048 1184 1344 768 771 777 806   -hsync -vsync
Switchres: [ 32] 1024x 768 @ 70 : ATI ADL timing "1024x768_70 56.475000KHz 70.068237Hz" 75.000000 1024 1048 1184 1328 768 771 777 806   -hsync -vsync
Switchres: [ 33] 1024x 768 @100 : system mode
Switchres: [ 34] 1024x 768 @120 : system mode
Switchres: [ 35] 1024x 768 @144 : system mode
Switchres: [ 36] 1152x 864 @ 59 : system mode
Switchres: [ 37] 1152x 864 @ 60 : system mode
Switchres: [ 38] 1152x 864 @ 75 : ATI ADL timing "1152x864_75 67.500000KHz 75.000000Hz" 108.000000 1152 1216 1344 1600 864 865 868 900   +hsync +vsync
Switchres: [ 39] 1152x 864 @100 : system mode
Switchres: [ 40] 1152x 864 @120 : system mode
Switchres: [ 41] 1152x 864 @144 : system mode
Switchres: [ 42] 1280x 720 @ 50 : ATI ADL timing "1280x720_50 37.500000KHz 50.000000Hz" 74.250000 1280 1720 1760 1980 720 725 730 750   +hsync +vsync
Switchres: [ 43] 1280x 720 @ 59 : system mode
Switchres: [ 44] 1280x 720 @ 60 : ATI ADL timing "1280x720_60 44.951000KHz 59.934666Hz" 74.170000 1280 1390 1430 1650 720 725 730 750   +hsync +vsync
Switchres: [ 45] 1280x 720 @100 : system mode
Switchres: [ 46] 1280x 720 @120 : system mode
Switchres: [ 47] 1280x 720 @144 : system mode
Switchres: [ 48] 1280x 800 @ 59 : system mode
Switchres: [ 49] 1280x 800 @ 60 : ATI ADL timing "1280x800_60 49.702000KHz 59.809868Hz" 83.500000 1280 1352 1480 1680 800 803 809 831   -hsync +vsync
Switchres: [ 50] 1280x 800 @100 : system mode
Switchres: [ 51] 1280x 800 @120 : system mode
Switchres: [ 52] 1280x 800 @144 : system mode
Switchres: [ 53] 1280x 960 @ 59 : system mode
Switchres: [ 54] 1280x 960 @ 60 : ATI ADL timing "1280x960_60 60.000000KHz 60.000000Hz" 108.000000 1280 1376 1488 1800 960 961 964 1000   +hsync +vsync
Switchres: [ 55] 1280x 960 @100 : system mode
Switchres: [ 56] 1280x 960 @120 : system mode
Switchres: [ 57] 1280x 960 @144 : system mode
Switchres: [ 58] 1280x1024 @ 59 : system mode
Switchres: [ 59] 1280x1024 @ 60 : ATI ADL timing "1280x1024_60 63.981000KHz 60.019699Hz" 108.000000 1280 1328 1440 1688 1024 1025 1028 1066   +hsync +vsync
Switchres: [ 60] 1280x1024 @100 : system mode
Switchres: [ 61] 1280x1024 @120 : system mode
Switchres: [ 62] 1280x1024 @144 : system mode
Switchres: [ 63] 1440x 900 @ 59 : system mode
Switchres: [ 64] 1440x 900 @ 60 : ATI ADL timing "1440x900_60 55.934000KHz 59.886509Hz" 106.500000 1440 1520 1672 1904 900 903 909 934   -hsync +vsync
Switchres: [ 65] 1440x 900 @100 : system mode
Switchres: [ 66] 1440x 900 @120 : system mode
Switchres: [ 67] 1440x 900 @144 : system mode
Switchres: [ 68] 1440x1080 @ 59 : system mode
Switchres: [ 69] 1440x1080 @ 60 : system mode
Switchres: [ 70] 1440x1080 @100 : system mode
Switchres: [ 71] 1440x1080 @120 : ATI ADL timing "1440x1080_120 131.400000KHz 120.000000Hz" 200.780000 1440 1456 1480 1528 1080 1083 1087 1095   +hsync +vsync
Switchres: [ 72] 1440x1080 @144 : system mode
Switchres: [ 73] 1600x 900 @ 59 : system mode
Switchres: [ 74] 1600x 900 @ 60 : system mode
Switchres: [ 75] 1600x 900 @100 : system mode
Switchres: [ 76] 1600x 900 @120 : system mode
Switchres: [ 77] 1600x 900 @144 : system mode
Switchres: [ 78] 1680x1050 @ 59 : system mode
Switchres: [ 79] 1680x1050 @ 60 : ATI ADL timing "1680x1050_60 65.290000KHz 59.954086Hz" 146.250000 1680 1784 1960 2240 1050 1053 1059 1089   -hsync +vsync
Switchres: [ 80] 1680x1050 @100 : system mode
Switchres: [ 81] 1680x1050 @120 : system mode
Switchres: [ 82] 1680x1050 @144 : system mode
Switchres: [ 83] 1920x1080 @ 25 : ATI ADL timing "1920x1080_25 28.125000KHz 50.000000Hz" 74.250000 1920 2448 2492 2640 1080 1085 1095 1125 interlace  +hsync +vsync
Switchres: [ 84] 1920x1080 @ 29 : system mode
Switchres: [ 85] 1920x1080 @ 30 : ATI ADL timing "1920x1080_30 33.713000KHz 59.934223Hz" 74.170000 1920 2008 2052 2200 1080 1085 1095 1125 interlace  +hsync +vsync
Switchres: [ 86] 1920x1080 @ 50 : system mode
Switchres: [ 87] 1920x1080 @ 58 : ATI ADL timing "1920x1080_58 125.920000KHz 115.100548Hz" 255.870000 1920 1944 1968 2032 1080 1082 1086 1094   +hsync +vsync
Switchres: [ 88] 1920x1080 @ 59 : system mode
Switchres: [ 89] 1920x1080 @ 60 : system mode
Switchres: [ 90] 1920x1080 @100 : ATI ADL timing "1920x1080_100 113.221000KHz 99.930275Hz" 235.500000 1920 1968 2000 2080 1080 1083 1088 1133   +hsync -vsync
Switchres: [ 91] 1920x1080 @120 : ATI ADL timing "1920x1080_120 137.259000KHz 119.981644Hz" 285.500000 1920 1968 2000 2080 1080 1083 1088 1144   +hsync -vsync
Switchres: [ 92] 1920x1080 @144* : ATI ADL timing "1920x1080_144 158.112000KHz 144.000000Hz" 325.080000 1920 1944 1976 2056 1080 1083 1088 1098   +hsync +vsync
SwitchRes: Found 24 custom of 92 active video modes
SwitchRes: -resolution was forced as 1920x1080@58

SwitchRes: Entering switchres_modeline_setup
SwitchRes: v0.017n:[esprade] Calculating best video mode for 240x320@57.550644 orientation: rotated

SwitchRes: [ 640]x[ 480]_[59=59.000000Hz] - locked

SwitchRes: [ 640]x[ 480]_(60=59.927620Hz) - locked

SwitchRes: [ 640]x[ 480]_(67=66.607567Hz) - locked

SwitchRes: [ 640]x[ 480]_[100=100.000000Hz] - locked

SwitchRes: [ 640]x[ 480]_[120=120.000000Hz] - locked

SwitchRes: [ 640]x[ 480]_[144=144.000000Hz] - locked

SwitchRes: [ 720]x[ 400]_[59=59.000000Hz] - locked

SwitchRes: [ 720]x[ 400]_[60=60.000000Hz] - locked

SwitchRes: [ 720]x[ 400]_(70=69.752380Hz) - locked

SwitchRes: [ 720]x[ 400]_[100=100.000000Hz] - locked

SwitchRes: [ 720]x[ 400]_[120=120.000000Hz] - locked

SwitchRes: [ 720]x[ 400]_[144=144.000000Hz] - locked

SwitchRes: [ 720]x[ 480]_[59=59.000000Hz] - locked

SwitchRes: [ 720]x[ 480]_(60=59.939049Hz) - locked

SwitchRes: [ 720]x[ 480]_[100=100.000000Hz] - locked

SwitchRes: [ 720]x[ 480]_[120=120.000000Hz] - locked

SwitchRes: [ 720]x[ 480]_[144=144.000000Hz] - locked

SwitchRes: [ 720]x[ 576]_(50=50.000000Hz) - locked

SwitchRes: [ 720]x[ 576]_[59=59.000000Hz] - locked

SwitchRes: [ 720]x[ 576]_[60=60.000000Hz] - locked

SwitchRes: [ 720]x[ 576]_[100=100.000000Hz] - locked

SwitchRes: [ 720]x[ 576]_[120=120.000000Hz] - locked

SwitchRes: [ 720]x[ 576]_[144=144.000000Hz] - locked

SwitchRes: [ 800]x[ 600]_(56=56.249599Hz) - locked

SwitchRes: [ 800]x[ 600]_[59=59.000000Hz] - locked

SwitchRes: [ 800]x[ 600]_(60=60.315285Hz) - locked

SwitchRes: [ 800]x[ 600]_[100=100.000000Hz] - locked

SwitchRes: [ 800]x[ 600]_[120=120.000000Hz] - locked

SwitchRes: [ 800]x[ 600]_[144=144.000000Hz] - locked

SwitchRes: [1024]x[ 768]_[59=59.000000Hz] - locked

SwitchRes: [1024]x[ 768]_(60=60.003723Hz) - locked

SwitchRes: [1024]x[ 768]_(70=70.068237Hz) - locked

SwitchRes: [1024]x[ 768]_[100=100.000000Hz] - locked

SwitchRes: [1024]x[ 768]_[120=120.000000Hz] - locked

SwitchRes: [1024]x[ 768]_[144=144.000000Hz] - locked

SwitchRes: [1152]x[ 864]_[59=59.000000Hz] - locked

SwitchRes: [1152]x[ 864]_[60=60.000000Hz] - locked

SwitchRes: [1152]x[ 864]_(75=75.000000Hz) - locked

SwitchRes: [1152]x[ 864]_[100=100.000000Hz] - locked

SwitchRes: [1152]x[ 864]_[120=120.000000Hz] - locked

SwitchRes: [1152]x[ 864]_[144=144.000000Hz] - locked

SwitchRes: [1280]x[ 720]_(50=50.000000Hz) - locked

SwitchRes: [1280]x[ 720]_[59=59.000000Hz] - locked

SwitchRes: [1280]x[ 720]_(60=59.934666Hz) - locked

SwitchRes: [1280]x[ 720]_[100=100.000000Hz] - locked

SwitchRes: [1280]x[ 720]_[120=120.000000Hz] - locked

SwitchRes: [1280]x[ 720]_[144=144.000000Hz] - locked

SwitchRes: [1280]x[ 800]_[59=59.000000Hz] - locked

SwitchRes: [1280]x[ 800]_(60=59.809868Hz) - locked

SwitchRes: [1280]x[ 800]_[100=100.000000Hz] - locked

SwitchRes: [1280]x[ 800]_[120=120.000000Hz] - locked

SwitchRes: [1280]x[ 800]_[144=144.000000Hz] - locked

SwitchRes: [1280]x[ 960]_[59=59.000000Hz] - locked

SwitchRes: [1280]x[ 960]_(60=60.000000Hz) - locked

SwitchRes: [1280]x[ 960]_[100=100.000000Hz] - locked

SwitchRes: [1280]x[ 960]_[120=120.000000Hz] - locked

SwitchRes: [1280]x[ 960]_[144=144.000000Hz] - locked

SwitchRes: [1280]x[1024]_[59=59.000000Hz] - locked

SwitchRes: [1280]x[1024]_(60=60.019699Hz) - locked

SwitchRes: [1280]x[1024]_[100=100.000000Hz] - locked

SwitchRes: [1280]x[1024]_[120=120.000000Hz] - locked

SwitchRes: [1280]x[1024]_[144=144.000000Hz] - locked

SwitchRes: [1440]x[ 900]_[59=59.000000Hz] - locked

SwitchRes: [1440]x[ 900]_(60=59.886509Hz) - locked

SwitchRes: [1440]x[ 900]_[100=100.000000Hz] - locked

SwitchRes: [1440]x[ 900]_[120=120.000000Hz] - locked

SwitchRes: [1440]x[ 900]_[144=144.000000Hz] - locked

SwitchRes: [1440]x[1080]_[59=59.000000Hz] - locked

SwitchRes: [1440]x[1080]_[60=60.000000Hz] - locked

SwitchRes: [1440]x[1080]_[100=100.000000Hz] - locked

SwitchRes: [1440]x[1080]_(120=120.000000Hz) - locked

SwitchRes: [1440]x[1080]_[144=144.000000Hz] - locked

SwitchRes: [1600]x[ 900]_[59=59.000000Hz] - locked

SwitchRes: [1600]x[ 900]_[60=60.000000Hz] - locked

SwitchRes: [1600]x[ 900]_[100=100.000000Hz] - locked

SwitchRes: [1600]x[ 900]_[120=120.000000Hz] - locked

SwitchRes: [1600]x[ 900]_[144=144.000000Hz] - locked

SwitchRes: [1680]x[1050]_[59=59.000000Hz] - locked

SwitchRes: [1680]x[1050]_(60=59.954086Hz) - locked

SwitchRes: [1680]x[1050]_[100=100.000000Hz] - locked

SwitchRes: [1680]x[1050]_[120=120.000000Hz] - locked

SwitchRes: [1680]x[1050]_[144=144.000000Hz] - locked

SwitchRes: [1920]x[1080]_(25=50.000000Hz) - locked

SwitchRes: [1920]x[1080]_[29=29.000000Hz] - locked

SwitchRes: [1920]x[1080]_(30=59.934223Hz) - locked

SwitchRes: [1920]x[1080]_[50=50.000000Hz] - locked

SwitchRes: [1920]x[1080]_(58=115.100548Hz)
   rng(0): 1920 x1080_57.550644p 62.557550 [fract] scale(5, 3, 1) diff(11.11, 22.17, 0.0000) ratio(8.000, 3.375)

SwitchRes: [1920]x[1080]_[59=59.000000Hz] - locked

SwitchRes: [1920]x[1080]_[60=60.000000Hz] - locked

SwitchRes: [1920]x[1080]_(100=99.930275Hz) - locked

SwitchRes: [1920]x[1080]_(120=119.981644Hz) - locked

SwitchRes: [1920]x[1080]_[144=144.000000Hz] - locked

SwitchRes: [esprade] (1) vertical (240x320@57.550644)->(1920x1080@57.550644)
   rng(0): 1920 x1080_57.550644p 62.557550 [fract] scale(5, 3, 1) diff(11.11, 22.17, 0.0000) ratio(8.000, 3.375)
SwitchRes: Modeline "1920x1080_58 62.557550KHz 57.550644Hz" 124.114176 1920 1936 1952 1984 1080 1081 1083 1087   +hsync +vsync
Switchres: saving    ATI ADL timing "1920x1080_58 125.920000KHz 115.100548Hz" 255.870000 1920 1944 1968 2032 1080 1082 1086 1094   +hsync +vsync
Switchres: updating  ATI ADL timing "1920x1080_58 62.557550KHz 57.550644Hz" 124.114176 1920 1936 1952 1984 1080 1081 1083 1087   +hsync +vsync
SwitchRes: Setting option -rotate
SwitchRes: Setting option -noror
SwitchRes: Setting option -noautoror
SwitchRes: Setting option -norol
SwitchRes: Setting option -noautorol
SwitchRes: Setting option -keepaspect
SwitchRes: Setting option -unevenstretch
SwitchRes: Setting option -nounevenstretchx
SwitchRes: Setting option -noblack_frame_insertion
SwitchRes: Setting option -syncrefresh
SwitchRes: Setting option -notriplebuffer
SwitchRes: Setting option -waitvsync
SwitchRes: Setting option -nofilter
Video: Monitor 65537 = "\\.\DISPLAY15" (primary)
Direct3D: Using Direct3D 9Ex
Physical width 1920, height 1080
Direct3D: Initialize
Direct3D: Configuring adapter #0 = Radeon RX 570 Series
Direct3D: Adapter has Vendor ID: 1002 and Device ID: 67DF
Direct3D: Using dynamic textures
Direct3D: YUV format = RGB
Direct3D: Max texture size = 16384x16384
Direct3D: Device created at 1920x1080
Direct3D: Initialize HLSL
Direct3D: First store options
Direct3D: HLSL initialized
DirectInput: Using DirectInput 8
RawInput: APIs detected
RawInput: APIs detected
stream_buffer_size = 37888
DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channels
Input: Adding keyboard #0: Keyboard (device id: Keyboard product_6f1d2b61-d5a0-11cf-bfc7-444553540000 instance_6f1d2b61-d5a0-11cf-bfc7-444553540000)
Input: Adding mouse #0: HID-compliant mouse (device id: \\?\HID#VID_046D&PID_C049&MI_00#7&b2d31c1&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding lightgun #0: HID-compliant mouse (device id: \\?\HID#VID_046D&PID_C049&MI_00#7&b2d31c1&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding joystick #0: XInput Player 1 (device id: XInput Player 1)
Input: Adding joystick #1: XInput Player 2 (device id: XInput Player 2)
Region ':maincpu' created
unzip: opened archive file roms\esprade.zip
unzip: found roms\esprade.zip ECD
unzip: roms\esprade.zip has no ZIP64 ECD locator
unzip: read roms\esprade.zip central directory
unzip: closing archive file roms\esprade.zip and sending to cache
unzip: found roms\esprade.zip in cache
unzip: opened archive file roms\esprade.zip
unzip: closing archive file roms\esprade.zip and sending to cache
Region ':sprites0' created
unzip: found roms\esprade.zip in cache
unzip: opened archive file roms\esprade.zip
unzip: closing archive file roms\esprade.zip and sending to cache
unzip: found roms\esprade.zip in cache
unzip: opened archive file roms\esprade.zip
unzip: closing archive file roms\esprade.zip and sending to cache
unzip: found roms\esprade.zip in cache
unzip: opened archive file roms\esprade.zip
unzip: closing archive file roms\esprade.zip and sending to cache
unzip: found roms\esprade.zip in cache
unzip: opened archive file roms\esprade.zip
unzip: closing archive file roms\esprade.zip and sending to cache
Region ':layer0' created
unzip: found roms\esprade.zip in cache
unzip: opened archive file roms\esprade.zip
unzip: closing archive file roms\esprade.zip and sending to cache
unzip: found roms\esprade.zip in cache
unzip: opened archive file roms\esprade.zip
unzip: closing archive file roms\esprade.zip and sending to cache
Region ':layer1' created
unzip: found roms\esprade.zip in cache
unzip: opened archive file roms\esprade.zip
unzip: closing archive file roms\esprade.zip and sending to cache
unzip: found roms\esprade.zip in cache
unzip: opened archive file roms\esprade.zip
unzip: closing archive file roms\esprade.zip and sending to cache
Region ':layer2' created
unzip: found roms\esprade.zip in cache
unzip: opened archive file roms\esprade.zip
unzip: closing archive file roms\esprade.zip and sending to cache
Region ':ymz' created
unzip: found roms\esprade.zip in cache
unzip: opened archive file roms\esprade.zip
unzip: closing archive file roms\esprade.zip and sending to cache
Region ':eeprom' created
unzip: found roms\esprade.zip in cache
unzip: opened archive file roms\esprade.zip
unzip: closing archive file roms\esprade.zip and sending to cache
Optional device ':startup' not found
Optional device ':soundlatch' not found
Optional device ':int_timer_right' not found
Optional device ':int_timer_left' not found
Optional device ':oki2' not found
Optional device ':oki1' not found
Optional device ':audiocpu' not found
Optional memory bank ':oki2_bankhi' not found
Optional memory bank ':oki1_bankhi' not found
Optional memory bank ':oki2_banklo' not found
Optional memory bank ':oki1_banklo' not found
Optional memory bank ':z80bank' not found
Optional memory region ':audiocpu' not found
Optional memory region ':oki2' not found
Optional memory region ':oki1' not found
Optional memory region ':layer3' not found
Optional memory region ':sprites3' not found
Optional memory region ':sprites2' not found
Optional memory region ':sprites1' not found
Optional shared pointer ':paletteram.3' not found
Optional shared pointer ':paletteram.2' not found
Optional shared pointer ':paletteram.1' not found
Optional shared pointer ':spriteram.3' not found
Optional shared pointer ':spriteram.2' not found
Optional shared pointer ':spriteram.1' not found
Optional shared pointer ':vctrl.3' not found
Optional shared pointer ':vram.3' not found
Optional shared pointer ':videoregs.3' not found
Optional shared pointer ':videoregs.2' not found
Optional shared pointer ':videoregs.1' not found
Optional device ':screen:finder_dummy_tag' not found
Optional device ':screen:finder_dummy_tag' not found
Optional device ':screen:finder_dummy_tag' not found
Optional memory region ':palette:finder_dummy_tag' not found
Optional device ':eeprom:finder_dummy_tag' not found
Optional device ':ymz:finder_dummy_tag' not found
Starting ESP Ra.De. (International, Ver. 98/04/22) ':'
  (missing dependencies; rescheduling)
Starting Motorola MC68000 ':maincpu'
Starting Timer ':int_timer'
Starting Video Screen ':screen'
Starting palette ':palette'
Starting Serial EEPROM 93C46 (64x16) ':eeprom'
Starting gfxdecode ':gfxdecode'
Starting Speaker ':mono'
  (missing dependencies; rescheduling)
Starting Yamaha YMZ280B PCMD8 ':ymz'
Starting ESP Ra.De. (International, Ver. 98/04/22) ':'
  (missing dependencies; rescheduling)
Starting Speaker ':mono'
Starting ESP Ra.De. (International, Ver. 98/04/22) ':'
Attempting to parse: default.cfg
Input: Remapped joystick #0: XInput Player 1 (device id: XInput Player 1)
Input: Remapped joystick #1: XInput Player 2 (device id: XInput Player 2)
Attempting to parse: default.cfg
Attempting to parse: esprade.cfg
Direct3D: Frame delay: 1, First scanline: 6, L
« Last Edit: February 05, 2019, 04:47:09 am by retrogamer123 »

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 7414
  • Last login:April 10, 2024, 02:02:31 pm
  • Quote me with care
Re: Clarification on using GroovyMAME on a LCD
« Reply #122 on: February 05, 2019, 04:56:57 am »
You seem to have frame delay enabled. You can't use frame delay and bfi simultaneously.
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 of pasting it.

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

retrogamer123

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 26
  • Last login:April 11, 2021, 04:06:23 am
  • I want to build my own arcade controls!
Re: Clarification on using GroovyMAME on a LCD
« Reply #123 on: February 05, 2019, 05:19:22 am »
I just enabled it temporarily to see if it makes any difference with the speedup.
When starting mame without bfi i still have speedup. When i go to the slider controls, set framedelay to 1 and then back to 0, gamespeed is at normal speed O.O.

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 7414
  • Last login:April 10, 2024, 02:02:31 pm
  • Quote me with care
Re: Clarification on using GroovyMAME on a LCD
« Reply #124 on: February 05, 2019, 05:27:14 am »
I just enabled it temporarily to see if it makes any difference with the speedup.
When starting mame without bfi i still have speedup. When i go to the slider controls, set framedelay to 1 and then back to 0, gamespeed is at normal speed O.O.

Without bfi you will have speedup because you're setting vfreq_min = 100 Hz.

command line: mame64.exe esprade -syncrefresh -bfi -fd 0 -v > esprade.txt

Oh wait you have this again?: SwitchRes: Monitor range 54900.00-158112.00,50.00-144.00,0.074,0.098,0.246,0.019,0.032,0.063,1,1,1080,1080,0,0
« Last Edit: February 05, 2019, 05:28:58 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 of pasting it.

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

retrogamer123

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 26
  • Last login:April 11, 2021, 04:06:23 am
  • I want to build my own arcade controls!
Re: Clarification on using GroovyMAME on a LCD
« Reply #125 on: February 05, 2019, 05:32:58 am »
yes i have, SwitchRes: Monitor range 54900.00-158112.00,50.00-144.00,0.074,0.098,0.246,0.019,0.032,0.063,1,1,1080,1080,0,0
for normal and

SwitchRes: Monitor range 109800-158112.00,100.00-144.00,0.074,0.098,0.246,0.019,0.032,0.063,1,1,1080,1080,0,0
in the ini when i enable bfi

Funny thing is when I have black frame insertion activated, speedup is also gone for me when i use the slider controls got to frame_delay 1 and then back to 0

edit: oh it probably switches refreshrate somehow when doing this, setting frame_delay to 1 in the slider controls, the screen goes black for a sec

edit2: Is it normal to have the switchres: error trying to fill monitor range with d3d at mame startup, because of my lcd. I still have this one. I see it on the commandline but not in the logs.
« Last Edit: February 05, 2019, 05:40:59 am by retrogamer123 »

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 7414
  • Last login:April 10, 2024, 02:02:31 pm
  • Quote me with care
Re: Clarification on using GroovyMAME on a LCD
« Reply #126 on: February 05, 2019, 05:39:26 am »
Could you start from scratch? This is to avoid cfg corruption. Download my full package, unzip, copy your current mame.ini, leave the frame delay slider alone, and run with non-bfi and bfi configuration, and post both logs, please full logs with the endings, not cropped like the previous ones.

Also, please launch the game from command line, not from internal gui.
« Last Edit: February 05, 2019, 05:41:42 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 of pasting it.

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

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 7414
  • Last login:April 10, 2024, 02:02:31 pm
  • Quote me with care
Re: Clarification on using GroovyMAME on a LCD
« Reply #127 on: February 05, 2019, 05:43:21 am »
edit2: Is it normal to have the switchres: error trying to fill monitor range with d3d at mame startup, because of my lcd. I still have this one. I see it on the commandline but not in the logs.

No, it's not normal. Please copy the exact error, d3d has nothing to do with the monitor range, you're probably mixing two errors.
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 of pasting it.

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

retrogamer123

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 26
  • Last login:April 11, 2021, 04:06:23 am
  • I want to build my own arcade controls!
Re: Clarification on using GroovyMAME on a LCD
« Reply #128 on: February 05, 2019, 05:53:59 am »
Starting from scratch with the full package did the trick. It works normal now  :)
Many many thanks for all your help.

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 7414
  • Last login:April 10, 2024, 02:02:31 pm
  • Quote me with care
Re: Clarification on using GroovyMAME on a LCD
« Reply #129 on: February 05, 2019, 06:03:51 am »
Starting from scratch with the full package did the trick. It works normal now  :)
Many many thanks for all your help.

If you have the time and energy, try to figure out what the issue was, so we all learn  :)
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 of pasting it.

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

lettuce

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1900
  • Last login:December 31, 2021, 01:46:10 pm
  • Make It So!
Re: Clarification on using GroovyMAME on a LCD
« Reply #130 on: July 28, 2019, 01:46:22 pm »
Im guessing this only works for AMD cards not Intel, as the copy to clip board option for me is greyed out??

cybermat

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 29
  • Last login:June 05, 2023, 08:27:39 am
Re: Clarification on using GroovyMAME on a LCD
« Reply #131 on: May 12, 2020, 10:49:36 am »
Sorry to bump this thread (in my opinion ruined by a lot of useless posts).

At the moment i'm using LCD in fixed way and i'm happy with it, i don't have problems, but i want to see running Rtype at 55 just to see if it's possible in my enviroment.

I use an Nvidia card and i'm trying to use custom and crtrange way , hoping to have well understood that with this method i should not add custom modelines manually.
Monitor used is a simple HP L1950 4:3

I cannot read EDID with ArcadeOs so i used "MonInfo" , for crtrange i read a thread where obtaining the values from Groovyarcade log.
I added a dummy modeline 1280x1024@59 with Nvidia control panel (and also via CRU) , but it's shown as "native" and not "custom" under Arcade_os.

I don't know if the expected behaviour should be having 55hz, but i cannot use this refresh.

Attached you can find mame ini and rtype log

Regarding these voices

lock_system_modes         1
lock_unsupported_modes    1

I suppose they are ok, i keep these to "0" when i use LCD in fixed mode. Anyway if i put to 0 i got black screen.

I read a lot and went up and down for the forum, so forgive me if i didn't understand! :)

« Last Edit: May 12, 2020, 01:36:07 pm by cybermat »

schmerzkaufen

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 791
  • Last login:October 03, 2023, 02:27:31 pm
  • Multiple Electronic Machine Emulator
Re: Clarification on using GroovyMAME on a LCD
« Reply #132 on: May 13, 2020, 09:50:08 am »
I use an Nvidia card and i'm trying to use custom and crtrange way , hoping to have well understood that with this method i should not add custom modelines manually.
But you should! (add modes tho, not modelines)
Since you're using an nVidia card that's not compatible with Emudrivers and dynamic modelines, you're therefore trying the 'static' method, which requires you to create custom static individual modes from the nVidia control panel or CRU.
Typically you write a rounded Hz value like 55 or 57 at your panel resolution then hit add, then the software kindly adjusts the other modeline parameters for you in the background (well that's how I picture what happens lol)
You can try and create only one for 55Hz games (1280x1024@55), but you can also make several from 53 to 61 if you want the vast majority of games supported, or narrower 54 to 60, whatever, and provided your monitor will accept all 7 or 9 modes, of course.

I added a dummy modeline 1280x1024@59 with Nvidia control panel (and also via CRU) , but it's shown as "native" and not "custom" under Arcade_os.
It might be that there is already an existing 59Hz mode in your nVidia driver (typically actually the 59.94 mode labelled '59'), in which case you could try to erase it and then try again to create you own desired 'real' 59 mode.

PS: for the dummy mode I always pick whatever my panel resolution but at 58Hz or lower, if there is ever need to avoid confusion. Anyway getting rid of the stock nVidia 59 mode is recommended so you won't be bothered by it again.
Scratch that, actually I seem to recall it's ****x****@0 you should write. The dummy mode is used for the dynamic method (w/ AMD & Emudrivers)

lock_system_modes         1
lock_unsupported_modes    1

I suppose they are ok, i keep these to "0" when i use LCD in fixed mode. Anyway if i put to 0 i got black screen.
Yes IIRC both on 0 should be fine. If you have created the 55Hz modeline at your nVidia panel or CRU, this time you should get a picture, I think. ^^

Note that again there's no guarantee your monitor will accept 55Hz (old non-HD monitors are often good picks for refresh flexibility tho). And even if you do get a picture; you'll have to check what the info says right after booting the game, as it tells both the game's refresh and the switches/monitor's running, they should be pretty close to a match with less than 1Hz discrepancy if the method worked as expected, and scrollings should be perfectly smooth.
« Last Edit: May 13, 2020, 09:58:33 am by schmerzkaufen »

cybermat

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 29
  • Last login:June 05, 2023, 08:27:39 am
Re: Clarification on using GroovyMAME on a LCD
« Reply #133 on: May 14, 2020, 06:45:28 am »
Ok thanks for clarification about Nvidia enviroment.
I tried but it seems that i cannot sync to 55hz! Nvidia let me create 55-56-57 and so on but when i select for example 55 via Windows it seems ok...i come back to settings but i see 60hz.

So running Groovymame a game like Rtype, i have 109% as running speed!

SwitchRes: [1280]x[1024]_[55=55.000000Hz]
   rng(0): 1280 x1024_55.000000p 0.000000 [integ] scale(3, 4, 1) diff(10.00, 0.00, -0.0176) ratio(3.333, 4.000)

SwitchRes: [1280]x[1024]_[60=60.000000Hz]
   rng(0): 1280 x1024_60.000000p 0.000000 [integ] scale(3, 4, 1) diff(10.00, 0.00, 4.9824) ratio(3.333, 4.000)

SwitchRes: [1280]x[1024]_[75=75.000000Hz]
   rng(0):  out of range

SwitchRes: [rtype] (1) horizontal (384x256@55.017605)->(1280x1024@55.000000)
   rng(0): 1280 x1024_55.000000p 0.000000 [integ] scale(3, 4, 1) diff(10.00, 0.00, -0.0176) ratio(3.333, 4.000)
SwitchRes: Modeline "1280x1024_55 0.000000KHz 55.000000Hz" 0.000000 1280 0 0 0 1024 0 0 0   -hsync -vsync
Starting R-Type (World) ':'
Attempting to parse: default.cfg
Attempting to parse: rtype.cfg
Average speed: 108.78% (6 seconds)
Sound: buffer overflows=4 underflows=0

I came back to LCD fix!

I got the chance to thanks all the people involved on this project. I'm changing PC, so i will have a spare pc with HD 5770, so i will probably come back here :)



« Last Edit: May 14, 2020, 06:53:13 am by cybermat »

schmerzkaufen

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 791
  • Last login:October 03, 2023, 02:27:31 pm
  • Multiple Electronic Machine Emulator
Re: Clarification on using GroovyMAME on a LCD
« Reply #134 on: May 14, 2020, 07:20:25 am »
Ok thanks for clarification about Nvidia enviroment.
I tried but it seems that i cannot sync to 55hz! Nvidia let me create 55-56-57 and so on but when i select for example 55 via Windows it seems ok...i come back to settings but i see 60hz.

So running Groovymame a game like Rtype, i have 109% as running speed!

SwitchRes: [1280]x[1024]_[55=55.000000Hz]
   rng(0): 1280 x1024_55.000000p 0.000000 [integ] scale(3, 4, 1) diff(10.00, 0.00, -0.0176) ratio(3.333, 4.000)

SwitchRes: [1280]x[1024]_[60=60.000000Hz]
   rng(0): 1280 x1024_60.000000p 0.000000 [integ] scale(3, 4, 1) diff(10.00, 0.00, 4.9824) ratio(3.333, 4.000)

SwitchRes: [1280]x[1024]_[75=75.000000Hz]
   rng(0):  out of range

SwitchRes: [rtype] (1) horizontal (384x256@55.017605)->(1280x1024@55.000000)
   rng(0): 1280 x1024_55.000000p 0.000000 [integ] scale(3, 4, 1) diff(10.00, 0.00, -0.0176) ratio(3.333, 4.000)
SwitchRes: Modeline "1280x1024_55 0.000000KHz 55.000000Hz" 0.000000 1280 0 0 0 1024 0 0 0   -hsync -vsync
Starting R-Type (World) ':'
Attempting to parse: default.cfg
Attempting to parse: rtype.cfg
Average speed: 108.78% (6 seconds)
Sound: buffer overflows=4 underflows=0
Aw, maybe that's bad luck, some monitors can, some cannot... honestly I have tried about 10 different LCDs I found around, and only 2 would accept to run non-60Hz.

PS: could you please post the full log ? thx

cybermat

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 29
  • Last login:June 05, 2023, 08:27:39 am
Re: Clarification on using GroovyMAME on a LCD
« Reply #135 on: May 14, 2020, 08:21:33 am »
That's the log!

I use HP L1950 and is a good lcd for a bartop.

- At the moment i have a raspberry with rgbpi cable (scart) connect to a Trinitron CRT consumer. With this setup i can play properly a lot of games with their native refresh.
- A bartop with this LCD using Geforce 1030. I can say that with groovymame, even though i use a LCD, i have a good user experience. This build should be the only one to be used, it will save a lot of headhache when you need to run games like wonderboy, powerspikes etc etc

In the future i will set up my (future) old pc with HD 5770 following the guide found here with groovymane, connecting to Trinitron CRT consumer.

« Last Edit: May 14, 2020, 08:28:34 am by cybermat »

schmerzkaufen

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 791
  • Last login:October 03, 2023, 02:27:31 pm
  • Multiple Electronic Machine Emulator
Re: Clarification on using GroovyMAME on a LCD
« Reply #136 on: May 14, 2020, 10:51:27 am »
Mmh..and yet the 55Hz mode is available in the list.

Maybe the problem is not the monitor, but at this point I am not good enough to give better advice, sorry.   :dunno

cybermat

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 29
  • Last login:June 05, 2023, 08:27:39 am
Re: Clarification on using GroovyMAME on a LCD
« Reply #137 on: May 15, 2020, 10:43:13 am »
It's available but it's a fake entry, when you select it you still have 60hz.

I tried 55hz on ProLite XB2374HDS with GTX970 and Nvidia control panel tell me "out of range" , so i think that GT1030 on HP L1050 is not able to understand that is out of range and let me add that resolution.
With CRU i cannot add refresh under 60hz (59 58 etc etc are red).

The most important thing is understanding that i'm doing well, so i can test on different LCD this setup. At work i have several different LCD.






schmerzkaufen

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 791
  • Last login:October 03, 2023, 02:27:31 pm
  • Multiple Electronic Machine Emulator
Re: Clarification on using GroovyMAME on a LCD
« Reply #138 on: May 15, 2020, 11:42:20 am »
If you can get your hands on a ViewSonic the chances are good with that manufacturer, I use one myself (check my signature).

There is a hint, if you download a ViewSonic model's user guide .pdf (not the comparison sheet or datasheet, use their downloads search engine or check their global site), then scroll down to the specifications and in the list of supported resolutions you see that uncommon 56Hz listed, then it probably means that it is a model similar to mine: compatible with any native refresh you throw at it and therefore fully supporting GroovyMAME whether using the dynamic or static method.



In regards to other brands, sorry IDK, my only other one compatible is a Maxdata/Belinea from 2007.

People will find that buying a G-Sync or FreeSync monitor to go with their GPU is much easier, of course.
But since some much cheaper monitors might support non-60Hz then naturally Groovy expands our choices and can save money.

cybermat

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 29
  • Last login:June 05, 2023, 08:27:39 am
Re: Clarification on using GroovyMAME on a LCD
« Reply #139 on: May 18, 2020, 02:47:22 pm »
Ok my daddy's LCD, a Samsung Syncmaster 930BF has that 56hz! So this week end i will give a try and in case of success, i will stole it!  :lol :lol :lol

I found a lot of old threads and i don't know what is the current situation, but i don't want to open another thread regarding the best settings to use with a LCD, taking in account lags and so on... I read about a lot of comparisons, lag testing, bgfx vs d3d9 d3d11 etc etc

I have on my bartop Windows 7 64 bit and i use BGFX with auto as backend.

- Windows Aero should be on or off ?
- BGFX should be D3d9 , d3d11 or auto ?

or would be better put video as "direct3d" using HLSL ?


schmerzkaufen

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 791
  • Last login:October 03, 2023, 02:27:31 pm
  • Multiple Electronic Machine Emulator
Re: Clarification on using GroovyMAME on a LCD
« Reply #140 on: May 18, 2020, 03:16:18 pm »
Ok my daddy's LCD, a Samsung Syncmaster 930BF has that 56hz!
Please do not misunderstand, it doesn't have to be 56Hz, and I simply gave you the only example I know of a hint that ViewSonic monitors might be compatible with non-60Hz refreshes.

If whatever monitor from any other name brand has non-60Hz modes listed in the specs then yes, they might be like the ViewSonics, but again this is only a vague clue, not a solid indication.

I found a lot of old threads and i don't know what is the current situation, but i don't want to open another thread regarding the best settings to use with a LCD, taking in account lags and so on... I read about a lot of comparisons, lag testing, bgfx vs d3d9 d3d11 etc etc
Be careful reading the forums, there is no emulator that confuses people more than GroovyMAME as far as I've seen and experienced, which is why it is not very popular. If you read too much info in disorder across the community you will definitely get overwhelmed/confused. Some threads carry outdated information.

- Windows Aero should be on or off ?
off
- BGFX should be D3d9 , d3d11 or auto ?
or would be better put video as "direct3d" using HLSL ?
Note if you use BGFX, the GroovyMAME features (smooth scrollings @ exact refresh with frame_delay lag reduction) WILL NOT WORK.

Leave 'video' on 'auto', because Groovy is coded to use d3d9ex by default.
You can use HLSL (adjust settings using the 'raster.ini' file)

Basically with GroovyMAME, you cannot do whatever you want changing the settings in the mame.ini at random, you have to follow some strict rules or everything will fall apart, the first step should always be here;
http://geedorah.com/eiusdemmodi/forum/viewtopic.php?id=433
If you succeed there is nothing better, nothing more accurate as far as MAME emulation goes.
« Last Edit: May 18, 2020, 03:17:55 pm by schmerzkaufen »

cybermat

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 29
  • Last login:June 05, 2023, 08:27:39 am
Re: Clarification on using GroovyMAME on a LCD
« Reply #141 on: May 19, 2020, 05:54:29 am »
Ok thanks! I started from the scratch changing what is suggested on the link you provided, and i can say that i can see more responsiveness! Wonder Boy is a good test bench. Frame Delay has been set to 5.
I'm testing different HLSL settings, i've seen on shmups an interesting thread, in the past i was used to use Lettuce's settings, that i find very good.

Regarding 56hz, i understood that 56hz is not meaning "LCD will support anything you set" , but it's a good starting point. I tried 3 LCD where 56hz is not mentioned and it doesn work, so i will test on a LCD where is stated 800x600@56hz.


schmerzkaufen

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 791
  • Last login:October 03, 2023, 02:27:31 pm
  • Multiple Electronic Machine Emulator
Re: Clarification on using GroovyMAME on a LCD
« Reply #142 on: January 02, 2022, 11:28:08 am »
Heya! upping this thread.  :applaud:

I have been trying to do the static method again, since I'll be using an nVidia GPU for some time,
and oh damn, it's been a long while and I get strange results, also I bet a couple of things are different now with SwitchRes 2.0 ^^

Here's what I have extracted from moninfo and turned into workable modeline and crt range
"1920x1080" 148,500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
into;
Code: [Select]
SwitchRes: user modeline "1920x1080_60 67.500000KHz 60.000000Hz" 148.500000 1920 2008 2052 2200 1080 1084 1089 1125   +hsync +vsync
Switchres: Monitor range 67275.00-67725.00,59.80-60.20,0.593,0.296,0.997,0.059,0.074,0.533,1,1,1080,1080,0,0
then into;
Code: [Select]
56250-84375,50.00-75.00,0.593,0.296,0.997,0.059,0.074,0.533,1,1,1080,1080,0,0
Got a bunch of custom modes ready, set from the nVidia control panel (54, 55, 56, etc) and checked that they're all working (this is my usual lcd monitor so of course they do)

Not sure how I am supposed to configure modern Groovy though... attached a couple logs and mame.ini in its current state.

What happends is that even with sync_refresh_tolerance set to 1 the games are running at weird refreshes like 94% for esprade, or 97% for raiden2, with distorted sound.
Previously with that method I was getting 99% speed on all games with no issues, so I bet it is still possible today but I am doing it wrong....anew ?  :lol

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 7414
  • Last login:April 10, 2024, 02:02:31 pm
  • Quote me with care
Re: Clarification on using GroovyMAME on a LCD
« Reply #143 on: January 02, 2022, 02:20:08 pm »
The first thing I'm seeing wrong is -refresh_dont_care: you shouldn't have it enabled. I don't remember if this was the recommendation at some point, but certainly it's not now. Basically what happens with that option is that you tell SR that the refresh is editable, when it is not.
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 of pasting it.

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

schmerzkaufen

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 791
  • Last login:October 03, 2023, 02:27:31 pm
  • Multiple Electronic Machine Emulator
Re: Clarification on using GroovyMAME on a LCD
« Reply #144 on: January 02, 2022, 02:29:25 pm »
The first thing I'm seeing wrong is -refresh_dont_care

Yup ! you spotted the culprit immediately.

That setting is on by default actually, I didn't pay attention but that makes sense. ^^

Thanks !  :cheers: