- --
Viewing Issue Advanced Details
ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
---|---|---|---|---|---|
03597 | Original Reference | Minor | N/A | Dec 24, 2009, 02:07 | Dec 24, 2009, 03:34 |
Tester | Machone | View Status | Public | Platform | |
Assigned To | Tafoid | Resolution | Fixed | OS | |
Status [?] | Resolved | Driver | |||
Version | 0.135u4 | Fixed in Version | 0.136 | Build | |
Fixed in Git Commit | Github Pull Request # | ||||
Summary | 03597: outrun, outrunra, outruno, outrundx, outrunb: Incorrect vsync speed on Outrun | ||||
Description |
Outrun is using the wrong crystal to determine the pixel clock speed. Thanks to Guru's notes in 0.135u4 we can see that vsync should be 60.0543 Hz, whereas MAME is currently at 47 Hz. Needs following line change: MDRV_SCREEN_RAW_PARAMS(MASTER_CLOCK/8, 400, 0, 320, 262, 0, 224) to: MDRV_SCREEN_RAW_PARAMS(MASTER_CLOCK_25MHz/4, 400, 0, 320, 262, 0, 224) to bring it up to 60.0543 Hz (same as Super Hang-on is using). Also, the following line: #define MASTER_CLOCK_25MHz (XTAL_25_1748MHz) /* super hang-on only */ needs to be changed to reflect the fact that Outrun also uses the 25 MHz clock, as noted in Guru's readme as well as http://arcade.ym2149.com/pcb/sega/outrun_video_pcb_partside.jpg (video board pic). |
||||
Steps To Reproduce | |||||
Additional Information | |||||
Github Commit | |||||
Flags | |||||
Regression Version | |||||
Affected Sets / Systems | outrun, outrunra, outruno, outrundx, outrunb | ||||
Attached Files
|
|||||
Relationships
There are no relationship linked to this issue. |
Notes
1
No.05302
Tafoid Administrator
Dec 24, 2009, 03:34
|
The clock readings are close, but not precise due to variations of the osc speeds, but you are correct - when I changed the main cpu, I didn't think to check the video. Thank you. |
---|