|
Mame 0.217 doesn't work with Intel IrisPro Graphics [with shaders enabled]
#384904 - 01/04/20 04:49 AM
|
|
|
Mame 0.217 doesn't work with Intel IrisPro Graphics [with shaders enabled]
[Edited the subject line to clarify what is REALLY the issue here - Mr. Do]
Edited by Mr. Do (01/05/20 01:13 AM)
|
|
|
|
Re: Mame 0.217 doesn't work with Intel IrisPro Graphics [with shaders enabled]
[Re: Keatah]
#384907 - 01/04/20 05:19 PM
|
|
|
> Mame 0.217 doesn't work with Intel IrisPro Graphics [with shaders enabled]
Edited by Mr. Do (01/05/20 01:11 AM)
|
|
|
|
Re: Mame 0.217 doesn't work with Intel IrisPro Graphics [with shaders enabled]
[Re: MooglyGuy]
#384909 - 01/04/20 08:34 PM
|
|
|
More specifically, can't do anything with any shaders. No BGFX, GLSL, or HLSL. Otherwise it works fine. And 217 does do shader effects on lesser "cards" like the UHD 630.
Edited by Mr. Do (01/05/20 01:11 AM)
|
|
|
|
Re: Mame 0.217 doesn't work with Intel IrisPro Graphics [with shaders enabled]
[Re: Keatah]
#384910 - 01/04/20 08:43 PM
|
|
|
> More specifically, can't do anything with any shaders. No BGFX, GLSL, or HLSL.
> Otherwise it works fine. And 217 does do shader effects on lesser "cards" like the
> UHD 630.
By all means, don't feel obligated to post -verbose logs or anything that would help anyone diagnose the issue.
Edited by Mr. Do (01/05/20 01:11 AM)
|
|
|
|
Re: Mame 0.217 doesn't work with Intel IrisPro Graphics [with shaders enabled]
[Re: MooglyGuy]
#384913 - 01/05/20 12:08 AM
|
|
|
Oh absolutely not! Would never consider such a thing. I just got tired of hearing "get a better graphics card"..
I can make some additional logs (using -verbose) tonight and post them before tomorrow night.
---
This is an iris pro fail from .216. Win10 pro. 16GB RAM, i7-8559u Reasonably updated graphics and other drivers according to the intel driver update utility I ran a couple of weeks ago.
Without trying to do shaders everything seems to run great with minimal cpu usage.
F:\Copy of test\mame>mame tempest -video bgfx
-----------------------------------------------------
Exception at EIP=086e3418 (bgfx::EncoderImpl::discard()+0x0018): ACCESS VIOLATION
While attempting to read memory at ffffffff
-----------------------------------------------------
EAX=ffffffff EBX=14307358 ECX=14307358 EDX=00000000
ESI=fffffffc EDI=13b8c344 EBP=10cbbff8 ESP=10cbbf5c
-----------------------------------------------------
Stack crawl:
10cbbff8: 086e3418 (bgfx::EncoderImpl::discard()+0x0018)
10cbc058: 05f5379f (bgfx::init(bgfx::Init const&)+0x013f)
10cbc148: 03b148fd (renderer_bgfx::create()+0x02ad)
10cbc1f8: 03ad9abf (win_window_info::complete_create()+0x04bf)
10cbc3d8: 03ada759 (win_window_info::create(running_machine&, int, std::shared_ptr, osd_window_config const*)+0x0a39)
10cbc438: 03ad571b (windows_osd_interface::video_init()+0x008b)
10cbc4e8: 03ac6498 (osd_common_t::init_subsystems()+0x1e68)
10cbc688: 03abd5ca (windows_osd_interface::init(running_machine&)+0x02da)
10cbc718: 059478a5 (running_machine::start()+0x0375)
10cbc7b8: 0594970d (running_machine::run(bool)+0x004d)
10cbf798: 03b84fce (mame_machine_manager::execute()+0x01de)
10cbf928: 03bf4994 (cli_frontend::start_execution(mame_machine_manager*, std::vector, std::allocator >, std::allocator, std::allocator > > > const&)+0x0274)
10cbfa98: 03bf4c79 (cli_frontend::execute(std::vector, std::allocator >, std::allocator, std::allocator > > >&)+0x0039)
10cbfac8: 03b82cbd (emulator_info::start_frontend(emu_options&, osd_interface&, std::vector, std::allocator >, std::allocator, std::allocator > > >&)+0x002d)
10cbfec8: 0a6b45aa (main+0x01aa)
10cbff68: 0040138b (__tmainCRTStartup+0x023b)
10cbff80: 74a96359 (BaseThreadInitThunk+0x0019)
10cbffdc: 771a7a94 (RtlGetAppContainerNamedObjectPath+0x00e4)
10cc00e4: 771a7a64 (RtlGetAppContainerNamedObjectPath+0x00b4)
00000000: 02020000 (usgames_state::usg32(machine_config&)+0x0500)
F:\
Edited by Mr. Do (01/05/20 01:11 AM)
|
|
|
|
Re: Mame 0.217 doesn't work with Intel IrisPro Graphics [with shaders enabled]
[Re: Keatah]
#384914 - 01/05/20 12:15 AM
|
|
|
Alright, in this case it looks like it's BGFX itself that's failing to create the backend.
Since BGFX isn't plumbed to the verbose logging option, there's not much point in running with -video bgfx.
Just for kicks, what does MAME print if you run with "-video d3d -verbose", and similarly, what does it print if you run with "-video opengl -verbose"?
There's no reason why you should have to get a better graphics card in this case. Running without shaders is a basic enough use case that MAME should be able to handle it.
Edited by Mr. Do (01/05/20 01:12 AM)
|
|
|
|
|
Alright. Here's 2 log files. Happy to post other information as req.
|
|
|
|
Re: Mame 0.217 doesn't work with Intel IrisPro Graphics [with shaders enabled]
[Re: Keatah]
#384921 - 01/05/20 01:19 PM
|
|
|
This stands out to me in the D3D log:
"Direct3D: Unable to find D3DXCreateEffectFromFileW"
The D3D renderer in MAME is pretty ancient by today's standards and still uses Direct3D 9. As such, you need to have the DirectX 9.0c runtime installed.
Grab it from Microsoft over here - https://www.microsoft.com/en-us/download/details.aspx?id=34429 - and let me know if that solves your issue with the D3D backend.
BGFX seems a little bit more involved, but it might be fixed by this as well. Please give it a shot.
|
|
|
|
Re: Mame 0.217 doesn't work with Intel IrisPro Graphics [with shaders enabled]
[Re: MooglyGuy]
#384932 - 01/06/20 09:42 AM
|
|
|
Yes I can now use HLSL effects under D3D. So thanks for the tip. Not confident I would have arrived at that solution on my own.
I just used the settings in the standard MAME UI and away it went. I now get the "extended" set of sliders. The ones that control the bloom and saturation, distortion and masks, and more.
The exact integrated graphics chip is the Iris Plus 655 w/128MB eDRAM. Not Iris Pro, my bad.
I didn't have any luck with BGFX or GLSL. Just D3D. But I'm quite ok with that. The i7-8559U still gives hundreds or even thousands of % above normal framerate if you let it run unthrottled.
I will experiment around with BGFX and OpenGL more - for fun. Maybe I'm doing something wrong there or something.
|
|
|
|
Re: Mame 0.217 doesn't work with Intel IrisPro Graphics [with shaders enabled]
[Re: Keatah]
#384934 - 01/06/20 02:32 PM
|
|
|
Great to hear that D3D is working!
BGFX, I'm really not sure what's going on there. It could just be that the BGFX library doesn't support Iris Plus graphics. Since it's a 3rd-party library, we don't have much control over it.
I think you might have mentioned it earlier in the thread, but what OS are you running?
|
|
|
|
Re: Mame 0.217 doesn't work with Intel IrisPro Graphics [with shaders enabled]
[Re: MooglyGuy]
#384939 - 01/06/20 09:27 PM
|
|
|
|
|
Previous 
Index 
Next 
Threaded 
Mame 0.217 doesn't work with Intel IrisPro Graphics [with shaders enabled]
Reply
[Re: 