Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
07138 Crash/Freeze Critical (emulation) Always 18 days ago 17 days ago
Tester Zaghadka View Status Public Platform MAME (Official Binary)
Assigned To Resolution Invalid report OS Windows 10 (64-bit)
Status [?] Closed Driver
Version 0.203 Fixed in Version Build 64-bit
Summary 07138: All HLSL launches: General HLSL failure to initialize DX9
Description The following error occurs on my system for any game utilizing HLSL. Mame 0.202 works fine. 0.203 hard crashes with a DX9 error.

If HLSL is turned off, the window launches fine. Overlay scanlines work as well. But DX9 HLSL is completely broken for me.

I have tested with a mame64 -cc ini file only changing hlsl_enable.
Steps To Reproduce Create default profile. Launch any game with hlsl_enable set to 1.
Additional Information Console dump:

D:\Games\Emulation\MAME>mame64 dkong
Unable to initialize Direct3D 9
Fatal error: Unable to complete window creation


-----------------------------------------------------
Exception at EIP=000000000268d600 (not found): ACCESS VIOLATION
While attempting to read memory at 0000000000000000
-----------------------------------------------------
RAX=0000000000000001 RBX=00000000124ff8e0 RCX=0000000000000000 RDX=000000000f050000
RSI=00000000124e8440 RDI=000000000dfda210 RBP=000000000efa8c00 RSP=000000000efa8b80
 R8=0000000000171380 R9=0000000000008000 R10=0000000000000000 R11=000000000efa8a50
R12=0000000000000000 R13=0000000000000000 R14=0000000000000000 R15=0000000000000000
-----------------------------------------------------
Stack crawl:
  000000000efa8b50: 000000000268d600 (not found)
  000000000efa8c30: 00000000026437e5 (not found)
  000000000efa8c90: 00000000026438cc (not found)
  000000000efa8ce0: 0000000002643ad7 (not found)
  000000000efa8dc0: 0000000002611b37 (not found)
  000000000efa8df0: 00000000026123cd (not found)
  000000000efa8f80: 00007ff9d2f96cc1 (CallWindowProcW+0x04c1)
  000000000efa8fd0: 00007ff9d2f9688b (CallWindowProcW+0x008b)
  000000000efa9070: 00007ff9c76d1b87 (Direct3DCreate9Ex+0x06a7)
  000000000efa9200: 00007ff9d2f96cc1 (CallWindowProcW+0x04c1)
  000000000efa9260: 00007ff9d2f9699c (CallWindowProcW+0x019c)
  000000000efa92c0: 00007ff9d2fa0453 (IsWindowVisible+0x01a3)
  000000000efa9348: 00007ff9d398dc04 (KiUserCallbackDispatcher+0x0024)
  000000000efa9350: 00007ff9d0a023c4 (NtUserDestroyWindow+0x0014)
  000000000efa93d0: 000000000260cf5f (not found)
  000000000efa9410: 000000000260db58 (not found)
  000000000efa9440: 000000000260b8c1 (not found)
  000000000efa9480: 00000000025febb5 (not found)
  000000000efa94c0: 00000000025f92e9 (not found)
  000000000efa9560: 0000000003f6be86 (not found)
  000000000efaf210: 00000000026abd3a (not found)
  000000000efaf4c0: 000000000271a1e4 (not found)
  000000000efaf630: 000000000271a6a5 (not found)
  000000000efaf690: 00000000026a9cda (not found)
  000000000efafe50: 0000000008d97c9d (not found)
  000000000efaff20: 00000000004013c7 (not found)
  000000000efaff50: 00000000004014fb (not found)
  000000000efaff80: 00007ff9d1293034 (BaseThreadInitThunk+0x0014)
  000000000efaffd0: 00007ff9d3961461 (RtlUserThreadStart+0x0021)
Flags
Regression Version
Affected Sets / Systems All HLSL launches
Attached Files
 
Relationships
There are no relationship linked to this issue.
Notes
5
User avatar
No.15688
Zaghadka
Tester
18 days ago
Tried this with a complete fresh install. Everything works fine.

Any idea what changed that could be causing this error?
User avatar
No.15689
Zaghadka
Tester
18 days ago
edited on: 18 days ago
Figured it out. HLSL shaders changed. I had copied the HLSL shaders from the official binary package over to MAME, using overwrite, but apparently I needed to blow away the directory and copy the whole thing to the install directory from scratch.

When you do this, it all works. Close the report. Sorry.
User avatar
No.15691
Zaghadka
Tester
17 days ago
From whatsnew.txt:

"-Added shaders for performing color transforms and three-dimensional lookup tables. [anikom15]
 * Allows arbitrary color space manipulation within the sRGB space."

Somehow, chroma.fx shader was missing from the directory. That's the cause of this error.
User avatar
No.15693
Haze
Senior Tester
17 days ago
edited on: 17 days ago
well looking at the official 64-bit binary distribution that file is present and everything works.

are you saying it's missing from one of the other distributions?

are you extracting using the Windows 10 built in zip support, which is critically broken in the latest Windows 10 update (if a file already exists it won't overwrite it)
User avatar
No.15695
Tafoid
Administrator
17 days ago
Unable to reproduce. We had this problem in the past where people are not updating the HLSL folder of its contents or other support folders. Everything is there in the official packages. No bug and not a valid report.
Closing