Author Topic: Ok me noob (Read 15195 times)

James33 · « **on:** January 18, 2005, 07:42:09 AM »

Going by this

Quote

On a side note I can report there is also an error in the NeoGeo driver. The Vblank rate is not 60hz
as someone read it to be. The driver was more accurate before that change was made. The correct vblank
speed is 59.1856 as confirmed on real hardware via test code (MV-1F). There are 264 scanlines (visable
area is scanlines 24 to 248) and hsync is 15625 Hz. Anyone who thinks this is wrong can try kof98
attract mode at both speeds, its clear to see music/graphics sync at 59.1856hz but not at 60hz. I have
also done side by side tests, using 60hz causes games that are timmed off vblank to run out of sync.

What I like to know is how I can change it back to 59HZ I am not 100% sure what to change ?

iq_132 · « **Reply #1 on:** January 18, 2005, 09:01:09 AM »

In drivers/neogeo.c

Change this:

Code: [Select]


	/* using a framerate of 59 will fix the sync of the kof98 video / sound however
	   using it would be a kludge as 60 has been measured using the hardware */
	MDRV_FRAMES_PER_SECOND(60) /* verified */
	MDRV_VBLANK_DURATION(DEFAULT_60HZ_VBLANK_DURATION)

James33 · « **Reply #2 on:** January 18, 2005, 09:14:36 AM »

I did that before but mame would not compile . This is why I posted here

Do I change both or just the MDRV_VBLANK_DURATION line ?

robber804 · « **Reply #3 on:** January 21, 2005, 06:27:40 AM »

Quote from: James33

I did that before but mame would not compile . This is why I posted here

Do I change both or just the MDRV_VBLANK_DURATION line ?

This is the most accurate i have found

MDRV_FRAMES_PER_SECOND(59.1856)
MDRV_VBLANK_DURATION(DEFAULT_REAL_60HZ_VBLANK_DURATION)

Worked fine for me and fixes many sync issues in the intro's.

X-or · « **Reply #4 on:** January 21, 2005, 08:44:07 PM »

Quote from: robber804

This is the most accurate i have found

MDRV_FRAMES_PER_SECOND(59.1856)

the most accurate value is 15625/246

James33 · « **Reply #5 on:** January 21, 2005, 11:20:32 PM »

I am getting confused now lol .

X-or · « **Reply #6 on:** January 22, 2005, 01:00:53 AM »

Quote from: James33

I am getting confused now lol .

compile with
MDRV_FRAMES_PER_SECOND(15625/246)

babytek · « **Reply #7 on:** January 22, 2005, 10:41:30 AM »

Quote from: X-or

compile with
MDRV_FRAMES_PER_SECOND(15625/246)

Done but fps is now 63 ... is it normal ?

wit 59.1856 frame per second are 59

what's the good one ?

iq_132 · « **Reply #8 on:** January 22, 2005, 12:44:34 PM »

I think the fraction would be better as 36991/625

X-or · « **Reply #9 on:** January 22, 2005, 02:08:37 PM »

ooops sorry my mistake!!

not 246 but 264, this is a typo sorry again

Quote from: Razoola

There are 264 scanlines (visable
area is scanlines 24 to 248) and hsync is 15625 Hz.

so the framerate is 15625/264 = (approximatively 59.1856)

babytek · « **Reply #10 on:** January 22, 2005, 02:18:25 PM »

OK

i'll try

James33 · « **Reply #11 on:** January 23, 2005, 04:55:42 AM »