Viewing Issue Advanced Details
[ Jump to Notes ]
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
03678 Interface Minor Have not tried Jan 19, 2010, 17:53 May 20, 2013, 10:10
Tester Tafoid View Status Public Platform MAME (Self-compiled)
Assigned To Resolution Won't fix OS
Status [?] Closed Driver
Version 0.136u1 Fixed in Version Build Normal
Fixed in Git Commit Github Pull Request #
Summary 03678: -d3dversion 8 does not work and reverts to GDI
Description Use of the trigger -d3dversion with 8 as the value is not valid as default built and the video mode falls back to GDI.

d:\emulator\arcade\mame>mame mappy -d3dversion 8 -video d3d -verbose -str 10
Parsing mame.ini
Video: Monitor 00010001 = "\\.\DISPLAY1" (primary)
Unable to initialize Direct3D.
DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channels
DirectInput: Using DirectInput 7
Input: Adding Kbd #1: Keyboard
Input: Adding Mouse #1: Mouse
Input: Adding Gun #1: Mouse
Input: Adding Joy #1: USB Game Device
Average speed: 31.66% (9 seconds)
Sound: buffer overflows=87 underflows=13

-----

d:\emulator\arcade\mame>mame mappy -d3dversion 9 -video d3d -verbose -str 10
Parsing mame.ini
Video: Monitor 00010001 = "\\.\DISPLAY1" (primary)
Direct3D: Using Direct3D 9
Direct3D: Configuring adapter #0 = ALL-IN-WONDER 9600 SERIES
Direct3D: Using dynamic textures
Direct3D: YUV format = UYVY
Direct3D: Device created at 1152x864
Direct3D: Max texture size = 2048x2048
DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channels
DirectInput: Using DirectInput 7
Input: Adding Kbd #1: Keyboard
Input: Adding Mouse #1: Mouse
Input: Adding Gun #1: Mouse
Input: Adding Joy #1: USB Game Device
Average speed: 99.72% (9 seconds)
Sound: buffer overflows=2 underflows=0
Steps To Reproduce
Additional Information Testing of binaries show that version 0.126u3 is the first version this is observed and has been consistently NOT working since then.
Github Commit
Flags
Regression Version 0.126u3
Affected Sets / Systems
Attached Files
  
Relationships
There are no relationship linked to this issue.
Notes
3
User avatar
No.05545
Firewave
Senior Tester
Jan 19, 2010, 19:04
 I can confirm this on Windows XP x64 with the official 0.136 binary and a self-compiled 0.136u1 binary.
User avatar
No.05547
Firewave
Senior Tester
Jan 19, 2010, 21:01
 Looking at the code in osd/windows/drawd3d.c the reason is quite simple:

#if DIRECT3D_VERSION < 0x0900
	// if that didn't work, try Direct3D 8
	if (d3dintf == NULL && version >= 8)
		d3dintf = drawd3d8_init();
#endif

since d3d9.h is included and it contains the following

#ifndef DIRECT3D_VERSION
#define DIRECT3D_VERSION  0x0900
#endif
User avatar
No.09512
Tafoid
Administrator
May 20, 2013, 10:10
 Effective 0.148u5, -d3dversion has been taken out of the command-line usage list and support for d3d 8 has been dropped from the core - leaving this bug unresolved and closed