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: Games with ISSUES: report here!  (Read 40750 times)

0 Members and 1 Guest are viewing this topic.

haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1135
  • retro maniac
Re: Games with ISSUES: report here!
« Reply #200 on: July 03, 2015, 01:40:34 am »
I didn't like it at the beginning but since every TV/ arcade monitor is cabable of displaying 768x224 it's not a problem.
« Last Edit: July 19, 2015, 04:53:28 am by haynor666 »

donluca

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 122
  • I want to build my own arcade controls!
Re: Games with ISSUES: report here!
« Reply #201 on: November 20, 2015, 03:38:45 pm »
Another issue found: Soul Calibur runs either at half speed when in Interlace mode or twice the speed when in non-interlace mode.

Not sure if this happens in regular MAME as well.

EDIT: the strange thing is that while in attract mode or at the beginning of a round, the speed is correct, only when the round starts the speed goes twice as fast or half.

EDIT 2: ok, it's a bug in MAME, found the bug ticket in their tracker. Nevermind.
« Last Edit: November 20, 2015, 03:56:48 pm by donluca »

stiegi

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 31
  • We learn from experience.
Re: Games with ISSUES: report here!
« Reply #202 on: November 21, 2015, 05:24:09 am »
Hello!

I would like to report an issue about the game pac-man. I am using groovymame .149 with an ati radeon x600. All in all the scrolling is very smooth

but I noticed that in the game pac-man - the character sprites and also the main character sprite which you move in the game has got some kind

of "microstutter" i.e. the movement is not smooth. Does anyone know if the original pac-man has got the same issue? From videos on the internet

I can tell that the characters have got smooth movement. I also noticed this issue in Donkey Kong when you move the main character. It is hard to

describe - the movement of the character is not "sharp and spot on" but in a way blurry and not precise. I can tell the difference in the game pac-

man because there is a pac-man speed up hack - and in this version when pac-man moves faster it is spot on and there is no micro stutter in it.

You can also see this issue in Bagman and SuperBagman - where the motion of the character is not precise.

Does anyone know why this happens - is it caused by input lag that groovy mame cannot exactly sync to the motion of the character?

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 6161
Re: Games with ISSUES: report here!
« Reply #203 on: November 21, 2015, 05:32:23 am »
If a game runs at its native refresh and syncrefresh is enabled it will be as smooth as the pcb was. Please read the first post in this thread and always attach a log to your posts reporting issues.
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

inv

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 18
  • I want to build my own arcade controls!
Re: Games with ISSUES: report here!
« Reply #204 on: February 24, 2016, 07:40:14 am »
Hi!

New to here.

I want to report a save/load state error of GM.

To reproduce this error, start a game, e.g. mslug, save state A in the start point, then advance till encounter a helicopter, beat it.

Then, load state from A, and advance to meet the helicopter, beat it again, and advance a bit, GM will eventually crush.

Other games will suffer from the same error, e.g. kov2 I tested.

I use mame64.exe -cc to create a mame.ini, and not modify it except lcd. I tested on two computers of mine, one had a AMD 7850 and one had a GTX 960, both crushed.


I have no idea why this error will produce, it's not in official mame. Guess it's a save/load route error.

inv

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 18
  • I want to build my own arcade controls!
Re: Games with ISSUES: report here!
« Reply #205 on: February 24, 2016, 08:57:22 pm »
Ok, there is my log file.

monitor: Benq lcd bl2410pt, system: win7 64-bit, video card: MicroStar Nvidia GTX 960, GM version: 0.171

Code: [Select]
SwitchRes: v0.015m, Monitor: lcd, Orientation: horizontal, Modeline generation: enabled
SwitchRes: Using default vfreq range for LCD 59.000000-61.000000
SwitchRes: \\.\DISPLAY1: NVIDIA GeForce GTX 960 (PCI\VEN_10DE&DEV_1401&SUBSYS_32021462&REV_A1)
SwitchRes: Device key: System\CurrentControlSet\Control\Video\{88E3986A-3E01-450B-BF23-C5AA20220357}\0000
Video chipset is not compatible.
Switchres: Searching for custom video modes...
Switchres: [  1]  640x 480 @ 60 : system mode
Switchres: [  2]  640x 480 @ 75 : system mode
Switchres: [  3]  720x 480 @ 60 : system mode
Switchres: [  4]  720x 480 @ 75 : system mode
Switchres: [  5]  720x 576 @ 60 : system mode
Switchres: [  6]  720x 576 @ 75 : system mode
Switchres: [  7]  800x 600 @ 60 : system mode
Switchres: [  8]  800x 600 @ 75 : system mode
Switchres: [  9] 1024x 768 @ 60 : system mode
Switchres: [ 10] 1024x 768 @ 75 : system mode
Switchres: [ 11] 1152x 864 @ 60 : system mode
Switchres: [ 12] 1152x 864 @ 75 : system mode
Switchres: [ 13] 1280x 720 @ 60 : system mode
Switchres: [ 14] 1280x 768 @ 60 : system mode
Switchres: [ 15] 1280x 800 @ 60 : system mode
Switchres: [ 16] 1280x 960 @ 60 : system mode
Switchres: [ 17] 1280x 960 @ 75 : system mode
Switchres: [ 18] 1280x1024 @ 60 : system mode
Switchres: [ 19] 1280x1024 @ 75 : system mode
Switchres: [ 20] 1360x 768 @ 60 : system mode
Switchres: [ 21] 1366x 768 @ 60 : system mode
Switchres: [ 22] 1600x 900 @ 60 : system mode
Switchres: [ 23] 1600x1024 @ 59 : system mode
Switchres: [ 24] 1600x1024 @ 60 : system mode
Switchres: [ 25] 1680x1050 @ 59 : system mode
Switchres: [ 26] 1680x1050 @ 60 : system mode
Switchres: [ 27] 1920x1080 @ 60* : system mode
SwitchRes: Found 0 custom of 27 active video modes
SwitchRes: Creating automatic specs for LCD based on VESA GTF
SwitchRes: Monitor range 65962.00-68198.00,59.00-61.00,0.741,1.157,1.898,0.015,0.045,0.507,0,1,1080,1080,0,0
SwitchRes: -resolution was forced as 1920x1080@60

SwitchRes: Entering switchres_modeline_setup
SwitchRes: v0.015m:[mslug] Calculating best video mode for 320x224@59.185608 orientation: normal

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

SwitchRes: [ 640]x[ 480]_[75=75.000000Hz] - locked

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

SwitchRes: [ 720]x[ 480]_[75=75.000000Hz] - locked

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

SwitchRes: [ 720]x[ 576]_[75=75.000000Hz] - locked

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

SwitchRes: [ 800]x[ 600]_[75=75.000000Hz] - locked

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

SwitchRes: [1024]x[ 768]_[75=75.000000Hz] - locked

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

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

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

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

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

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

SwitchRes: [1280]x[ 960]_[75=75.000000Hz] - locked

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

SwitchRes: [1280]x[1024]_[75=75.000000Hz] - locked

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

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

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

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

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

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

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

SwitchRes: [1920]x[1080]_[60=60.000000Hz]
   rng(0): 1920 x1080_60.000000p 0.000000 [fract] scale(6, 4, 1) diff(0.00, 18.07, 0.8144) ratio(6.000, 4.821)

SwitchRes: [mslug] (1) horizontal (320x224@59.185608)->(1920x1080@60.000000)
   rng(0): 1920 x1080_60.000000p 0.000000 [fract] scale(6, 4, 1) diff(0.00, 18.07, 0.8144) ratio(6.000, 4.821)
SwitchRes: Modeline "1920x1080_60 0.000000KHz 60.000000Hz" 0.000000 1920 0 0 0 1080 0 0 0   -hsync -vsync
SwitchRes: Setting option -rotate
SwitchRes: Setting option -noror
SwitchRes: Setting option -autoror
SwitchRes: Setting option -norol
SwitchRes: Setting option -noautorol
SwitchRes: Setting option -noblack_frame_insertion
SwitchRes: Setting option -nomultithreading
SwitchRes: Setting option -notriplebuffer
SwitchRes: Setting option -syncrefresh
SwitchRes: Setting option -waitvsync
SwitchRes: Setting option -keepaspect
SwitchRes: Setting option -filter
SwitchRes: Setting option -prescale 3
Video: Monitor 000000000864C398 = "\\.\DISPLAY1" (primary)
Direct3D: Using Direct3D 9
window_proc: WM_NCACTIVATE
blit_lock = TRUE
Physical width 1920, height 1080
Direct3D: Configuring adapter #0 = NVIDIA GeForce GTX 960
Direct3D: Adapter has Vendor ID: 10DE and Device ID: 1401
Direct3D: Using dynamic textures
Direct3D: Using StretchRect for prescaling
Direct3D: YUV format = RGB
Direct3D: Max texture size = 16384x16384
Direct3D: Device created at 1920x1080
Direct3D: First scanline: 0, Last scanline: 1079, Break scanline: 1079, Delay scanline: -108
blit_unlock = TRUE
RawInput: APIs detected
Input: Adding Mouse #0: HID-compliant mouse
Input: Adding Gun #0: HID-compliant mouse
Input: Adding Kbd #0: HID Keyboard Device
DirectInput: Using DirectInput 8
window_proc: WM_PAINT
blit_lock = FALSE
window_proc: WM_PAINT:END
stream_buffer_size = 37888
DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channels
Region ':maincpu' created
Region ':fixed' created
Region ':fixedbios' created
Region ':zoomy' created
Region ':mainbios' created
Region ':audiobios' created
Region ':audiocpu' created
Region ':ymsnd' created
Region ':sprites' created
Starting Metal Slug - Super Vehicle-001 ':'
Optional device 'cartslot6' not found
Optional device 'cartslot5' not found
Optional device 'cartslot4' not found
Optional device 'cartslot3' not found
Optional device 'cartslot2' not found
Optional device 'cartslot1' not found
  (missing dependencies; rescheduling)
Starting M68000 ':maincpu'
Starting Z80 ':audiocpu'
Starting Video Screen ':screen'
Optional device 'finder_dummy_tag' not found
Starting palette ':palette'
Starting Neogeo Sprites ':spritegen'
Starting Speaker ':lspeaker'
  (missing dependencies; rescheduling)
Starting Speaker ':rspeaker'
  (missing dependencies; rescheduling)
Starting YM2610 ':ymsnd'
Starting NeoGeo Banked Cartridge ':banked_cart'
Starting uPD4990A RTC ':upd4990a'
Starting NVRAM ':saveram'
Starting NeoGeo Memory Card ':memcard'
Starting NeoGeo Protection (Metal Slug X) ':mslugx_prot'
Starting NeoGeo SMA Cartridge ':sma_prot'
Starting NeoGeo Protection (CMC) ':cmc_prot'
Starting NeoGeo Protection (NEOPCM2) ':pcm2_prot'
Starting NeoGeo Protection (PVC) ':pvc_prot'
Starting NeoGeo Protection (Bootleg) ':bootleg_prot'
Starting NeoGeo Protection (KOF2002) ':kof2002_prot'
Starting NeoGeo Protection (Fatal Fury 2) ':fatfury2_prot'
Starting NeoGeo Protection (KOF98) ':kof98_prot'
Starting NeoGeo Protection (Super Bubble Pop) ':sbp_prot'
Starting Metal Slug - Super Vehicle-001 ':'
Optional device 'cartslot6' not found
Optional device 'cartslot5' not found
Optional device 'cartslot4' not found
Optional device 'cartslot3' not found
Optional device 'cartslot2' not found
Optional device 'cartslot1' not found
  (missing dependencies; rescheduling)
Starting Speaker ':lspeaker'
Starting Speaker ':rspeaker'
Starting Metal Slug - Super Vehicle-001 ':'
Optional device 'cartslot6' not found
Optional device 'cartslot5' not found
Optional device 'cartslot4' not found
Optional device 'cartslot3' not found
Optional device 'cartslot2' not found
Optional device 'cartslot1' not found
Average speed: 101.35% (12 seconds)
window_proc: WM_NCACTIVATE
blit_lock = TRUE
window_proc: WM_DESTROY
blit_lock = TRUE

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 6161
Re: Games with ISSUES: report here!
« Reply #206 on: February 25, 2016, 11:26:25 am »
Ok, there is my log file.

Confirmed here, thanks for reporting.
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

funkycochise

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 101
  • 8 bits generation
Re: Games with ISSUES: report here!
« Reply #207 on: July 18, 2016, 02:48:32 pm »
Hi there,
First I'd like to thank Calamity for his huge work to make groovymame a reality.

I'm posting here because I noticed a strange behavior when running kungfum or spartanx (basically the same game).
Regarding groovymame's job, resolutions/frequency seems to work as it should.
Issues are on the audio part. Sound samples seems to be very low in volume and the music seems to crackle.

Same game, ran on regular mame have a much clear volume/sound track.

I don't believe that the log dump will give any advice. I made it anyway. I've seen lines concerning the audio driver but nothing like any error or so.
If someone could confirm this issue...

Thanks a lot.
FKY

haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1135
  • retro maniac
Re: Games with ISSUES: report here!
« Reply #208 on: July 20, 2016, 09:16:52 am »
You are comparing groovymame 171 vs mame 171 ?

Some time ago discrete sound has been added and cause a serious performance drop that's why on some configurations sound is choppy.

funkycochise

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 101
  • 8 bits generation
Re: Games with ISSUES: report here!
« Reply #209 on: July 20, 2016, 02:44:38 pm »
You are comparing groovymame 171 vs mame 171 ?

Some time ago discrete sound has been added and cause a serious performance drop that's why on some configurations sound is choppy.
Sound issue has nothing to do with performance drop making that caracteristic warped record sound, if it's what you are talking about.
And yes I used 171 version of groovymame and regular mame.
 

haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1135
  • retro maniac
Re: Games with ISSUES: report here!
« Reply #210 on: July 21, 2016, 05:10:22 am »
That might be problem with syncrefresh. A slightly more power is required to run groovymame that regular mame especially when You are using frame_delay option. From time to time I can hear it also on my arcade PC with G3258 4,2 GHz.

Dicrete emulation is really demanding for processor power.

Andypc

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 104
Re: Games with ISSUES: report here!
« Reply #211 on: September 11, 2016, 07:51:35 pm »
I'm having a problem with Golden Tee Fore running to fast in groovymame as if it's not throttled. Everything else is running fine. Any Suggestions. I am using Groovymame 0.171

ArcadeAction

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 49
  • I have built my own arcade controls!
    • ArcadeMade.com
Re: Games with ISSUES: report here!
« Reply #212 on: December 15, 2016, 02:10:36 pm »
When running through Hyperspin, Zookeeper starts and then gets distorted and seemingly errors out and doesn't play. CPS2 also failed to launch.

I was using:
-GroovyMAME versions .172 through .178 I believe with the same result
-CRTEmu_driver 2.0

***Update***
Using GroovyMAME .180 fixes the Zookeeper issue with Hyperspin. CPS2 games are still canceling out after the nag screen. Elevator Action is not launching.
« Last Edit: December 18, 2016, 10:20:07 am by ArcadeAction »

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 6161
Re: Games with ISSUES: report here!
« Reply #213 on: December 19, 2016, 07:02:56 am »
As you see I no longer bother asking for logs. I explored the path of moving posts to a purgatory thread but it involves even more time from my part.
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

ArcadeAction

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 49
  • I have built my own arcade controls!
    • ArcadeMade.com
Re: Games with ISSUES: report here!
« Reply #214 on: December 20, 2016, 06:36:11 pm »
As you see I no longer bother asking for logs. I explored the path of moving posts to a purgatory thread but it involves even more time from my part.

I recently noticed the requirement to post logs along with issues, and will do so with any similar future posts. Thanks

beaches

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 9
  • I want to build my own arcade controls!
Re: Games with ISSUES: report here!
« Reply #215 on: January 20, 2017, 08:21:47 am »
Hello everybody, well I can´t play tetris the grandmaster 2 by groovymame. It appears a blue screen. I can hear the sounds but only a blue screen on my CRT.
¿what´s the problem?
Here it´s the log.  Thanks.

Rom name: tgm2
Videocard: ati radeon X1300
Monitor: pal tv
OS: XP
Groovymame 0.161


Code: [Select]
SwitchRes: v0.015g, Monitor: generic_15, Orientation: horizontal, Modeline generation: enabled
SwitchRes: Monitor range 15625.00-15750.00,49.50-65.00,2.000,4.700,8.000,0.064,0.192,1.024,0,0,192,288,448,576
SwitchRes: \\.\DISPLAY1: Radeon X1300 Series
SwitchRes: DeviceKey: System\CurrentControlSet\Control\Video\{6E5AF182-A75A-4EE8-B9C8-B6E393D0BA61}\0000
Switchres: Searching for custom video modes...
Switchres: [  1]  480x 192 @ 60 : DALDTMCRTBCD480x192x0x60 - Modeline "480x192_60 15.66KHz 60.02Hz" 9.90 480 504 552 632 192 218 221 261   -hsync -vsync
Switchres: [  2]  480x 200 @ 60 : DALDTMCRTBCD480x200x0x60 - Modeline "480x200_60 15.66KHz 60.02Hz" 9.90 480 504 552 632 200 222 225 261   -hsync -vsync
Switchres: [  3]  496x 192 @ 60 : DALDTMCRTBCD496x192x0x60 - Modeline "496x192_60 15.66KHz 60.01Hz" 10.15 496 520 568 648 192 218 221 261   -hsync -vsync
Switchres: [  4]  512x 192 @ 60 : DALDTMCRTBCD512x192x0x60 - Modeline "512x192_60 15.66KHz 60.01Hz" 10.40 512 536 584 664 192 218 221 261   -hsync -vsync
Switchres: [  5]  512x 224 @ 60 : DALDTMCRTBCD512x224x0x60 - Modeline "512x224_60 15.66KHz 59.55Hz" 10.40 512 536 584 664 224 235 238 263   -hsync -vsync
Switchres: [  6]  512x 239 @ 60 : DALDTMCRTBCD512x239x0x60 - Modeline "512x239_60 15.66KHz 60.01Hz" 10.40 512 536 584 664 239 241 244 261   -hsync -vsync
Switchres: [  7]  512x 240 @ 60 : DALDTMCRTBCD512x240x0x60 - Modeline "512x240_60 15.66KHz 60.01Hz" 10.40 512 536 584 664 240 242 245 261   -hsync -vsync
Switchres: [  8]  512x 244 @ 60 : DALDTMCRTBCD512x244x0x60 - Modeline "512x244_60 15.83KHz 59.97Hz" 10.64 512 536 584 672 244 245 248 264   -hsync -vsync
Switchres: [  9]  512x 256 @ 58 : DALDTMCRTBCD512x256x0x58 - Modeline "512x256_58 16.20KHz 58.50Hz" 10.89 512 536 584 672 256 258 261 277   -hsync -vsync
Switchres: [ 10]  512x 448 @ 60 : DALDTMCRTBCD512x448x0x60 - Modeline "512x448_60 15.69KHz 60.01Hz" 10.42 512 536 584 664 448 467 473 523 interlace  -hsync -vsync
Switchres: [ 11]  512x 478 @ 60 : DALDTMCRTBCD512x478x0x60 - Modeline "512x478_60 15.69KHz 60.01Hz" 10.42 512 536 584 664 478 482 488 523 interlace  -hsync -vsync
Switchres: [ 12]  512x 480 @ 60 : DALDTMCRTBCD512x480x0x60 - Modeline "512x480_60 15.68KHz 57.53Hz" 10.41 512 536 584 664 480 494 500 545 interlace  -hsync -vsync
Switchres: [ 13]  512x 512 @ 58 : DALDTMCRTBCD512x512x0x58 - Modeline "512x512_58 16.23KHz 58.50Hz" 10.91 512 536 584 672 512 515 521 555 interlace  -hsync -vsync
Switchres: [ 14]  544x 242 @ 60 : DALDTMCRTBCD544x242x0x60 - Modeline "544x242_60 15.72KHz 59.98Hz" 11.19 544 568 624 712 242 243 246 262   -hsync -vsync
Switchres: [ 15]  640x 200 @ 60 : DALDTMCRTBCD640x200x0x60 - Modeline "640x200_60 15.66KHz 60.00Hz" 13.03 640 664 728 832 200 222 225 261   -hsync -vsync
Switchres: [ 16]  640x 224 @ 60 : DALDTMCRTBCD640x224x0x60 - Modeline "640x224_60 15.65KHz 59.96Hz" 13.02 640 664 728 832 224 234 237 261   -hsync -vsync
Switchres: [ 17]  640x 240 @ 60 : DALDTMCRTBCD640x240x0x60 - Modeline "640x240_60 15.65KHz 59.96Hz" 13.02 640 664 728 832 240 242 245 261   -hsync -vsync
Switchres: [ 18]  640x 244 @ 60 : DALDTMCRTBCD640x244x0x60 - Modeline "640x244_60 15.84KHz 60.00Hz" 13.18 640 664 728 832 244 245 248 264   -hsync -vsync
Switchres: [ 19]  640x 256 @ 58 : DALDTMCRTBCD640x256x0x58 - Modeline "640x256_58 16.20KHz 58.49Hz" 13.74 640 672 736 848 256 258 261 277   -hsync -vsync
Switchres: [ 20]  640x 480 @ 60* : DALDTMCRTBCD640x480x0x60 - Modeline "640x480_60 15.69KHz 59.98Hz" 13.05 640 664 728 832 480 483 489 523 interlace  -hsync -vsync
Switchres: [ 21]  640x 960 @ 60 : system mode
mode_locked
Switchres: [ 22]  664x 496 @ 60 : DALDTMCRTBCD664x496x0x60 - Modeline "664x496_60 16.17KHz 60.00Hz" 14.10 664 696 760 872 496 499 505 539 interlace  -hsync -vsync
Switchres: [ 23]  672x 224 @ 60 : DALDTMCRTBCD672x224x0x60 - Modeline "672x224_60 15.66KHz 60.00Hz" 13.78 672 704 768 880 224 234 237 261   -hsync -vsync
Switchres: [ 24]  720x 480 @ 60 : system mode
mode_locked
Switchres: [ 25]  768x 240 @ 60 : DALDTMCRTBCD768x240x0x60 - Modeline "768x240_60 15.63KHz 59.89Hz" 15.63 768 800 872 1000 240 242 245 261   -hsync -vsync
Switchres: [ 26]  768x 512 @ 58 : DALDTMCRTBCD768x512x0x58 - Modeline "768x512_58 16.23KHz 58.49Hz" 16.36 768 800 880 1008 512 515 521 555 interlace  -hsync -vsync
Switchres: [ 27] 1280x 480 @ 60 : system mode
mode_locked
Switchres: [ 28] 1280x 720 @ 60 : system mode
mode_locked
Switchres: [ 29] 1920x1200 @ 60 : system mode
mode_locked
Switchres: [ 30] 1920x1200 @ 75 : system mode
mode_locked
Switchres: [ 31] 1920x1200 @ 85 : system mode
mode_locked
Switchres: [ 32] 1920x1200 @100 : system mode
mode_locked
Switchres: [ 33] 1920x1440 @ 60 : system mode
mode_locked
Switchres: [ 34] 1920x1440 @ 75 : system mode
mode_locked
Switchres: [ 35] 1920x1440 @ 85 : system mode
mode_locked
Switchres: [ 36] 1920x1440 @ 90 : system mode
mode_locked
Switchres: [ 37] 2048x1536 @ 60 : system mode
mode_locked
Switchres: [ 38] 2048x1536 @ 66 : system mode
mode_locked
Switchres: [ 39] 2048x1536 @ 70 : system mode
mode_locked
Switchres: [ 40] 2048x1536 @ 75 : system mode
mode_locked
Switchres: [ 41] 2048x1536 @ 85 : system mode
mode_locked
SwitchRes: Found 24 custom of 41 active video modes

SwitchRes: Entering switchres_modeline_setup
SwitchRes: v0.015g:[tgm2] Calculating best video mode for 320x240@61.681171 orientation: normal

SwitchRes: [ 480]x[ 192]_(60=60.0153Hz)
   rng(0):  480 x 192_61.681p 15.667 [fract] scale(1, 1, 1) diff(33.33, 0.00, 0.0000) ratio(1.500, 0.800)

SwitchRes: [ 480]x[ 200]_(60=60.0153Hz)
   rng(0):  480 x 200_61.681p 15.667 [fract] scale(1, 1, 1) diff(33.33, 0.00, 0.0000) ratio(1.500, 0.833)

SwitchRes: [ 496]x[ 192]_(60=60.0115Hz)
   rng(0):  496 x 192_61.681p 15.667 [fract] scale(1, 1, 1) diff(35.48, 0.00, 0.0000) ratio(1.550, 0.800)

SwitchRes: [ 512]x[ 192]_(60=60.0077Hz)
   rng(0):  512 x 192_61.681p 15.667 [fract] scale(1, 1, 1) diff(37.50, 0.00, 0.0000) ratio(1.600, 0.800)

SwitchRes: [ 512]x[ 224]_(60=59.5513Hz)
   rng(0):  512 x 224_61.681p 15.667 [fract] scale(1, 1, 1) diff(37.50, 0.00, 0.0000) ratio(1.600, 0.933)

SwitchRes: [ 512]x[ 239]_(60=60.0077Hz)
   rng(0):  512 x 239_60.811p 15.750 [fract] scale(1, 1, 1) diff(37.50, 0.00, -0.8704) ratio(1.600, 0.996)

SwitchRes: [ 512]x[ 240]_(60=60.0077Hz)
   rng(0):  512 x 240_60.577p 15.750 [fract] scale(1, 1, 1) diff(37.50, 0.00, -1.1042) ratio(1.600, 1.000)

SwitchRes: [ 512]x[ 244]_(60=59.9735Hz)
   rng(0):  512 x 244_59.659p 15.750 [fract] scale(1, 1, 1) diff(37.50, 1.14, -2.0221) ratio(1.600, 1.017)

SwitchRes: [ 512]x[ 256]_(58=58.5018Hz)
   rng(0):  512 x 256_57.065p 15.750 [fract] scale(1, 1, 1) diff(37.50, 5.43, -4.6160) ratio(1.600, 1.067)

SwitchRes: [ 512]x[ 448]_(60=60.0076Hz)
   rng(0):  512 x 448_61.681i 15.698 [fract] scale(1, 1, 1) diff(37.50, 81.89, 0.0000) ratio(1.600, 1.867)

SwitchRes: [ 512]x[ 478]_(60=60.0076Hz)
   rng(0):  512 x 478_60.811i 15.780 [fract] scale(1, 1, 1) diff(37.50, 82.24, -0.8704) ratio(1.600, 1.992)

SwitchRes: [ 512]x[ 480]_(60=57.5303Hz)
   rng(0):  512 x 480_60.577i 15.780 [fract] scale(1, 2, 1) diff(37.50, 0.00, -1.1042) ratio(1.600, 2.000)

SwitchRes: [ 512]x[ 512]_(58=58.5045Hz)
   rng(0):  512 x 512_57.065i 15.779 [fract] scale(1, 2, 1) diff(37.50, 5.43, -4.6160) ratio(1.600, 2.133)

SwitchRes: [ 544]x[ 242]_(60=59.9847Hz)
   rng(0):  544 x 242_60.115p 15.750 [fract] scale(1, 1, 1) diff(41.18, 0.38, -1.5667) ratio(1.700, 1.008)

SwitchRes: [ 640]x[ 200]_(60=60.0038Hz)
   rng(0):  640 x 200_61.681p 15.667 [fract] scale(2, 1, 1) diff(0.00, 0.00, 0.0000) ratio(2.000, 0.833)

SwitchRes: [ 640]x[ 224]_(60=59.9579Hz)
   rng(0):  640 x 224_61.681p 15.667 [fract] scale(2, 1, 1) diff(0.00, 0.00, 0.0000) ratio(2.000, 0.933)

SwitchRes: [ 640]x[ 240]_(60=59.9579Hz)
   rng(0):  640 x 240_60.577p 15.750 [integ] scale(2, 1, 1) diff(0.00, 0.00, -1.1042) ratio(2.000, 1.000)

SwitchRes: [ 640]x[ 244]_(60=60.0038Hz)
   rng(0):  640 x 244_59.659p 15.750 [integ] scale(2, 1, 1) diff(0.00, 1.14, -2.0221) ratio(2.000, 1.017)

SwitchRes: [ 640]x[ 256]_(58=58.4910Hz)
   rng(0):  640 x 256_57.065p 15.750 [integ] scale(2, 1, 1) diff(0.00, 5.43, -4.6160) ratio(2.000, 1.067)

SwitchRes: [ 640]x[ 480]_[60=59.9809Hz]
   rng(0):  640 x 480_59.981i 15.685 [integ] scale(2, 2, 1) diff(0.00, 0.00, -1.7003) ratio(2.000, 2.000)

SwitchRes: [ 640]x[ 960]_[60=60.0000Hz] - locked

SwitchRes: [ 664]x[ 496]_(60=59.9963Hz)
   rng(0):  664 x 496_58.769i 15.779 [integ] scale(2, 2, 1) diff(3.61, 2.61, -2.9125) ratio(2.075, 2.067)

SwitchRes: [ 672]x[ 224]_(60=59.9962Hz)
   rng(0):  672 x 224_61.681p 15.667 [fract] scale(2, 1, 1) diff(4.76, 0.00, 0.0000) ratio(2.100, 0.933)

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

SwitchRes: [ 768]x[ 240]_(60=59.8851Hz)
   rng(0):  768 x 240_60.577p 15.750 [fract] scale(2, 1, 1) diff(16.67, 0.00, -1.1042) ratio(2.400, 1.000)

SwitchRes: [ 768]x[ 512]_(58=58.4865Hz)
   rng(0):  768 x 512_57.065i 15.779 [fract] scale(2, 2, 1) diff(16.67, 5.43, -4.6160) ratio(2.400, 2.133)

SwitchRes: [1280]x[ 480]_[60=60.0000Hz] - locked

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

SwitchRes: [1920]x[1200]_[60=60.0000Hz] - locked

SwitchRes: [1920]x[1200]_[75=75.0000Hz] - locked

SwitchRes: [1920]x[1200]_[85=85.0000Hz] - locked

SwitchRes: [1920]x[1200]_[100=100.0000Hz] - locked

SwitchRes: [1920]x[1440]_[60=60.0000Hz] - locked

SwitchRes: [1920]x[1440]_[75=75.0000Hz] - locked

SwitchRes: [1920]x[1440]_[85=85.0000Hz] - locked

SwitchRes: [1920]x[1440]_[90=90.0000Hz] - locked

SwitchRes: [2048]x[1536]_[60=60.0000Hz] - locked

SwitchRes: [2048]x[1536]_[66=66.0000Hz] - locked

SwitchRes: [2048]x[1536]_[70=70.0000Hz] - locked

SwitchRes: [2048]x[1536]_[75=75.0000Hz] - locked

SwitchRes: [2048]x[1536]_[85=85.0000Hz] - locked

SwitchRes: [tgm2] (1) horizontal (320x240@61.68)->(640x240@60.58)
   rng(0):  640 x 240_60.577p 15.750 [integ] scale(2, 1, 1) diff(0.00, 0.00, -1.1042) ratio(2.000, 1.000)
SwitchRes: Modeline "640x240_60 15.75KHz 60.58Hz" 13.10 640 664 728 832 240 241 244 260   -hsync -vsync
Switchres: saving    DALDTMCRTBCD640x240x0x60 - Modeline "640x240_60 15.65KHz 59.96Hz" 13.02 640 664 728 832 240 242 245 261   -hsync -vsync
Switchres: updating  DALDTMCRTBCD640x240x0x60 - Modeline "640x240_60 15.75KHz 60.58Hz" 13.10 640 664 728 832 240 241 244 260   -hsync -vsync
SwitchRes: Setting option -rotate
SwitchRes: Setting option -noror
SwitchRes: Setting option -autoror
SwitchRes: Setting option -norol
SwitchRes: Setting option -noautorol
SwitchRes: Setting option -noblack_frame_insertion
SwitchRes: Setting option -nomultithreading
SwitchRes: Setting option -notriplebuffer
SwitchRes: Setting option -syncrefresh
SwitchRes: Setting option -waitvsync
SwitchRes: Setting option -nohwstretch
SwitchRes: Setting option -keepaspect
SwitchRes: Setting option -nofilter
SwitchRes: Setting option -prescale 1
Video: Monitor 002581E4 = "\\.\DISPLAY1" (primary)
Direct3D: Using Direct3D 9
window_proc: WM_NCACTIVATE
blit_lock = TRUE
Direct3D: Configuring adapter #0 = Radeon X1300 Series
Direct3D: Using dynamic textures
Direct3D: YUV format = UYVY
Direct3D: Max texture size = 4096x4096
Direct3D: Device created at 640x240
blit_unlock = TRUE
RawInput: APIs detected
Input: Adding Mouse #0: Mouse compatible con HID
Input: Adding Gun #0: Mouse compatible con HID
Input: Adding Mouse #1: Mouse compatible con HID
Input: Adding Gun #1: Mouse compatible con HID
Input: Adding Kbd #0: Teclado estándar de 101/102 teclas o Microsoft Natural PS/2 Keyboard
Input: Adding Kbd #1: Dispositivo de teclado HID
Input: Adding Kbd #2: Dispositivo de teclado HID
Input: Adding Kbd #3: Dispositivo de teclado HID
DirectInput: Using DirectInput 8
window_proc: WM_PAINT
blit_lock = FALSE
window_proc: WM_PAINT:END
stream_buffer_size = 37888
DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channels
Region ':maincpu' created
Region ':gfx1' created
Region ':ymf' created
Region ':eeprom' created
Starting Tetris the Absolute The Grand Master 2 ':'
  (missing dependencies; rescheduling)
Starting SH-2 ':maincpu'
Starting Serial EEPROM 93C56 (256x8) ':eeprom'
Starting Buffered Sprite RAM ':spriteram'
Starting Video Screen ':screen'
Optional device 'finder_dummy_tag' not found
Starting gfxdecode ':gfxdecode'
Starting palette ':palette'
Starting Speaker ':lspeaker'
  (missing dependencies; rescheduling)
Starting Speaker ':rspeaker'
  (missing dependencies; rescheduling)
Starting YMF278B ':ymf'
Starting Tetris the Absolute The Grand Master 2 ':'
  (missing dependencies; rescheduling)
Starting Speaker ':lspeaker'
Starting Speaker ':rspeaker'
Starting Tetris the Absolute The Grand Master 2 ':'
Loading data from EEPROM region ':eeprom'
Average speed: 98.33% (170 seconds)
Switchres: restoring DALDTMCRTBCD640x240x0x60 - Modeline "640x240_60 15.65KHz 59.96Hz" 13.02 640 664 728 832 240 242 245 261   -hsync -vsync
Sound: buffer overflows=6 underflows=0
window_proc: WM_NCACTIVATE
blit_lock = TRUE
window_proc: WM_DESTROY
blit_lock = TRUE
.
« Last Edit: January 20, 2017, 11:32:41 am by beaches »

beaches

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 9
  • I want to build my own arcade controls!
Re: Games with ISSUES: report here!
« Reply #216 on: January 22, 2017, 05:42:27 pm »
Done : I have made a tgm2.ini file with resolution 320x240 and now works properly. Thanks

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 6161
Re: Games with ISSUES: report here!
« Reply #217 on: January 23, 2017, 03:42:51 pm »
Done : I have made a tgm2.ini file with resolution 320x240 and now works properly. Thanks

The blue screen on your TV probably means it doesn't accept the input frequency. This would make sense because tmg2 is outputting 61 Hz (beyond NTSC). However, if forcing 320x240 fixes the issue, then I must be missing something.

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

SpaceGod

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 39
  • I want to build my own arcade controls!
Re: Games with ISSUES: report here!
« Reply #218 on: February 26, 2017, 05:47:08 pm »
im having problems with win10 crtemudriver 12.6.1(hd6970) with tekken 3 with 15khz pvm. the game runs super slow and it doesn't run slow on linux using my lcd.

donluca

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 122
  • I want to build my own arcade controls!
Re: Games with ISSUES: report here!
« Reply #219 on: March 21, 2017, 01:34:30 pm »
Albeit not an issue specifically with GroovyMAME, does anyone know what's the state of emulation for wait states on CPS1 and CPS2 hardware?

big10p

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 658
  • Mmmm, arcade classics!
Re: Games with ISSUES: report here!
« Reply #220 on: May 07, 2017, 09:58:49 am »
I'm getting a weird error with GM 0.183 and Salamander 2. The game works OK with mainline MAME 0.183 on my PC, but with GM in my cab, one of the ROMs fails the boot test as BAD, and the machine reboots and repeats. I copied the romset from PC to cab, so they are identical.

EDIT: It's sorted now. I had an NVRAM save that was from an older version of GM. Deleteted it, and now it's working.
« Last Edit: May 07, 2017, 03:32:34 pm by big10p »

SPARTAN-122

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 19
  • Joseph-122
Hi All, hope everything is well with you.  I am running GroovyMAME 0.157 and I'm having a weird issue with how Scramble and Super Cobra's shots look. The display I use for these games is a 15KHz 20" Trinitron 600 line PVM flipped on it's side (in vertical/tate/portrait orientation). The video/audio and joystick input are all running smoothly and synchronizing fine.  Also the "bombs" drop and look normal and the player's ship animation is fine on both as well. However when you press the fire button they are both shooting yellow vertical bars out in front that look like this --> | | |  <-- instead of the usual small dots ...

(see "Scramble_wierd_shots.jpg" for reference)

If I run "standard" 64-bit MAME 0.157 on the same exact partition/mame dir with it's own "-cc generated" mame.ini and use the CLI settings recommended by Ultimarc (using AVGA 5000, a modded ati 5450-1GB and Win 7 64-bit drivers from the CD that ships with card) the fire for the Scramble jet (and the Super Cobra helicopter) look the way it's supposed to.

(see "Scramble_normal_shots.jpg" for reference)


Anyone possibly know why the players shots appear on the screen so differently in groovymame than in regular mame64? Just very curious about it, otherwise the games play fine.  Thanks in advance!

Joseph-122




« Last Edit: September 04, 2017, 09:11:28 pm by SPARTAN-122 »

SPARTAN-122

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 19
  • Joseph-122
Re: Games with ISSUES: report here!
« Reply #222 on: August 28, 2017, 05:19:49 pm »
Here is the screenshot with the normal looking shots in mainline 64-bit MAME 0.157

Command Prompt (Ultimarc recommended) command used for reference in mainline MAME:

"mame64 scramble -video ddraw -switchres -nohwstretch -nothrottle -triplebuffer -nomt"
« Last Edit: August 29, 2017, 01:11:01 pm by SPARTAN-122 »

nexus6

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 245
    • LowRez Retroshirts
Airbuster (stuttered scrolling)
« Reply #223 on: October 03, 2017, 11:34:40 am »
Airbuster has a stuttered scrolling at my configuration.
I'm using a multisyncmonitor and win7 with an ATI HD5450. Can it be a problem, because Gunbuster runs native with 57.4 Hz?

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 6161
Re: Airbuster (stuttered scrolling)
« Reply #224 on: October 18, 2017, 03:46:34 am »
Airbuster has a stuttered scrolling at my configuration.
I'm using a multisyncmonitor and win7 with an ATI HD5450. Can it be a problem, because Gunbuster runs native with 57.4 Hz?

Your card is HD4xxx, not HD5xxx. You must run GM with administrators rights when using pre-HD5xxx cards in W7.
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: 6161
Anyone possibly know why the players shots appear on the screen so differently in groovymame than in regular mame64? Just very curious about it, otherwise the games play fine.  Thanks in advance!

Sorry for the late answer. The reason is the "frogger/galaxian" patch that was included in previous versions of GM. Modern versions won't show the problem.
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

DaddyLongLegs

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 212
Re: Games with ISSUES: report here!
« Reply #226 on: December 15, 2017, 08:06:22 am »
I don't see anyone else complaining about Carnevil online, so my guess it's somehow groovyMAME related, but the game runs way, way too fast. It's so fast that even the audio is high pitched. I noticed the same issue with the Golden Tee games during FMV cutscenes.

I was just wondering if there were any way to fix this.

Sledge

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 455
Re: Games with ISSUES: report here!
« Reply #227 on: December 20, 2017, 02:58:18 am »
I don't see anyone else complaining about Carnevil online, so my guess it's somehow groovyMAME related, but the game runs way, way too fast. It's so fast that even the audio is high pitched. I noticed the same issue with the Golden Tee games during FMV cutscenes.

I was just wondering if there were any way to fix this.
Quote
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.

funkycochise

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 101
  • 8 bits generation
Re: Games with ISSUES: report here!
« Reply #228 on: January 28, 2018, 03:56:09 am »
PUNISHER - CAPCOM

Hi,
yesterday I tried to play punisher using groovymame 0193 version.
I must specify that I only played with player 1.
When reached some points in the game, the game went crazy, hearing a audio fast forward and a video switching to window and minimize, forcing to exit mame and switch back to 640x480
I also tried version 191 and 192 with same results. Only playing with player 2, at least juste a while seems to avoid the problem to occur.
stock mame 0.193 also shows that something happens (flash on screen) but it doesn't force to exit and allow to proceed playing.

It's quite simple to reproduce, just go to first boss and start to launch bomb (jump then B1+B2), the glitch should occur.

As I'm not sure if it's a mame issue or a groovy consequence, I submit here for opinion.
log file doesn't appear to show anything, but I provide it.
Windows 7, HD5450, d3dex groovymame.

regards.


anchounio

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 66
  • I want to build my own arcade controls!
Re: Games with ISSUES: report here!
« Reply #229 on: September 04, 2018, 07:00:58 am »
I don't see anyone else complaining about Carnevil online, so my guess it's somehow groovyMAME related, but the game runs way, way too fast. It's so fast that even the audio is high pitched. 

I was just wondering if there were any way to fix this.

I have the same problem with Carnevil... or similar
The gameplay speed seems fine, but the audio sounds high pitched.
I still can't post the log file because I don't have my arcade cabinet here, but I can share the whole information of my drivers, video card... and also share a video here of the issue.

I've attached the file carnevil.txt with information of my system.
Here's a video of the issue:

https://youtu.be/8x05TnYyVNk


UPDATE: I've attached the log of the game (carnevil2.txt) !!!
             I have named it as carnevil2.txt  because I already attached a file called carnevil.txt with my system specs.

carnevil.txt = my system specs
carnevil2.txt = the log file of the game created with mame - v

« Last Edit: September 14, 2018, 03:44:01 am by anchounio »

anchounio

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 66
  • I want to build my own arcade controls!
Re: Games with ISSUES: report here!
« Reply #230 on: September 14, 2018, 04:22:40 am »
Uptaded my previous post :)

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 6161
Re: Games with ISSUES: report here!
« Reply #231 on: September 14, 2018, 05:35:43 am »
For Carnevil, create a specific ini and set:

Code: [Select]
autosync 0
triplebuffer 1

Default syncrefresh configuration breaks this driver.
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

anchounio

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 66
  • I want to build my own arcade controls!
Re: Games with ISSUES: report here!
« Reply #232 on: September 15, 2018, 06:15:26 am »
For Carnevil, create a specific ini and set:

Code: [Select]
autosync 0
triplebuffer 1

Default syncrefresh configuration breaks this driver.

Thanks man !   
Could it have any relationship with this issue of the game emulation?
https://mametesters.org/view.php?id=7093

schmerzkaufen

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 206
  • I want a large cream coffee
Re: Games with ISSUES: report here!
« Reply #233 on: October 29, 2018, 06:01:13 am »
Sorry if they were mentioned somewhere but I couldn't find the following reported;

Are Nebulas Ray and STV games known to cause issues with frame_delay ? I'm seeing drops in perfomance no matter the setting even @1, but they're fine on plain d3d9ex when f_d is off.

Doubt my i5-4690k would be a bottleneck , but possibly my R7 260X is too weak... or it could be something else entirely.

I'll post a couple logs later today anyway.

EDIT: probably false alarm for STV, it's just that my pc insn't strong enough to push more than f_d 2 with that system, logs with fd_0 and fd_3 attached, but 2 is fine as far as I've seen.
For nebulasray though I'm not sure power is the problem, just fd_1 without even any vsync offset crushes it, logs attached too.
« Last Edit: October 29, 2018, 08:38:47 am by schmerzkaufen »

folken

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 45
  • I want to build my own arcade controls!
Re: Games with ISSUES: report here!
« Reply #234 on: October 30, 2018, 02:15:45 am »
I don't understand why Mame team does not ensure that all NEOGEO MVS, CPS 1, 2 and 3 games and 90's games work perfectly before emulating other systems...??? I'm thinking about background bug in MOTW Terry's 3rd stage for exemple...
« Last Edit: October 30, 2018, 02:18:01 am by folken »

schmerzkaufen

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 206
  • I want a large cream coffee
Re: Games with ISSUES: report here!
« Reply #235 on: October 30, 2018, 04:28:58 am »
EDIT: probably false alarm for STV, it's just that my pc insn't strong enough to push more than f_d 2 with that system, logs with fd_0 and fd_3 attached, but 2 is fine as far as I've seen.
For nebulasray though I'm not sure power is the problem, just fd_1 without even any vsync offset crushes it, logs attached too.

Scratch what I wrote yesterday, it seems that rather than issues with frame_delay, it's just that a bunch of the more demanding systems can't work at a stable full speed even with only f_d 1 because my R7 260X processing is significantly weaker than my CPU anyway.

Correct me if I'm wrong, but that means when frame_delay is off most of the workload is for the CPU as in 'normal' MAME, and when it's on it switches to the GPU ?

EDIT: of course for those more demanding systems I still have d3d9ex minimizing the greatest portion of unwanted lag so no big deal, they all work flawlesssy with it. I wonder though what magnitude of GPU might is required to use some levels of frame_delay with even those heavier ones (STV, gnet, playstation hardware, etc)
« Last Edit: October 30, 2018, 04:37:35 am by schmerzkaufen »

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 6161
Re: Games with ISSUES: report here!
« Reply #236 on: October 30, 2018, 04:40:53 am »
Correct me if I'm wrong, but that means when frame_delay is off most of the workload is for the CPU as in 'normal' MAME, and when it's on it switches to the GPU ?

Not exactly, but somewhat true. Frame delay still requires a big, even higher stress for the CPU. But for frame delay to work well it's also critical the time it takes for the GPU to render a frame, while this is secondary without frame delay.

Try this: instead of having your desktop rotated as you have it now, set the orientation back to landscape (even if your monitor is rotated vertically, mind your neck). Then run groovymame with the -orientation rotate_r or -orientation rotate_l options.

I seem to remind someone reporting that a rotated desktop setup caused poor performance.
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

schmerzkaufen

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 206
  • I want a large cream coffee
Re: Games with ISSUES: report here!
« Reply #237 on: October 30, 2018, 05:31:51 am »
Not exactly, but somewhat true. Frame delay still requires a big, even higher stress for the CPU. But for frame delay to work well it's also critical the time it takes for the GPU to render a frame, while this is secondary without frame delay.
I see.
Try this: instead of having your desktop rotated as you have it now, set the orientation back to landscape (even if your monitor is rotated vertically, mind your neck). Then run groovymame with the -orientation rotate_r or -orientation rotate_l options.

I seem to remind someone reporting that a rotated desktop setup caused poor performance.
Just tried that and I must say it only made a very subtle difference, a small gain in stability, but the games still crawl in places with even just f_d 1.

Later as I've planned I will retry a number of things with my GTX 750 Ti (which I seem to recall allowed me to push many games to f_d 7~8, while the R7 260X is more 5~6 tier on average.
Also I've just found a brand new R7 360 (unused but refurbished b/c of damaged package ) which is only a refreshed/boosted/rebranded plain 260 but it comes with OC'ing potential.

Not like benchmarking GPUs for frame_delay on flat panels will build a reference database, but it's somewhat interesting for realizing that sort of behaviour I'm experiencing here is not a bug or something like that, rather it's only showing where the ceiling is for one's hardware in that kind of configuration.

Paradroid

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 611
    • SCART Hunter
Re: Games with ISSUES: report here!
« Reply #238 on: October 30, 2018, 03:10:59 pm »
I don't understand why Mame team does not ensure that all NEOGEO MVS, CPS 1, 2 and 3 games and 90's games work perfectly before emulating other systems...???

That's a little bit like saying "shouldn't we make sure nobody lives in poverty before we explore outer space?"

The world (and MAME) don't work that way...
My MAME/SCART/CRT blog: SCART Hunter

Recapnation

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 119
    • Eiusdemmodi
Re: Games with ISSUES: report here!
« Reply #239 on: November 01, 2018, 06:13:10 am »
Seems they are taking rewards lately for "issues" submitted through Bounty Source:

https://www.bountysource.com/teams/mamedev

So if they need the motivation (and they obviously do -- the aforementioned Garou glitch, for instance, makes of MAME the only NG emulator which doesn't run this game properly after all these years), there's that now. Hopefully this gets at least as popular as Retro Arch's Patreon and we can see some progress on drivers which seem to be long forgotten because they're "good enough" (and the devs start getting some well-deserved money in return).

  
 

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