MAMEWorld Forums - MAMEUI & IV/Play - Re: Has anyone tried to use OBS and MAMEUI64 at the same time?

OK. Take two at this.

I ran MAME64 from the command line to have it launch its internal menu, chose a game, let it run for a few seconds, then pressed "EXIT" (button on my controller which is basically ) to get back to the menu and "EXIT" again to go back to the command line. Without OBS running, this worked as expected:

Code:

C:\MAME>mame64
Average speed: 99.99% (8 seconds)

Then I launched OBS and had it up monitoring the display to know what to record if I asked it to do so. Repeated the process as above. When I pressed "EXIT" the first time, MAME64 crashes back to command line with this message:

Code:

C:\MAME>mame64
Average speed: 100.00% (7 seconds)
Unable to create the Direct3D device (8876086C)
Unable to initialize Direct3D 9
Fatal error: Unable to complete window creation

And then to make sure, I repeated the process with OBS running and the same thing happened:

Code:

C:\MAME>mame64
Average speed: 100.02% (5 seconds)
Unable to create the Direct3D device (8876086C)
Unable to initialize Direct3D 9
Fatal error: Unable to complete window creation

This behavior is different than what I saw in MAMEUI64 where the app never crashed, but the video frame locked at the last frame that was rendered when I pressed "EXIT". If I held down ALT and pressed TAB to select MAMEUI64, I could see it rendering the normal menu in the thumbnail, but still rendering the last graphics frame from the previous game until I force-quit MAMEUI64.

Thoughts?

Thanks. Hope this write up gets posted properly this time

I think last time I previewed it and then moved on without submitting it the second time.