Home Page

MAME as of 0.162 crash with dual screen and D3D

Posted By: viajante

MAME as of 0.162 crash with dual screen and D3D - 12/18/17 10:44 PM

ISSUE: MAME as of 0.162 crashes with dual screen and D3D enabled simultaneously.
Message: No Driver Loaded [____empty]

HISTORIC:
Using MAME with dual monitor and Marquee artwork on 2nd screen. Run flawlessly up to MAME 0.161.
Now updated to MAME 0.192 and it crashes when enabled dual monitor (numscreens = 2) and D3D video acceleration.
On MAME 0.192 it works using single screen with D3D or using dual monitor with DDRAW/GDI/OpenGL.

After tests with other MAME versions I figure out the crashes occurs as of MAME 0.162 (after MAME/MESS merged).

Found issues in the web reporting MAME "No driver Loaded" and black screen for different reasons. Tried all posted solutions but no lucky so far.


Hardware used:
- AMD bulldozer
- Video AMD Radeon 7850 (Both monitors plugued on Radeon video card ports. Primary using DVi and Secondary using HDMI)
- O.S.: Windows 7 Ultimate; using latest AMD video drivers.
- CONTROLS: IPAC Ultimate I/O; ULTIMARC U360 joys; G27 wheel
Posted By: Just Desserts

Re: MAME as of 0.162 crash with dual screen and D3D - 12/18/17 10:52 PM

Sounds like you should use DDRAW, GDI, or OpenGL, then, along with the latest version of MAME. Not sure why you expect support for a 3-year-old version of MAME.
Posted By: viajante

Re: MAME as of 0.162 crash with dual screen and D3D - 12/18/17 11:33 PM

"Not sure why you expect support for a 3-year-old version of MAME"

Maybe there was a misunderstand in my statement. Im saying from MAME 0.162 to MAME 0.192 (Current version) it crashes with d3d and dual screen activated.
Im stuck on MAME 0.161 as the latest functional version.
Posted By: B2K24

Re: MAME as of 0.162 crash with dual screen and D3D - 12/19/17 12:43 AM

What is the exact command-line you're sending to MAME to get a crash? I have dual displays here and it doesn't crash with latest.
Posted By: viajante

Re: MAME as of 0.162 crash with dual screen and D3D - 12/19/17 03:26 AM

Using mame.ini

video d3d
numscreens 2


The following above crashes from MAME 0.162 to 0.192
Works with all older versions up to MAME 0.161

What hardware are you using for dual displays ? Are you using 2 video cards ?
I have both monitors using two different ports from same Video Card. Never had issues for years but considering you dont have issues with dual displays I suspect some incompatibility was created after v0.162.
Tomorrow I can try install a 2nd video card and plug each monitor on different video cards.
Posted By: R. Belmont

Re: MAME as of 0.162 crash with dual screen and D3D - 12/19/17 01:04 PM

Post your entire mame.ini and your complete command line arguments, as those two options don't reproduce the bug.
Posted By: B2K24

Re: MAME as of 0.162 crash with dual screen and D3D - 12/19/17 04:53 PM

Sorry, I was mistaken in my previous post.

Now after extensively testing, I can confirm here that running with -video bgfx -numscreens 2 causes an indefinite hang.

Running with -video d3d -numscreens 2 I get Unable to create the Direct3D device <88760868>

Using opengl everything works as it should.

I'll have to disconnect everything here and reseat all the connections to see if it's a specific fault here on my end.
Posted By: viajante

Re: MAME as of 0.162 crash with dual screen and D3D - 12/19/17 11:07 PM

Posting the entire mame.ini at the bottom as required. If you replicated my issue the ini file is the unlikely root cause.
I did a fresh/clean install, created the mame.ini with -cc comandline and the issue remains.
It works with all other video options as I posted previously (gdi/ddraw/opengl) but it is unplayable w/o d3d or bgfx.
Tried using log, verbose and debugger options on mame.ini but can't get error msgs this way.

Had success today using windowed mode (window 1). In windowed mode I can run d3d and 2 screens as expected.
Now Im stuck with the issue under following conditions:
D3D, 2 screens and Full Screen > results on black windowed screen and message: No Driver Loaded [____empty].

Tested many other versions. The bug shows up on MAME 0.162 update and has been replicated to all versions up to now.

========================================
#
# CORE CONFIGURATION OPTIONS
#
readconfig 1
writeconfig 0

#
# CORE SEARCH PATH OPTIONS
#
homepath .
rompath roms
hashpath hash
samplepath samples
artpath artwork
ctrlrpath ctrlr
inipath .;ini;ini/presets
fontpath .
cheatpath cheat
crosshairpath crosshair
pluginspath plugins
languagepath language
swpath software

#
# CORE OUTPUT DIRECTORY OPTIONS
#
cfg_directory cfg
nvram_directory nvram
input_directory inp
state_directory sta
snapshot_directory snap
diff_directory diff
comment_directory comments

#
# CORE STATE/PLAYBACK OPTIONS
#
state
autosave 0
playback
record
record_timecode 0
exit_after_playback 0
mngwrite
aviwrite
wavwrite
snapname %g/%i
snapsize auto
snapview internal
snapbilinear 1
statename %g
burnin 0

#
# CORE PERFORMANCE OPTIONS
#
autoframeskip 0
frameskip 0
seconds_to_run 0
throttle 1
sleep 1
speed 1.0
refreshspeed 0

#
# CORE RENDER OPTIONS
#
keepaspect 1
unevenstretch 1
unevenstretchx 0
unevenstretchy 0
autostretchxy 0
intoverscan 0
intscalex 0
intscaley 0

#
# CORE ROTATION OPTIONS
#
rotate 1
ror 0
rol 0
autoror 0
autorol 0
flipx 0
flipy 0

#
# CORE ARTWORK OPTIONS
#
artwork_crop 0
use_backdrops 1
use_overlays 1
use_bezels 1
use_cpanels 1
use_marquees 1

#
# CORE SCREEN OPTIONS
#
brightness 1.0
contrast 1.0
gamma 1.0
pause_brightness 0.65
effect none

#
# CORE VECTOR OPTIONS
#
beam_width_min 1.0
beam_width_max 1.0
beam_intensity_weight 0
flicker 0

#
# CORE SOUND OPTIONS
#
samplerate 48000
samples 1
volume 0

#
# CORE INPUT OPTIONS
#
coin_lockout 1
ctrlr
mouse 0
joystick 1
lightgun 0
multikeyboard 0
multimouse 0
steadykey 0
ui_active 0
offscreen_reload 0
joystick_map auto
joystick_deadzone 0.3
joystick_saturation 0.85
natural 0
joystick_contradictory 0
coin_impulse 0

#
# CORE INPUT AUTOMATIC ENABLE OPTIONS
#
paddle_device keyboard
adstick_device keyboard
pedal_device keyboard
dial_device keyboard
trackball_device keyboard
lightgun_device keyboard
positional_device keyboard
mouse_device mouse

#
# CORE DEBUGGING OPTIONS
#
verbose 0
log 0
oslog 0
debug 0
update_in_pause 0
debugscript

#
# CORE COMM OPTIONS
#
comm_localhost 0.0.0.0
comm_localport 15112
comm_remotehost 127.0.0.1
comm_remoteport 15112

#
# CORE MISC OPTIONS
#
drc 1
drc_use_c 0
drc_log_uml 0
drc_log_native 0
bios
cheat 0
skip_gameinfo 0
uifont default
ui cabinet
ramsize
confirm_quit 0
ui_mouse 1
autoboot_command
autoboot_delay 0
autoboot_script
console 0
plugins 1
plugin
noplugin
language English

#
# HTTP SERVER OPTIONS
#
http 0
http_port 8080
http_root web

#
# Opciones del Parche Nonag
#
Desactivar_parche_nonag 0
Desactivar_parche_pantallas_de_carga 0

#
# OSD KEYBOARD MAPPING OPTIONS
#
uimodekey SCRLOCK

#
# OSD FONT OPTIONS
#
uifontprovider auto

#
# OSD OUTPUT OPTIONS
#
output auto

#
# OSD INPUT OPTIONS
#
keyboardprovider auto
mouseprovider auto
lightgunprovider auto
joystickprovider auto

#
# OSD DEBUGGING OPTIONS
#
debugger auto
debugger_font auto
debugger_font_size 0
watchdog 0

#
# OSD PERFORMANCE OPTIONS
#
numprocessors auto
bench 0

#
# OSD VIDEO OPTIONS
#
video d3d
numscreens 2
window 0
maximize 0
waitvsync 0
syncrefresh 0
monitorprovider auto

#
# OSD PER-WINDOW VIDEO OPTIONS
#
screen auto
aspect auto
resolution auto
view auto
screen0 auto
aspect0 auto
resolution0 auto
view0 auto
screen1 auto
aspect1 auto
resolution1 auto
view1 auto
screen2 auto
aspect2 auto
resolution2 auto
view2 auto
screen3 auto
aspect3 auto
resolution3 auto
view3 auto

#
# OSD FULL SCREEN OPTIONS
#
switchres 0

#
# OSD ACCELERATED VIDEO OPTIONS
#
filter 1
prescale 1

#
# OpenGL-SPECIFIC OPTIONS
#
gl_forcepow2texture 0
gl_notexturerect 0
gl_vbo 1
gl_pbo 1
gl_glsl 0
gl_glsl_filter 1
glsl_shader_mame0 none
glsl_shader_mame1 none
glsl_shader_mame2 none
glsl_shader_mame3 none
glsl_shader_mame4 none
glsl_shader_mame5 none
glsl_shader_mame6 none
glsl_shader_mame7 none
glsl_shader_mame8 none
glsl_shader_mame9 none
glsl_shader_screen0 none
glsl_shader_screen1 none
glsl_shader_screen2 none
glsl_shader_screen3 none
glsl_shader_screen4 none
glsl_shader_screen5 none
glsl_shader_screen6 none
glsl_shader_screen7 none
glsl_shader_screen8 none
glsl_shader_screen9 none

#
# OSD SOUND OPTIONS
#
sound auto
audio_latency 2

#
# PORTAUDIO OPTIONS
#
pa_api none
pa_device none
pa_latency 0

#
# BGFX POST-PROCESSING OPTIONS
#
bgfx_path bgfx
bgfx_backend auto
bgfx_debug 0
bgfx_screen_chains default
bgfx_shadow_mask slot-mask.png
bgfx_avi_name auto

#
# WINDOWS PERFORMANCE OPTIONS
#
priority 0
profile 0

#
# WINDOWS VIDEO OPTIONS
#
menu 0

#
# DIRECT3D POST-PROCESSING OPTIONS
#
hlslpath hlsl
hlsl_enable 0
hlsl_oversampling 0
hlsl_write auto
hlsl_snap_width 2048
hlsl_snap_height 1536
shadow_mask_tile_mode 0
shadow_mask_alpha 0.0
shadow_mask_texture shadow-mask.png
shadow_mask_x_count 6
shadow_mask_y_count 4
shadow_mask_usize 0.1875
shadow_mask_vsize 0.25
shadow_mask_uoffset 0.0
shadow_mask_voffset 0.0
distortion 0.0
cubic_distortion 0.0
distort_corner 0.0
round_corner 0.0
smooth_border 0.0
reflection 0.0
vignetting 0.0
scanline_alpha 0.0
scanline_size 1.0
scanline_height 1.0
scanline_variation 1.0
scanline_bright_scale 1.0
scanline_bright_offset 0.0
scanline_jitter 0.0
hum_bar_alpha 0.0
defocus 0.0,0.0
converge_x 0.0,0.0,0.0
converge_y 0.0,0.0,0.0
radial_converge_x 0.0,0.0,0.0
radial_converge_y 0.0,0.0,0.0
red_ratio 1.0,0.0,0.0
grn_ratio 0.0,1.0,0.0
blu_ratio 0.0,0.0,1.0
saturation 1.0
offset 0.0,0.0,0.0
scale 1.0,1.0,1.0
power 1.0,1.0,1.0
floor 0.0,0.0,0.0
phosphor_life 0.0,0.0,0.0

#
# NTSC POST-PROCESSING OPTIONS
#
yiq_enable 0
yiq_jitter 0.0
yiq_cc 3.57954545
yiq_a 0.5
yiq_b 0.5
yiq_o 0.0
yiq_p 1.0
yiq_n 1.0
yiq_y 6.0
yiq_i 1.2
yiq_q 0.6
yiq_scan_time 52.6
yiq_phase_count 2

#
# VECTOR POST-PROCESSING OPTIONS
#
vector_beam_smooth 0.0
vector_length_scale 0.5
vector_length_ratio 0.5

#
# BLOOM POST-PROCESSING OPTIONS
#
bloom_blend_mode 0
bloom_scale 0.0
bloom_overdrive 1.0,1.0,1.0
bloom_lvl0_weight 1.0
bloom_lvl1_weight 0.64
bloom_lvl2_weight 0.32
bloom_lvl3_weight 0.16
bloom_lvl4_weight 0.08
bloom_lvl5_weight 0.06
bloom_lvl6_weight 0.04
bloom_lvl7_weight 0.02
bloom_lvl8_weight 0.01

#
# FULL SCREEN OPTIONS
#
triplebuffer 0
full_screen_brightness 1.0
full_screen_contrast 1.0
full_screen_gamma 1.0

#
# INPUT DEVICE OPTIONS
#
global_inputs 0
dual_lightgun 0

#
# FRONTEND COMMAND OPTIONS
#
dtd 1

===================================
Posted By: B2K24

Re: MAME as of 0.162 crash with dual screen and D3D - 12/20/17 12:35 AM

I know for a fact that dual screens have worked correctly long after 0.162

The issue here is that it seems you're using unofficial builds and/or unofficial compiled builds because of this spotted in your mame.ini

Code
# Opciones del Parche Nonag
#
Desactivar_parche_nonag 0
Desactivar_parche_pantallas_de_carga 0


Which means that you'll get different results or different bugs that don't exist when compared with someone using the official build from mamedev.org

Now I'm not totally ruling out that something isn't wrong at this point, but more investigative work might be needed.
Posted By: viajante

Re: MAME as of 0.162 crash with dual screen and D3D - 12/21/17 12:05 AM

Sorry. Forget to mention I used on tests the official and unofficial builds looking for different results but both had same issue.
Below is the mame.ini from tests using MAME 0.192 Official Binaries 64bit.
This time used FE to generate ini file (not -cc command line), results on black windowed screen and message: No Driver Loaded [____empty].
==========================================
#
# CORE CONFIGURATION OPTIONS
#
readconfig 1
writeconfig 0

#
# CORE SEARCH PATH OPTIONS
#
homepath .
rompath roms
hashpath hash
samplepath samples
artpath artwork
ctrlrpath ctrlr
inipath .;ini;ini/presets
fontpath .
cheatpath cheat
crosshairpath crosshair
pluginspath plugins
languagepath language
swpath software

#
# CORE OUTPUT DIRECTORY OPTIONS
#
cfg_directory cfg
nvram_directory nvram
input_directory inp
state_directory sta
snapshot_directory snap
diff_directory diff
comment_directory comments

#
# CORE STATE/PLAYBACK OPTIONS
#
state
autosave 0
playback
record
record_timecode 0
exit_after_playback 0
mngwrite
aviwrite
wavwrite
snapname %g/%i
snapsize auto
snapview internal
snapbilinear 1
statename %g
burnin 0

#
# CORE PERFORMANCE OPTIONS
#
autoframeskip 0
frameskip 0
seconds_to_run 0
throttle 1
sleep 1
speed 1.0
refreshspeed 0

#
# CORE RENDER OPTIONS
#
keepaspect 1
unevenstretch 1
unevenstretchx 0
unevenstretchy 0
autostretchxy 0
intoverscan 0
intscalex 0
intscaley 0

#
# CORE ROTATION OPTIONS
#
rotate 1
ror 0
rol 0
autoror 0
autorol 0
flipx 0
flipy 0

#
# CORE ARTWORK OPTIONS
#
artwork_crop 0
use_backdrops 1
use_overlays 1
use_bezels 1
use_cpanels 1
use_marquees 1

#
# CORE SCREEN OPTIONS
#
brightness 1.0
contrast 1.0
gamma 1.0
pause_brightness 0.65
effect none

#
# CORE VECTOR OPTIONS
#
beam_width_min 1.0
beam_width_max 1.0
beam_intensity_weight 0
flicker 0

#
# CORE SOUND OPTIONS
#
samplerate 48000
samples 1
volume 0

#
# CORE INPUT OPTIONS
#
coin_lockout 1
ctrlr
mouse 0
joystick 1
lightgun 0
multikeyboard 0
multimouse 0
steadykey 0
ui_active 0
offscreen_reload 0
joystick_map auto
joystick_deadzone 0.3
joystick_saturation 0.85
natural 0
joystick_contradictory 0
coin_impulse 0

#
# CORE INPUT AUTOMATIC ENABLE OPTIONS
#
paddle_device keyboard
adstick_device keyboard
pedal_device keyboard
dial_device keyboard
trackball_device keyboard
lightgun_device keyboard
positional_device keyboard
mouse_device mouse

#
# CORE DEBUGGING OPTIONS
#
verbose 0
log 0
oslog 0
debug 0
update_in_pause 0
debugscript

#
# CORE COMM OPTIONS
#
comm_localhost 0.0.0.0
comm_localport 15112
comm_remotehost 127.0.0.1
comm_remoteport 15112

#
# CORE MISC OPTIONS
#
drc 1
drc_use_c 0
drc_log_uml 0
drc_log_native 0
bios
cheat 0
skip_gameinfo 0
uifont default
ui cabinet
ramsize
confirm_quit 0
ui_mouse 1
autoboot_command
autoboot_delay 0
autoboot_script
console 0
plugins 1
plugin
noplugin
language English

#
# HTTP SERVER OPTIONS
#
http 0
http_port 8080
http_root web

#
# OSD KEYBOARD MAPPING OPTIONS
#
uimodekey SCRLOCK

#
# OSD FONT OPTIONS
#
uifontprovider auto

#
# OSD OUTPUT OPTIONS
#
output auto

#
# OSD INPUT OPTIONS
#
keyboardprovider auto
mouseprovider auto
lightgunprovider auto
joystickprovider auto

#
# OSD DEBUGGING OPTIONS
#
debugger auto
debugger_font auto
debugger_font_size 0
watchdog 0

#
# OSD PERFORMANCE OPTIONS
#
numprocessors auto
bench 0

#
# OSD VIDEO OPTIONS
#
video d3d
numscreens 2
window 0
maximize 1
waitvsync 0
syncrefresh 0
monitorprovider auto

#
# OSD PER-WINDOW VIDEO OPTIONS
#
screen auto
aspect auto
resolution auto
view auto
screen0 auto
aspect0 auto
resolution0 auto
view0 auto
screen1 auto
aspect1 auto
resolution1 auto
view1 auto
screen2 auto
aspect2 auto
resolution2 auto
view2 auto
screen3 auto
aspect3 auto
resolution3 auto
view3 auto

#
# OSD FULL SCREEN OPTIONS
#
switchres 0

#
# OSD ACCELERATED VIDEO OPTIONS
#
filter 1
prescale 1

#
# OpenGL-SPECIFIC OPTIONS
#
gl_forcepow2texture 0
gl_notexturerect 0
gl_vbo 1
gl_pbo 1
gl_glsl 0
gl_glsl_filter 1
glsl_shader_mame0 none
glsl_shader_mame1 none
glsl_shader_mame2 none
glsl_shader_mame3 none
glsl_shader_mame4 none
glsl_shader_mame5 none
glsl_shader_mame6 none
glsl_shader_mame7 none
glsl_shader_mame8 none
glsl_shader_mame9 none
glsl_shader_screen0 none
glsl_shader_screen1 none
glsl_shader_screen2 none
glsl_shader_screen3 none
glsl_shader_screen4 none
glsl_shader_screen5 none
glsl_shader_screen6 none
glsl_shader_screen7 none
glsl_shader_screen8 none
glsl_shader_screen9 none

#
# OSD SOUND OPTIONS
#
sound auto
audio_latency 2

#
# PORTAUDIO OPTIONS
#
pa_api none
pa_device none
pa_latency 0

#
# BGFX POST-PROCESSING OPTIONS
#
bgfx_path bgfx
bgfx_backend auto
bgfx_debug 0
bgfx_screen_chains default
bgfx_shadow_mask slot-mask.png
bgfx_avi_name auto

#
# WINDOWS PERFORMANCE OPTIONS
#
priority 0
profile 0

#
# WINDOWS VIDEO OPTIONS
#
menu 0

#
# DIRECT3D POST-PROCESSING OPTIONS
#
hlslpath hlsl
hlsl_enable 0
hlsl_oversampling 0
hlsl_write auto
hlsl_snap_width 2048
hlsl_snap_height 1536
shadow_mask_tile_mode 0
shadow_mask_alpha 0.25
shadow_mask_texture shadow-mask.png
shadow_mask_x_count 12
shadow_mask_y_count 6
shadow_mask_usize 0.5
shadow_mask_vsize 0.5
shadow_mask_uoffset 0.0
shadow_mask_voffset 0.0
distortion 0.0
cubic_distortion 0.0
distort_corner 0.0
round_corner 0.0
smooth_border 0.0
reflection 0.0
vignetting 0.0
scanline_alpha 0.50
scanline_size 1.0
scanline_height 1.0
scanline_variation 1.0
scanline_bright_scale 2.0
scanline_bright_offset 0.0
scanline_jitter 0.0
hum_bar_alpha 0.0
defocus 0.75,0.0
converge_x 0.0,0.0,0.0
converge_y 0.0,0.0,0.0
radial_converge_x 0.0,0.0,0.0
radial_converge_y 0.0,0.0,0.0
red_ratio 1.05,0.00,0.10
grn_ratio -0.10,1.00,0.25
blu_ratio -0.25,0.25,1.25
saturation 1.25
offset -0.30,-0.20,-0.05
scale 1.15,1.05,0.90
power 0.90,0.90,1.15
floor 0.025,0.025,0.025
phosphor_life 0.25,0.25,0.25

#
# NTSC POST-PROCESSING OPTIONS
#
yiq_enable 0
yiq_jitter 0.0
yiq_cc 3.57954545
yiq_a 0.5
yiq_b 0.5
yiq_o 0.0
yiq_p 1.0
yiq_n 1.0
yiq_y 6.0
yiq_i 1.2
yiq_q 0.6
yiq_scan_time 52.6
yiq_phase_count 2

#
# VECTOR POST-PROCESSING OPTIONS
#
vector_beam_smooth 0.0
vector_length_scale 0.5
vector_length_ratio 0.5

#
# BLOOM POST-PROCESSING OPTIONS
#
bloom_blend_mode 0
bloom_scale 0.25
bloom_overdrive 1.00,1.00,1.00
bloom_lvl0_weight 1.00
bloom_lvl1_weight 0.64
bloom_lvl2_weight 0.32
bloom_lvl3_weight 0.16
bloom_lvl4_weight 0.08
bloom_lvl5_weight 0.06
bloom_lvl6_weight 0.04
bloom_lvl7_weight 0.02
bloom_lvl8_weight 0.01

#
# FULL SCREEN OPTIONS
#
triplebuffer 0
full_screen_brightness 1.0
full_screen_contrast 1.0
full_screen_gamma 1.0

#
# INPUT DEVICE OPTIONS
#
global_inputs 0
dual_lightgun 0
Posted By: Haze

Re: MAME as of 0.162 crash with dual screen and D3D - 12/21/17 12:08 AM

the -verbose output for cases that don't work might be useful.
Posted By: viajante

Re: MAME as of 0.162 crash with dual screen and D3D - 12/22/17 02:23 AM

I know. In the beginning I tried verbose and log from debugging options but mame seems crashes before be able to create a error file.
Today did other tries :
- Ran DXdiag tool checking DX and D3D;
- Reinstall DX anyway;
- Forced different frequencies setup on both monitors;
- install mame 32bit version. Also tried compatibility modes;
- plugged monitor in other video card port;
- Reset Radeon softw configs using manufacturer default adjustments.

No lucky so far

Im starting to be out of ideas.

If the statement is true that nobody else has issues running latest mame versions with 2 screens, I only can think on hardware incompatibility.
Maybe I need to replace my Radeon video card and try NVidia. At instance I will discard problems with Gigabyte gamer motherboard or win7 OS.
But still hard to believe on hardware issue considering I have MAME 0.161 and over 30 other emulators running under the FE.
Posted By: viajante

Re: MAME as of 0.162 crash with dual screen and D3D - 12/24/17 01:08 AM

Today I confirmed the issue DOES exist with latest MAME versions using 2 screens mode.
I used other CPU (Intel i7 - NVidia video Card - Win10) and the issue was replicated exactly same.
Therefore there are no hardware or software incompatibility with my AMD Bulldozer - Radeon video card - Win7)
The bug DOES exist. Be free to confirm it and if possible address this problem.

Considering the current situation I will keep MAME 0.161 that DOES work with 2 screens and use MAME 0.192 with one screen mode to run newer games.
Posted By: Haze

Re: MAME as of 0.162 crash with dual screen and D3D - 12/24/17 12:57 PM

Maybe this is just a case of where the hardware is only capable of driving the 2nd display with a more limited set of DirectX features, I know my old card refused to do proper accelerated modes on the 2nd monitor.

MAME did drop support for some weaker cards at one point, so given the feature still works for some people it might just be something along those lines.

You've still not posted any kind of -verbose output for the cases that fail in the latest version tho.
Posted By: R. Belmont

Re: MAME as of 0.162 crash with dual screen and D3D - 12/24/17 01:56 PM

Here's the problem: multiple monitors have largely been abandoned by PC users in favor of a single higher-res one. For instance, a year ago I junked my 2 20" monitors for one 28" 4K monitor. So I'm not sure anyone that could help you actually has 2 monitors.
Posted By: Vas Crabb

Re: MAME as of 0.162 crash with dual screen and D3D - 12/24/17 02:22 PM

Yeah, I have a single 31.5" 4k monitor on my Windows setup as well - I can't fit a second one on my desk in Sydney.
Posted By: Haze

Re: MAME as of 0.162 crash with dual screen and D3D - 12/24/17 02:25 PM

while instead I'm seeing more and more people getting multi-monitor setups here and asking me, as somebody who does development, why I don't have one... (I found it annoying and just re-purposed the monitor on another machine)
Posted By: viajante

Re: MAME as of 0.162 crash with dual screen and D3D - 12/24/17 07:26 PM

I tried verbose option on both CPU tests but didnt create any log file.
Dont know why. Maybe MAME crashes before be able to create log file ? Or MAME doesnt see it as an error ?
If someone else can test it and see what happens I will appreciate.
Posted By: Haze

Re: MAME as of 0.162 crash with dual screen and D3D - 12/24/17 07:32 PM

-verbose prints information to the commandline, not a file
Posted By: ICEknight

Re: MAME as of 0.162 crash with dual screen and D3D - 12/24/17 07:50 PM

Graphic tablets also act as a second monitor, so I'm sure that there must be a lot of people who will still be interested in MAME supporting dual monitor setups.
Posted By: Heihachi_73

Re: MAME as of 0.162 crash with dual screen and D3D - 12/24/17 10:30 PM

Originally Posted by B2K24
Sorry, I was mistaken in my previous post.

Now after extensively testing, I can confirm here that running with -video bgfx -numscreens 2 causes an indefinite hang.

Running with -video d3d -numscreens 2 I get Unable to create the Direct3D device <88760868>

Using opengl everything works as it should.

I'll have to disconnect everything here and reseat all the connections to see if it's a specific fault here on my end.

Interesting, I used to get the exact same error code if I tried to Alt+Tab from full screen MAME in D3D mode (or was it Alt+Enter that caused that? I forget), it used to require a force kill via Task Manager (or a Ctrl+C in the command line) as the error dialog would repeat infinitely. It didn't happen in OpenGL.
Posted By: Just Desserts

Re: MAME as of 0.162 crash with dual screen and D3D - 12/24/17 10:48 PM

I might be able to look into this at some point, if I'm able to reproduce it on my dual-screen setup.
Posted By: u-man

Re: MAME as of 0.162 crash with dual screen and D3D - 12/25/17 10:33 AM

Could anyone try this, with artwork DISABLED.
I remember something from Jezze, that Dual-screens dont work with artwork enabled.
Posted By: Just Desserts

Re: MAME as of 0.162 crash with dual screen and D3D - 12/25/17 11:02 AM

Good call, u-man. Now that you mention it, I vaguely remember something similar!
Posted By: viajante

Re: MAME as of 0.162 crash with dual screen and D3D - 12/28/17 04:50 PM

New tests with MAME with d3d and Dual Screen:
1. Run verbose under CMD window as instructed. It results in message: "Unable to create the Direct3D device (88760868) "
2. Disabled Artwork > no changes. Same bug
3. Windowed mode > IT WORKS

My opinion so far after tests: looks like occurs when changes the aspect ratio on full screen mode and dual screen simultaneously. Or could be the UI using natively OpenGL and crashes when changes to D3D ?
Didnt see relation with artwork handling.
© 2019 Forums