Mr. Do![Administrator Administrator](//www.mameworld.info/ubbthreads/images/adm.gif) |
MAME Art Editor
|
|
|
Reged: 09/21/03
|
Posts: 4887
|
Loc: California
|
|
Send PM
|
|
|
|
So a few weeks ago a made a comment about the learning curve of bgfx/hlsl etc., but that it was also my own fault for not reading up on stuff. So a did a little bit of reading...
It's both simple and complicated... for everyday Joe, you make a few changes to your INI file, and you have a really nice "out of the box" solution. And then for the advanced user, there are lots of tweaks you can do on your own if you please.
Mad props to MAME team members that have put in the time on this to make it more user friendly.
I found this short little guide here:
https://forums.launchbox-app.com/topic/33564-mame-bgfx-shaders-tutorial/
And from that, I was able to make it work real pretty like with just a couple changes to my INI file:
-- video bgfx -- bgfx_screen_chains crt-geom,crt-geom,crt-geom
Just with that simple change... everything looks great.
With that... I had a question:
1) I've had a few drivers crash with errors that start similar to below...
----------------------------------------------------- Exception at EIP=0000000003a427fc (chain_manager::update_screen_textures(unsigned int, render_primitive*, osd_window&)+ x03bc): ACCESS VIOLATION While attempting to read memory at ffffffffffffffff -----------------------------------------------------
... specifically snes, genesis, breakout. Is this likely something on my side, like with my video card? Or something else? (Hoping to get something up to date next year).
Running on my laptop right now, which is a Latitude e6540; video is Intel 4600 + Radeon 8790M.
[ATTACHED IMAGE - CLICK FOR FULL SIZE]
|
RELAX and just have fun. Remember, it's all about the games.
|
|
|
Re: bgfx is awesome!! Got some questions...
[Re: Mr. Do]
#384380 - 11/25/19 08:54 AM
|
|
|
There were some bgfx issues which were fixed since 0.215 was released, including crash with drivers changing resolution. Can you try checking if your issue is still present in git master? Otherwise you can try different backends as an attempt to work around the problem (-bgfx_backend). On windows you have the following options: dx9, dx11, dx12, opengl and vulkan.
|
|
|
|
Re: bgfx is awesome!! Got some questions...
[Re: belegdol]
#384381 - 11/25/19 09:06 AM
|
|
|
> There were some bgfx issues which were fixed since 0.215 was released, including > crash with drivers changing resolution. Can you try checking if your issue is still > present in git master? > Otherwise you can try different backends as an attempt to work around the problem > (-bgfx_backend). On windows you have the following options: dx9, dx11, dx12, opengl > and vulkan.
Note that if you want to use Vulkan you should really install the latest video card drivers. I got crashes with Vulkan with the latest NVIDIA drivers from Windows Update that were resolved by installing the latest from NVIDIA themselves.
|
|
|
|
Re: bgfx is awesome!! Got some questions...
[Re: Mr. Do]
#384382 - 11/25/19 10:05 AM
|
|
|
> 1) I've had a few drivers crash with errors that start similar to below... > > ----------------------------------------------------- > Exception at EIP=0000000003a427fc (chain_manager::update_screen_textures(unsigned > int, render_primitive*, osd_window&)+ > x03bc): ACCESS VIOLATION > While attempting to read memory at ffffffffffffffff > ----------------------------------------------------- > > ... specifically snes, genesis, breakout. Is this likely something on my side, like > with my video card? Or something else? (Hoping to get something up to date next > year).
Known issue with 0.215, resolved for the upcoming 0.216 release. There are a few other issues with the BGFX backend in 0.215 that have since been resolved for 0.216:
- MAME crashes when running laserdisc games. - If it doesn't crash, the OpenGL backend just shows a 2x2 grid of huge pixels for Laserdisc games. - Brightness/Contrast/Gamma adjusters don't work. - The "none" screen chain doesn't work for certain games. - Game & Watch games are heavily glitched on the primary screen. This has not yet been fully fixed, the shadow pass still does not appear for the primary screen, but it works fine if you specify -bgfx_screen_chains none,none,none,none in order to avoid the post-processing passes.
|
|
|
|