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: GroovyMame and FreeSync  (Read 7120 times)

0 Members and 1 Guest are viewing this topic.

oomek

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 268
  • Last login:December 08, 2023, 02:31:38 pm
  • Mame forever.
    • https://github.com/oomek
GroovyMame and FreeSync
« on: February 23, 2017, 03:30:16 pm »
Is it necessary, unnecessary, mistake or irrelevant for GM to automaticaly adjust Delay scanline: -107 ?
Does it affect the latency in any way when i'm using -nowaitvsync and -nosyncrefresh ?

Code: [Select]
D:\GAMES\MAME182>mame64 -nokeepaspect  -nowaitvsync -nofilter cawing -v
SwitchRes: v0.016_final, Monitor: custom, Orientation: horizontal, Modeline generation: disabled
SwitchRes: Monitor range 54048.00-81072.00,48.00-72.00,0.643,0.984,1.627,0.012,0.037,0.518,0,1,1080,1080,0,0
SwitchRes: \\.\DISPLAY5: AMD Radeon R7 200 Series (PCI\VEN_1002&DEV_6658&SUBSYS_E258174B&REV_00)
SwitchRes: Device key: System\CurrentControlSet\Control\Video\{094BA853-AD5C-465A-8BF8-B16501159C96}\0000
ATI/AMD ADL init
ADL Library not found!
ERROR: ADL Initialization error!
Switchres: Searching for custom video modes...
Switchres: [  1]  640x 480 @ 59 : system mode
Switchres: [  2]  640x 480 @ 60 : system mode
Switchres: [  3]  640x 480 @ 72 : system mode
Switchres: [  4]  720x 480 @ 59 : system mode
Switchres: [  5]  720x 480 @ 60 : system mode
Switchres: [  6]  720x 480 @ 72 : system mode
Switchres: [  7]  720x 576 @ 50 : system mode
Switchres: [  8]  720x 576 @ 60 : system mode
Switchres: [  9]  720x 576 @ 72 : system mode
Switchres: [ 10]  800x 600 @ 60 : system mode
Switchres: [ 11]  800x 600 @ 72 : system mode
Switchres: [ 12] 1024x 768 @ 60 : system mode
Switchres: [ 13] 1024x 768 @ 72 : system mode
Switchres: [ 14] 1120x1080 @ 60 : system mode
Switchres: [ 15] 1120x1080 @ 72 : system mode
Switchres: [ 16] 1152x 648 @ 50 : system mode
Switchres: [ 17] 1152x 648 @ 59 : system mode
Switchres: [ 18] 1152x 648 @ 60 : system mode
Switchres: [ 19] 1280x 720 @ 50 : system mode
Switchres: [ 20] 1280x 720 @ 59 : system mode
Switchres: [ 21] 1280x 720 @ 60 : system mode
Switchres: [ 22] 1280x 768 @ 60 : system mode
Switchres: [ 23] 1280x 768 @ 72 : system mode
Switchres: [ 24] 1280x 800 @ 60 : system mode
Switchres: [ 25] 1280x 800 @ 72 : system mode
Switchres: [ 26] 1280x 960 @ 60 : system mode
Switchres: [ 27] 1280x 960 @ 72 : system mode
Switchres: [ 28] 1280x1024 @ 60 : system mode
Switchres: [ 29] 1280x1024 @ 72 : system mode
Switchres: [ 30] 1360x 768 @ 60 : system mode
Switchres: [ 31] 1360x 768 @ 72 : system mode
Switchres: [ 32] 1366x 768 @ 60 : system mode
Switchres: [ 33] 1366x 768 @ 72 : system mode
Switchres: [ 34] 1440x 900 @ 60 : system mode
Switchres: [ 35] 1440x 900 @ 72 : system mode
Switchres: [ 36] 1600x 900 @ 60 : system mode
Switchres: [ 37] 1600x 900 @ 72 : system mode
Switchres: [ 38] 1600x1080 @ 60 : system mode
Switchres: [ 39] 1600x1080 @ 72 : system mode
Switchres: [ 40] 1680x1050 @ 60 : system mode
Switchres: [ 41] 1680x1050 @ 72 : system mode
Switchres: [ 42] 1776x1000 @ 50 : system mode
Switchres: [ 43] 1776x1000 @ 59 : system mode
Switchres: [ 44] 1776x1000 @ 60 : system mode
Switchres: [ 45] 1920x1080 @ 50 : system mode
Switchres: [ 46] 1920x1080 @ 59* : system mode
Switchres: [ 47] 1920x1080 @ 60 : system mode
Switchres: [ 48] 1920x1080 @ 72 : system mode
SwitchRes: Found 0 custom of 48 active video modes
SwitchRes: -resolution was forced as 1600x1080@72

SwitchRes: Entering switchres_modeline_setup
SwitchRes: v0.016_final:[cawing] Calculating best video mode for 384x224@59.637405 orientation: normal

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

SwitchRes: [ 640]x[ 480]_[60=60.000000Hz] - locked

SwitchRes: [ 640]x[ 480]_[72=72.000000Hz] - locked

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

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

SwitchRes: [ 720]x[ 480]_[72=72.000000Hz] - locked

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

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

SwitchRes: [ 720]x[ 576]_[72=72.000000Hz] - locked

SwitchRes: [ 800]x[ 600]_[60=60.000000Hz] - locked

SwitchRes: [ 800]x[ 600]_[72=72.000000Hz] - locked

SwitchRes: [1024]x[ 768]_[60=60.000000Hz] - locked

SwitchRes: [1024]x[ 768]_[72=72.000000Hz] - locked

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

SwitchRes: [1120]x[1080]_[72=72.000000Hz] - locked

SwitchRes: [1152]x[ 648]_[50=50.000000Hz] - locked

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

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

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

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

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

SwitchRes: [1280]x[ 768]_[60=60.000000Hz] - locked

SwitchRes: [1280]x[ 768]_[72=72.000000Hz] - locked

SwitchRes: [1280]x[ 800]_[60=60.000000Hz] - locked

SwitchRes: [1280]x[ 800]_[72=72.000000Hz] - locked

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

SwitchRes: [1280]x[ 960]_[72=72.000000Hz] - locked

SwitchRes: [1280]x[1024]_[60=60.000000Hz] - locked

SwitchRes: [1280]x[1024]_[72=72.000000Hz] - locked

SwitchRes: [1360]x[ 768]_[60=60.000000Hz] - locked

SwitchRes: [1360]x[ 768]_[72=72.000000Hz] - locked

SwitchRes: [1366]x[ 768]_[60=60.000000Hz] - locked

SwitchRes: [1366]x[ 768]_[72=72.000000Hz] - locked

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

SwitchRes: [1440]x[ 900]_[72=72.000000Hz] - locked

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

SwitchRes: [1600]x[ 900]_[72=72.000000Hz] - locked

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

SwitchRes: [1600]x[1080]_[72=72.000000Hz]
   rng(0): 1600 x1080_72.000000p 0.000000 [fract] scale(3, 4, 1) diff(13.60, 33.39, 12.3626) ratio(4.167, 4.821)

SwitchRes: [1680]x[1050]_[60=60.000000Hz] - locked

SwitchRes: [1680]x[1050]_[72=72.000000Hz] - locked

SwitchRes: [1776]x[1000]_[50=50.000000Hz] - locked

SwitchRes: [1776]x[1000]_[59=59.000000Hz] - locked

SwitchRes: [1776]x[1000]_[60=60.000000Hz] - locked

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

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

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

SwitchRes: [1920]x[1080]_[72=72.000000Hz] - locked

SwitchRes: [cawing] (1) horizontal (384x224@59.637405)->(1600x1080@72.000000)
   rng(0): 1600 x1080_72.000000p 0.000000 [fract] scale(3, 4, 1) diff(13.60, 33.39, 12.3626) ratio(4.167, 4.821)
SwitchRes: Setting option -rotate
SwitchRes: Setting option -noror
SwitchRes: Setting option -autoror
SwitchRes: Setting option -norol
SwitchRes: Setting option -noautorol
SwitchRes: Setting option -nokeepaspect
SwitchRes: Setting option -unevenstretch
SwitchRes: Setting option -nounevenstretchx
SwitchRes: Setting option -noblack_frame_insertion
SwitchRes: Setting option -nosyncrefresh
SwitchRes: Setting option -notriplebuffer
SwitchRes: Setting option -nowaitvsync
SwitchRes: Setting option -nofilter
Video: Monitor 65537 = "\\.\DISPLAY5" (primary)
Direct3D: Using Direct3D 9Ex
Physical width 1920, height 1080
Direct3D: Initialize
Direct3D: Configuring adapter #0 = AMD Radeon R7 200 Series
Direct3D: Adapter has Vendor ID: 1002 and Device ID: 6658
Direct3D: Using dynamic textures
Direct3D: YUV format = RGB
Direct3D: Max texture size = 16384x16384
Direct3D: Device created at 1600x1080
Direct3D: First scanline: 1, Last scanline: 1080, Break scanline: 1080, Delay scanline: -107
Direct3D: Initialize HLSL
Direct3D: First store options
Direct3D: HLSL initialized
RawInput: APIs detected
RawInput: APIs detected
RawInput: APIs detected
PortAudio: API MME has 5 devices
PortAudio: MME: "Microsoft Sound Mapper - Input"
PortAudio: MME: "Desktop Microphone (Microsoft« "
PortAudio: MME: "Microsoft Sound Mapper - Output"
PortAudio: MME: "Speakers (High Definition Audio" (default)
PortAudio: MME: "Digital Audio (S/PDIF) (High De"
PortAudio: API Windows DirectSound has 5 devices
PortAudio: Windows DirectSound: "Primary Sound Capture Driver"
PortAudio: Windows DirectSound: "Desktop Microphone (Microsoft« LifeCam HD-3000)"
PortAudio: Windows DirectSound: "Primary Sound Driver" (default)
PortAudio: Windows DirectSound: "Speakers (High Definition Audio Device)"
PortAudio: Windows DirectSound: "Digital Audio (S/PDIF) (High Definition Audio Device)"
PortAudio: API Windows WASAPI has 3 devices
PortAudio: Windows WASAPI: "Speakers (High Definition Audio Device)" (default)
PortAudio: Windows WASAPI: "Digital Audio (S/PDIF) (High Definition Audio Device)"
PortAudio: Windows WASAPI: "Desktop Microphone (Microsoft® LifeCam HD-3000)"
PortAudio: API Windows WDM-KS has 3 devices
PortAudio: Windows WDM-KS: "SPDIF Out (HD Audio SPDIF out)"
PortAudio: Windows WDM-KS: "Speakers (HD Audio Speaker)" (default)
PortAudio: Windows WDM-KS: "Desktop Microphone (Microsoft® LifeCam HD-3000)"
PortAudio: Using device "Speakers (High Definition Audio Device)" on API "Windows WASAPI"
PortAudio: Sample rate is 48000 Hz, device output latency is 2.67 ms
PortAudio: Allowed additional buffering latency is 10.00 ms/480 frames
Input: Adding keyboard #0: HID Keyboard Device (device id: \\?\HID#VID_046D&PID_C52B&MI_00#8&330a63b2&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding keyboard #1: Razer Mamba (device id: \\?\HID#VID_1532&PID_0044&MI_01#8&495080f&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding keyboard #2: HID Keyboard Device (device id: \\?\HID#VID_1532&PID_0044&MI_02&Col01#8&286c45d1&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding mouse #0: HID-compliant mouse (device id: \\?\HID#VID_046D&PID_C52B&MI_01&Col01#8&a9fb5e9&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding mouse #1: Razer Mamba (device id: \\?\HID#VID_1532&PID_0044&MI_00#8&1f4235b3&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding lightgun #0: HID-compliant mouse (device id: \\?\HID#VID_046D&PID_C52B&MI_01&Col01#8&a9fb5e9&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Input: Adding lightgun #1: Razer Mamba (device id: \\?\HID#VID_1532&PID_0044&MI_00#8&1f4235b3&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
Region ':maincpu' created
unzip: opened archive file D:\GAMES\MAME\roms.big\cawing.zip
unzip: found D:\GAMES\MAME\roms.big\cawing.zip ECD
unzip: D:\GAMES\MAME\roms.big\cawing.zip has no ZIP64 ECD locator
unzip: read D:\GAMES\MAME\roms.big\cawing.zip central directory
unzip: closing archive file D:\GAMES\MAME\roms.big\cawing.zip and sending to cache
unzip: found D:\GAMES\MAME\roms.big\cawing.zip in cache
unzip: opened archive file D:\GAMES\MAME\roms.big\cawing.zip
unzip: closing archive file D:\GAMES\MAME\roms.big\cawing.zip and sending to cache
unzip: found D:\GAMES\MAME\roms.big\cawing.zip in cache
unzip: opened archive file D:\GAMES\MAME\roms.big\cawing.zip
unzip: closing archive file D:\GAMES\MAME\roms.big\cawing.zip and sending to cache
unzip: found D:\GAMES\MAME\roms.big\cawing.zip in cache
unzip: opened archive file D:\GAMES\MAME\roms.big\cawing.zip
unzip: closing archive file D:\GAMES\MAME\roms.big\cawing.zip and sending to cache
unzip: found D:\GAMES\MAME\roms.big\cawing.zip in cache
unzip: opened archive file D:\GAMES\MAME\roms.big\cawing.zip
unzip: closing archive file D:\GAMES\MAME\roms.big\cawing.zip and sending to cache
Region ':gfx' created
unzip: found D:\GAMES\MAME\roms.big\cawing.zip in cache
unzip: opened archive file D:\GAMES\MAME\roms.big\cawing.zip
unzip: closing archive file D:\GAMES\MAME\roms.big\cawing.zip and sending to cache
unzip: found D:\GAMES\MAME\roms.big\cawing.zip in cache
unzip: opened archive file D:\GAMES\MAME\roms.big\cawing.zip
unzip: closing archive file D:\GAMES\MAME\roms.big\cawing.zip and sending to cache
unzip: found D:\GAMES\MAME\roms.big\cawing.zip in cache
unzip: opened archive file D:\GAMES\MAME\roms.big\cawing.zip
unzip: closing archive file D:\GAMES\MAME\roms.big\cawing.zip and sending to cache
unzip: found D:\GAMES\MAME\roms.big\cawing.zip in cache
unzip: opened archive file D:\GAMES\MAME\roms.big\cawing.zip
unzip: closing archive file D:\GAMES\MAME\roms.big\cawing.zip and sending to cache
Region ':audiocpu' created
unzip: found D:\GAMES\MAME\roms.big\cawing.zip in cache
unzip: opened archive file D:\GAMES\MAME\roms.big\cawing.zip
unzip: closing archive file D:\GAMES\MAME\roms.big\cawing.zip and sending to cache
Region ':oki' created
unzip: found D:\GAMES\MAME\roms.big\cawing.zip in cache
unzip: opened archive file D:\GAMES\MAME\roms.big\cawing.zip
unzip: closing archive file D:\GAMES\MAME\roms.big\cawing.zip and sending to cache
unzip: found D:\GAMES\MAME\roms.big\cawing.zip in cache
unzip: opened archive file D:\GAMES\MAME\roms.big\cawing.zip
unzip: closing archive file D:\GAMES\MAME\roms.big\cawing.zip and sending to cache
Region ':aboardplds' created
unzip: found D:\GAMES\MAME\roms.big\cawing.zip in cache
unzip: opened archive file D:\GAMES\MAME\roms.big\cawing.zip
unzip: closing archive file D:\GAMES\MAME\roms.big\cawing.zip and sending to cache
unzip: found D:\GAMES\MAME\roms.big\cawing.zip in cache
unzip: opened archive file D:\GAMES\MAME\roms.big\cawing.zip
unzip: closing archive file D:\GAMES\MAME\roms.big\cawing.zip and sending to cache
unzip: found D:\GAMES\MAME\roms.big\cawing.zip in cache
unzip: opened archive file D:\GAMES\MAME\roms.big\cawing.zip
unzip: closing archive file D:\GAMES\MAME\roms.big\cawing.zip and sending to cache
unzip: found D:\GAMES\MAME\roms.big\cawing.zip in cache
unzip: opened archive file D:\GAMES\MAME\roms.big\cawing.zip
unzip: closing archive file D:\GAMES\MAME\roms.big\cawing.zip and sending to cache
unzip: found D:\GAMES\MAME\roms.big\cawing.zip in cache
unzip: opened archive file D:\GAMES\MAME\roms.big\cawing.zip
unzip: closing archive file D:\GAMES\MAME\roms.big\cawing.zip and sending to cache
Region ':bboardplds' created
unzip: found D:\GAMES\MAME\roms.big\cawing.zip in cache
unzip: opened archive file D:\GAMES\MAME\roms.big\cawing.zip
unzip: closing archive file D:\GAMES\MAME\roms.big\cawing.zip and sending to cache
unzip: found D:\GAMES\MAME\roms.big\cawing.zip in cache
unzip: opened archive file D:\GAMES\MAME\roms.big\cawing.zip
unzip: closing archive file D:\GAMES\MAME\roms.big\cawing.zip and sending to cache
Starting Carrier Air Wing (World 901012) ':'
Optional memory region ':stars' not found
Optional memory region ':key' not found
Optional shared pointer ':decrypted_opcodes' not found
Optional device ':msm2' not found
Optional device ':msm1' not found
Optional device ':m48t35' not found
Optional shared pointer ':output' not found
Optional shared pointer ':objram2' not found
Optional shared pointer ':objram1' not found
Optional shared pointer ':qsound_ram2' not found
Optional shared pointer ':qsound_ram1' not found
  (missing dependencies; rescheduling)
Starting M68000 ':maincpu'
Starting Z80 ':audiocpu'
Starting Video Screen ':screen'
  (missing dependencies; rescheduling)
Starting gfxdecode ':gfxdecode'
Starting palette ':palette'
Starting Speaker ':mono'
  (missing dependencies; rescheduling)
Starting Generic 8-bit latch ':soundlatch'
Starting Generic 8-bit latch ':soundlatch2'
Starting YM2151 ':2151'
Starting OKI6295 ':oki'
Starting Carrier Air Wing (World 901012) ':'
Optional memory region ':stars' not found
Optional memory region ':key' not found
Optional shared pointer ':decrypted_opcodes' not found
Optional device ':msm2' not found
Optional device ':msm1' not found
Optional device ':m48t35' not found
Optional shared pointer ':output' not found
Optional shared pointer ':objram2' not found
Optional shared pointer ':objram1' not found
Optional shared pointer ':qsound_ram2' not found
Optional shared pointer ':qsound_ram1' not found
  (missing dependencies; rescheduling)
Starting Video Screen ':screen'
Starting Speaker ':mono'
Starting Carrier Air Wing (World 901012) ':'
Optional memory region ':stars' not found
Optional memory region ':key' not found
Optional shared pointer ':decrypted_opcodes' not found
Optional device ':msm2' not found
Optional device ':msm1' not found
Optional device ':m48t35' not found
Optional shared pointer ':output' not found
Optional shared pointer ':objram2' not found
Optional shared pointer ':objram1' not found
Optional shared pointer ':qsound_ram2' not found
Optional shared pointer ':qsound_ram1' not found
Input: Dropping invalid input token JOYCODE_1_DPADUP
Input: Dropping invalid input token JOYCODE_1_DPADDOWN
Input: Dropping invalid input token JOYCODE_1_DPADLEFT
Input: Dropping invalid input token JOYCODE_1_DPADRIGHT
Sound: overflows=1 underflows=1
« Last Edit: February 23, 2017, 03:33:09 pm by oomek »

oomek

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 268
  • Last login:December 08, 2023, 02:31:38 pm
  • Mame forever.
    • https://github.com/oomek
Re: GroovyMame and FreeSync
« Reply #1 on: February 23, 2017, 11:09:19 pm »
If anyone is wondering how GM is performing with Freesync. I have to tell you, it's awesome. On cheap Samsung F350 27inch (Freesync over HDMI), i5-2500K and R7 260X I get only 5ms of total latency And I do not have to worry about the custom refresh rates.

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: GroovyMame and FreeSync
« Reply #2 on: February 24, 2017, 04:04:09 am »
Is it necessary, unnecessary, mistake or irrelevant for GM to automaticaly adjust Delay scanline: -107 ?
Does it affect the latency in any way when i'm using -nowaitvsync and -nosyncrefresh ?

It won't affect latency or anything, it's just irrelevant information as the frame delay code is bypassed without syncrefresh.

Quote
If anyone is wondering how GM is performing with Freesync. I have to tell you, it's awesome. On cheap Samsung F350 27inch (Freesync over HDMI), i5-2500K and R7 260X I get only 5ms of total latency And I do not have to worry about the custom refresh rates.

5ms is insanely low  :o

Is there any real advantage in using GM versus baseline with a Freesync 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 of pasting it.

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

oomek

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 268
  • Last login:December 08, 2023, 02:31:38 pm
  • Mame forever.
    • https://github.com/oomek
Re: GroovyMame and FreeSync
« Reply #3 on: February 24, 2017, 08:47:16 am »
Did I just see a little decrease in your confidence ;) ?
Well let's take a look at the numbers, shall we?



Source videos:
https://www.dropbox.com/sh/n9liikhscq2ldve/AABr3BcX4x5HGOGKY7eWUDOia?dl=0
« Last Edit: July 21, 2019, 06:17:41 am by oomek »

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: GroovyMame and FreeSync
« Reply #4 on: February 24, 2017, 01:22:31 pm »
Excellent job oomek!

I've been wishing to see a side by side comparison like this since long. The videos are of great quality too.

I'm not fully sure what changes are directly responsible for the latency cut in this case but it is definitely there.

There's a full frame of latency reduction (16 ms) in the D3D case, even with a FreeSync setup, which is generally advertised as "lag-less". An average of 12.5 ms is basically next frame response.

The reduction is not so relevant in the BFGX case (6 ms), where you have 30.3 vs 36.4 (around 2 frames of latency in both cases).
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: GroovyMame and FreeSync
« Reply #5 on: February 24, 2017, 01:24:41 pm »
By the way, I'm on the quest of a 24" FreeSync panel which can be rotated to portrait orientation, IPS if possible.
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

oomek

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 268
  • Last login:December 08, 2023, 02:31:38 pm
  • Mame forever.
    • https://github.com/oomek
Re: GroovyMame and FreeSync
« Reply #6 on: February 24, 2017, 02:41:52 pm »
I'm happy you liked my spreadsheet. I was shocked by the results too. What is more surprising FreeSync is very forgiving in terms of cpu power. My mini ITX board with dual core celeron 847 1.1GHz was only 5ms slower so you still getting the next frame latency.

Regarding the monitor, I don't know what to advise, depends how much you are planning to spend. The cheapest one would be similar to mine but smaller Samsung S24F350 but it doesn't swivel unfortunately.

Besides, i'm in a middle of assembling my first cab and I'm planning to use that monster 27incher. I'm running just 2 custom resolutions, 1600x1080 for horizontal and 1120x1080 or 800x1080 (haven't decided yet) for vertical games (set in vertical.ini) I'm planning to mask unused area of the screen, so it will be like using a 4:3 22" screen. This is the compromise I had to do as there is no 16:10 Freesync equipped lcds on the market. With proper hlsl filters it's looking more than acceptable.
« Last Edit: February 24, 2017, 02:44:03 pm by oomek »

oomek

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 268
  • Last login:December 08, 2023, 02:31:38 pm
  • Mame forever.
    • https://github.com/oomek
Re: GroovyMame and FreeSync
« Reply #7 on: February 24, 2017, 03:09:33 pm »
Btw, is there any particular reason for ignoring keepaspect 0 set in ini and forcing -keepaspect by GM

u-man

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 87
  • Last login:November 29, 2023, 05:57:09 am
  • I want to build my own arcade controls!
Re: GroovyMame and FreeSync
« Reply #8 on: February 26, 2017, 03:47:04 am »
By the way, I'm on the quest of a 24" FreeSync panel which can be rotated to portrait orientation, IPS if possible.

If you really want to buy a FreeSync panel, than my advice is to wait 4-5 month, when the new models come out with 4k resolution and more important HDR.
HDR will be much more close to a real CRT, because of the awesome brightness & contrast levels. Cant wait to see Vector games with that technology. 4k resolution will help to improve the simulation of shadowmasks a lot.

PS: IPS is a lot more expensive and has a little more latency, but has the best viewing angles and color fastness.
"Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd all be running around in darkened rooms, munching magic pills and listening to repetitive electronic music."

oomek

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 268
  • Last login:December 08, 2023, 02:31:38 pm
  • Mame forever.
    • https://github.com/oomek
Re: GroovyMame and FreeSync
« Reply #9 on: February 26, 2017, 04:32:14 am »
HDR makes sense only on OLED panels. Adding HDR will not make automaticaly an IPS panel more contrasty.

u-man

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 87
  • Last login:November 29, 2023, 05:57:09 am
  • I want to build my own arcade controls!
Re: GroovyMame and FreeSync
« Reply #10 on: February 26, 2017, 07:03:27 am »
AMD and Nvidia announced new monitor models (free sync and g-sync) coming out in juni-july 2017. These new models will feature 4k and HDR, what kind of panel it will be, doesnt interest me as long as HDR is fully working, which it will according to both companys.

older link:
http://www.pcworld.com/article/3154782/displays/nvidias-first-hdr-g-sync-monitors-are-basically-the-holy-grail-of-pc-displays.html
"Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd all be running around in darkened rooms, munching magic pills and listening to repetitive electronic music."

B2K24

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 216
  • Last login:May 10, 2023, 09:33:05 pm
Re: GroovyMame and FreeSync
« Reply #11 on: February 27, 2017, 03:25:38 am »
Is it possible to run the latest GroovyMAME with a PC that has a Nvidia GTX 980? I have a G-Sync display and wanted to compare it to baseline MAME.
Upon trying to run a game I get the following:

Code: [Select]
Video chipset is not compatible.
SwitchRes: could not find a video mode that meets your specs

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: GroovyMame and FreeSync
« Reply #12 on: February 27, 2017, 04:10:22 am »
Is it possible to run the latest GroovyMAME with a PC that has a Nvidia GTX 980? I have a G-Sync display and wanted to compare it to baseline MAME.
Upon trying to run a game I get the following:

Code: [Select]
Video chipset is not compatible.
SwitchRes: could not find a video mode that meets your specs

Yes, it's possible. Create the extra required options by running groovymame.exe -cc

Then set "monitor lcd" in the Switchres options block.
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

B2K24

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 216
  • Last login:May 10, 2023, 09:33:05 pm
Re: GroovyMame and FreeSync
« Reply #13 on: February 27, 2017, 10:41:41 am »
Thanks for the help. I put lcd for the monitor but still get presented with the same message. Maybe something's wrong in my mame.ini?

http://pastebin.com/v12fK0ti


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: GroovyMame and FreeSync
« Reply #14 on: February 27, 2017, 11:03:04 am »
Thanks for the help. I put lcd for the monitor but still get presented with the same message. Maybe something's wrong in my mame.ini?

http://pastebin.com/v12fK0ti

The "Video chipset is not compatible." is expected because you're using Nvidia but you can ignore it. However the other message should be gone ("SwitchRes: could not find a video mode that meets your specs").
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

B2K24

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 216
  • Last login:May 10, 2023, 09:33:05 pm
Re: GroovyMame and FreeSync
« Reply #15 on: February 27, 2017, 11:26:31 am »
The switchRes message is still there. I downloaded groovymame64_0183.017b.7z and didn't pick the d3d9ex version is this correct?

Otherwise, I can't figure out why it's throwing the message.


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: GroovyMame and FreeSync
« Reply #16 on: February 27, 2017, 11:30:17 am »
The switchRes message is still there. I downloaded groovymame64_0183.017b.7z and didn't pick the d3d9ex version is this correct?

Otherwise, I can't figure out why it's throwing the message.

Post a log, it must be some silly detail: groovymame romname -v >romname.txt

Either the d3d9ex or the normal one should be the same, although I recommend the d3d9ex if you're on 7 or up for responsiveness.
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

B2K24

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 216
  • Last login:May 10, 2023, 09:33:05 pm
Re: GroovyMame and FreeSync
« Reply #17 on: February 27, 2017, 11:47:10 am »
Thank you. I'll try the other build once we can figure this out. I'm on Windows 10 Pro X64

Here's the log using set sf2ce
http://pastebin.com/12WtsUhW

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: GroovyMame and FreeSync
« Reply #18 on: February 27, 2017, 11:51:30 am »
Ok it's a 144 Hz monitor. Set -lcd_range  50-145

Default "auto" is 59-61, that's why it couldn't find a proper mode. I guess I need to update this option.
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

B2K24

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 216
  • Last login:May 10, 2023, 09:33:05 pm
Re: GroovyMame and FreeSync
« Reply #19 on: February 27, 2017, 11:58:00 am »
That was exactly the problem. Thank you so much!  :)

rock145

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 141
  • Last login:November 07, 2021, 02:05:20 pm
Re: GroovyMame and FreeSync
« Reply #20 on: February 27, 2017, 12:02:40 pm »
By the way, I'm on the quest of a 24" FreeSync panel which can be rotated to portrait orientation, IPS if possible.

If you really want to buy a FreeSync panel, than my advice is to wait 4-5 month, when the new models come out with 4k resolution and more important HDR.
HDR will be much more close to a real CRT, because of the awesome brightness & contrast levels. Cant wait to see Vector games with that technology. 4k resolution will help to improve the simulation of shadowmasks a lot.

PS: IPS is a lot more expensive and has a little more latency, but has the best viewing angles and color fastness.

I have a 4k monitor and I can confirm that Mame games with HLSL at 3840x2160 look much much better than 1080p. The scanlines are more compact and look more natural. Even vertical games that did not look good at 1080p looks much better at 4k.

rock145

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 141
  • Last login:November 07, 2021, 02:05:20 pm
Re: GroovyMame and FreeSync
« Reply #21 on: February 27, 2017, 12:09:38 pm »
I was able to setup groovymame64_0183.017b_d3d9ex with freesync. I do notice is faster than before.
« Last Edit: February 28, 2017, 01:08:59 pm by rock145 »

schmerzkaufen

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 791
  • Last login:October 03, 2023, 02:27:31 pm
  • Multiple Electronic Machine Emulator
Re: GroovyMame and FreeSync
« Reply #22 on: April 18, 2019, 05:50:11 am »
Necro!

Hey oomek could you please reupload that test results pic ?