Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
02676 Color/Palette Major Always Nov 24, 2008, 22:06 Jan 2, 2009, 16:58
Tester Layne View Status Public Platform MAME (Official Binary)
Assigned To aaron Resolution Fixed OS Windows XP/Vista 32-bit
Status [?] Resolved Driver
Version 0.128u4 Fixed in Version 0.129 Build Normal
Fixed in Git Commit Github Pull Request #
Summary 02676: All Laserdisc Games: Wrong colors using Direct3D on ATI cards.
Description I noticed strange colors on laserdiscs that I tried, Cube Quest and FireFox. The colors that appears on my screen are different than the ones I see in all videos on youtube and in general than those in circulation.

Let me explain better, in Cube Quest for example the intro text and SIMUTREK word are BLUE, not RED as they should be, I see the star into the attract mode PURPLE and not RED as it should be, and so on, all colors are totally altered. It happens the same in FireFox, the title of the game should be ORANGE-RED, I see it GREEN WATER, and colors of the sky and sea are completely different.

Pressing F12 generates snaps with right colors and not with ones I can see on screen, for example word Simutrek on snap is red while I'm seeing it blue on the screen! The only way to prove it is to photograph the screen completely. Under the snaps of what I see on the screen and what I have pressing F12.

Haze helped in solving the question, it seems a problem related to ATI cards series 9xxx. I have a Radeon 9800 Pro AGP 128MB, and another user from MAMEItalia has the same problem with a similar ATI card. With ddraw mode colors are right.
Steps To Reproduce
Additional Information
Github Commit
Flags
Regression Version
Affected Sets / Systems All Laserdisc Games
Attached Files
jpg file icon Wrong Simutrek.jpg (146,691 bytes) Nov 24, 2008, 22:11
jpg file icon Wrong Star.jpg (125,453 bytes) Nov 24, 2008, 22:12
png file icon Right Simutrek MAME F12.png (422,266 bytes) Nov 24, 2008, 22:14
png file icon Right Star MAME F12.png (614,301 bytes) Nov 24, 2008, 22:14
Relationships
There are no relationship linked to this issue.
Notes
17
User avatar
No.03117
Tafoid
Administrator
Nov 25, 2008, 00:30
I'll leave this for the Devs to discuss. I'm of the opinion since it's unique hardware which doesn't act correctly under certain conditions - it probably shouldn't be labeled a bug in MAME - rather a bug in the ATI driver.
User avatar
No.03118
Fujix
Administrator
Nov 25, 2008, 03:17
Correct work on my GeForce graphic board.

Does any ATI user confirm the issue?
User avatar
No.03120
aaron
Developer
Nov 25, 2008, 05:31
Please run with -verbose and paste the results here.
User avatar
No.03121
Layne
Tester
Nov 25, 2008, 09:10
Generated using Fire Fox (set 1):

F:\>mame.exe -verbose
Video: Monitor 00010001 = "\\.\DISPLAY1" (primary)
Direct3D: Using Direct3D 9
Direct3D: Configuring adapter #0 = RADEON 9800 PRO
Direct3D: Using dynamic textures
Direct3D: YUV format = UYVY
Direct3D: Device created at 1280x1024
Direct3D: Max texture size = 2048x2048
DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channels
RawInput: APIs detected
Input: Adding Mouse #1: \??\HID#Vid_04f2&Pid_0210&MI_02#7&1bc339cd&0&0000#{378de
44c-56ef-11d1-bc8c-00a0c91405dd}
Input: Adding Gun #1: \??\HID#Vid_04f2&Pid_0210&MI_02#7&1bc339cd&0&0000#{378de44
c-56ef-11d1-bc8c-00a0c91405dd}
Input: Adding Kbd #1: \??\HID#Vid_04f2&Pid_0210&MI_00#7&27d6eb4a&0&0000#{884b96c
3-56ef-11d1-bc8c-00a0c91405dd}
DirectInput: Using DirectInput 7
Video: Monitor 00010001 = "\\.\DISPLAY1" (primary)
Direct3D: Using Direct3D 9
Direct3D: Configuring adapter #0 = RADEON 9800 PRO
Direct3D: Using dynamic textures
Direct3D: YUV format = UYVY
Direct3D: Device created at 1280x1024
Direct3D: Max texture size = 2048x2048
DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channels
RawInput: APIs detected
Input: Adding Mouse #1: \??\HID#Vid_04f2&Pid_0210&MI_02#7&1bc339cd&0&0000#{378de
44c-56ef-11d1-bc8c-00a0c91405dd}
Input: Adding Gun #1: \??\HID#Vid_04f2&Pid_0210&MI_02#7&1bc339cd&0&0000#{378de44
c-56ef-11d1-bc8c-00a0c91405dd}
Input: Adding Kbd #1: \??\HID#Vid_04f2&Pid_0210&MI_00#7&27d6eb4a&0&0000#{884b96c
3-56ef-11d1-bc8c-00a0c91405dd}
DirectInput: Using DirectInput 7
Average speed: 98.91% (111 seconds)
Sound: buffer overflows=15 underflows=0
No.03122
user457
Nov 25, 2008, 13:00
I have the same problem using the ArcadeVGA2 PCIe...
User avatar
No.03140
john_iv
Senior Tester
Nov 27, 2008, 08:48
Datapoint: This is no-repro on ATI hardware at the 4850 level in Vista64. My output matches my other machine's NVIDIA 8800GTS [G92].
User avatar
No.03145
Fujix
Administrator
Nov 28, 2008, 09:06
Is this the cause?
Direct3D: YUV format = UYVY
It's "RGB" here.
User avatar
No.03220
aaron
Developer
Dec 4, 2008, 10:02
Can't verify it myself, but I think I fixed it for u5.
User avatar
No.03243
Layne
Tester
Dec 7, 2008, 11:19
Sorry but colors bug is still present in 0.128u5, I've just tested it.
User avatar
No.03247
robiza
Developer
Dec 7, 2008, 13:16
Please run with -verbose and paste the results here
User avatar
No.03248
Layne
Tester
Dec 7, 2008, 13:59
Still using Fire Fox (set 1):

F:\>mame.exe -verbose
Video: Monitor 00010001 = "\\.\DISPLAY1" (primary)
Direct3D: Using Direct3D 9
Direct3D: Configuring adapter #0 = RADEON 9800 PRO
Direct3D: Using dynamic textures
Direct3D: YUV format = UYVY
Direct3D: Device created at 1280x1024
Direct3D: Max texture size = 2048x2048
DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channels
RawInput: APIs detected
Input: Adding Mouse #1: \??\HID#Vid_04f2&Pid_0210&MI_02#7&1bc339cd&0&0000#{378de
44c-56ef-11d1-bc8c-00a0c91405dd}
Input: Adding Gun #1: \??\HID#Vid_04f2&Pid_0210&MI_02#7&1bc339cd&0&0000#{378de44
c-56ef-11d1-bc8c-00a0c91405dd}
Input: Adding Kbd #1: \??\HID#Vid_04f2&Pid_0210&MI_00#7&27d6eb4a&0&0000#{884b96c
3-56ef-11d1-bc8c-00a0c91405dd}
DirectInput: Using DirectInput 7
Video: Monitor 00010001 = "\\.\DISPLAY1" (primary)
Direct3D: Using Direct3D 9
Direct3D: Configuring adapter #0 = RADEON 9800 PRO
Direct3D: Using dynamic textures
Direct3D: YUV format = UYVY
Direct3D: Device created at 1280x1024
Direct3D: Max texture size = 2048x2048
DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channels
RawInput: APIs detected
Input: Adding Mouse #1: \??\HID#Vid_04f2&Pid_0210&MI_02#7&1bc339cd&0&0000#{378de
44c-56ef-11d1-bc8c-00a0c91405dd}
Input: Adding Gun #1: \??\HID#Vid_04f2&Pid_0210&MI_02#7&1bc339cd&0&0000#{378de44
c-56ef-11d1-bc8c-00a0c91405dd}
Input: Adding Kbd #1: \??\HID#Vid_04f2&Pid_0210&MI_00#7&27d6eb4a&0&0000#{884b96c
3-56ef-11d1-bc8c-00a0c91405dd}
DirectInput: Using DirectInput 7
Average speed: 87.25% (133 seconds)
Sound: buffer overflows=136 underflows=0
User avatar
No.03455
aaron
Developer
Jan 1, 2009, 21:44
edited on: Jan 1, 2009, 21:45
Ok, pretty sure I got it this time.

Can someone with a repro of the problem try this binary:
http://aarongiles.com/test/mame-atitest.zip

(Note that the direct link won't work, you'll have to copy/paste the URL into your browser.)

Let me know if it fixes the problem for you.
User avatar
No.03456
Layne
Tester
Jan 1, 2009, 22:25
edited on: Jan 1, 2009, 22:29
Yes, now colors are fixed :-) Thank you Aaron!!

But sometimes I receive this message launching cubequest, mame crash with this error:

F:\>mame.exe

-----------------------------------------------------
Exception at EIP=0094583D: ACCESS VIOLATION
While attempting to read memory at 04FE7088
-----------------------------------------------------
EAX=00008400 EBX=00000046 ECX=00008400 EDX=04FC6088
ESI=00000000 EDI=00000000 EBP=0022F998 ESP=0022F950
User avatar
No.03464
aaron
Developer
Jan 2, 2009, 03:56
Hmmm, I can't repro the crash. How often does it happen? Every time you run? Does it change based on window mode versus full-screen mode?
User avatar
No.03478
Layne
Tester
Jan 2, 2009, 10:24
It happens with cubequest only at first 3-4 launch, then it starts normally. nvram file is not created in consecutive crash. When nvram is created crash no more happens. Nothing changes on window mode versus full-screen mode. If i can run some specific command to help you please let me know.
User avatar
No.03480
RansAckeR
Tester
Jan 2, 2009, 12:49
It's fixed for me too with Aaron's fix. I can't make it crash like Layne however.

I had this problem too with 0.128u7. I have a X800, so it was not limited to the older 9xxx series.

verbose output:
Video: Monitor 00010003 = "\\.\DISPLAY1"
Video: Monitor 00010001 = "\\.\DISPLAY2" (primary)
Video: Monitor 00010005 = "\\.\DISPLAY3"
Direct3D: Using Direct3D 9
Direct3D: Configuring adapter #1 = RADEON X800 PRO
Direct3D: Using dynamic textures
Direct3D: YUV format = UYVY
Direct3D: Device created at 1280x1024
Direct3D: Max texture size = 2048x2048
DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channels
RawInput: APIs detected
Input: Adding Mouse #1: \??\ACPI#PNP0F03#4&35f762c4&0#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
Input: Adding Gun #1: \??\ACPI#PNP0F03#4&35f762c4&0#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
Input: Adding Mouse #2: \??\HID#Vid_413c&Pid_3016#6&de43a91&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
Input: Adding Gun #2: \??\HID#Vid_413c&Pid_3016#6&de43a91&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
Input: Adding Kbd #1: \??\ACPI#PNP0303#4&35f762c4&0#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
DirectInput: Using DirectInput 7
User avatar
No.03484
aaron
Developer
Jan 2, 2009, 16:58
I'm marking the bug as resolved. If 0.129 comes out and you are still seeing the crash, open a new bug on that.