Build Your Own Arcade Controls Forum
Main => Software Forum => Topic started by: srarcade on February 05, 2016, 03:48:20 pm
-
MAME 0.170 and other earlier versions.
Ok- i've hit a dead end and I can't find the problem. I just got done moving my MAME box to a new machine, just about everything is the same- Win 7, same video card, DirectX11- I go to launch mame64.exe and I'm getting a nasty error with hlsl enabled:
C:\MAME>mame64.exe sf2
Shader primary.fx is missing, corrupt or cannot be compiled.
Shader post.fx is missing, corrupt or cannot be compiled.
Shader distortion.fx is missing, corrupt or cannot be compiled.
Shader prescale.fx is missing, corrupt or cannot be compiled.
Shader phosphor.fx is missing, corrupt or cannot be compiled.
Shader focus.fx is missing, corrupt or cannot be compiled.
Shader deconverge.fx is missing, corrupt or cannot be compiled.
Shader color.fx is missing, corrupt or cannot be compiled.
Shader ntsc.fx is missing, corrupt or cannot be compiled.
Shader bloom.fx is missing, corrupt or cannot be compiled.
Shader downsample.fx is missing, corrupt or cannot be compiled.
Shader vector.fx is missing, corrupt or cannot be compiled.
Unable to initialize Direct3D.
0000000000229980: 0000000001512191 (winmain_dump_stack()+0x0041)
0000000000229A40: 00000000029AC1A9 (osd_break_into_debugger(char const*)+0x002
9)
0000000000229A80: 0000000002500095 (emu_fatalerror::emu_fatalerror(char const*
, char*)+0x0045)
0000000000229EF0: 000000000250030D (fatalerror(char const*, ...)+0x004d)
0000000000229FC0: 0000000001537CDC (win_window_info::create(running_machine&,
int, osd_monitor_info*, osd_window_config const*)+0x078c)
000000000022A030: 0000000001532842 (windows_osd_interface::video_init()+0x00f2
)
000000000022A120: 0000000001514882 (osd_common_t::init_subsystems()+0x0942)
000000000022A1F0: 00000000015134B7 (windows_osd_interface::init(running_machin
e&)+0x01d7)
000000000022A310: 000000000256FE3A (running_machine::start()+0x052a)
000000000022A370: 0000000002570C42 (running_machine::run(bool)+0x00b2)
000000000022F770: 000000000256A436 (machine_manager::execute()+0x0216)
000000000022F950: 00000000024BDDE2 (cli_frontend::execute(int, char**)+0x0cc2)
000000000022FDF0: 000000000151166B (utf8_main(int, char**)+0x016b)
000000000022FE50: 00000000029A9B2F (wmain+0x007f)
000000000022FF20: 000000000040140C (__tmainCRTStartup+0x025c)
000000000022FF50: 000000000040153B (mainCRTStartup+0x001b)
000000000022FF80: 00000000773A59ED (BaseThreadInitThunk+0x000d)
000000000022FFD0: 00000000774DB831 (RtlUserThreadStart+0x0021)
FATALERROR: Unable to complete window creation
-Win 7 Pro OS, all up to date
-DirectX11 up to date
-GeForce GT430 with latest Nvidia drivers
-DX web installer, up to date
-dxdiag - no issues found on 32 or 64 bit menus, everything enabled
-Direct3D works fine on other apps
-confirmed that those hlsl Shader files are in fact there
-problem even happening on vanilla download of MAME with no changes except 'hlsl_enable' set to 1.
-tried running it from cmd.exe "as Administrator" for kicks, same result.
Ideas and suggestions welcomed. I am totally bust on this one.
Thanks!
-
probably missing direct x 9 runtimes as mentioned two threads below this thread you just started.
http://forum.arcadecontrols.com/index.php/topic,116068.0.html (http://forum.arcadecontrols.com/index.php/topic,116068.0.html)
Having direct x 11 up to date doesn't mean that you have all prior versions covered.
You'd think it would work that way, but it does not.
-
Yes [iwata] please understand [/iwata] that Directx9 and below are separate from 10 and beyond. A common problem for many games and emulators is an improperly installed DX9 runtime.
-
Well slap me and call me stupid- yea, that was the problem. :hissy: Did not have the DirectX SDK from June 2010 specifically. Thanks for the hint. Sorry I did not see the same thread two posts down, I even sat here like a dummy with the search button for 20 minutes before I made a post!