> > > > Many thanks for working on this! I'm pretty sure that this will indeed become > > very > > > > popular on YT soon for those that are capturing MAME footage . > > > > > > > > Is this a D3D exclusive and does it also require some specific > bgfx_screen_chains > > > > with HLSL or can it be used with OpenGL as will for older systems? > > > > > > > > I’m really looking forward to v0.173 or later when this is officially added to > > the > > > > source. Best regards. > > > > > > Not to try and speak for MG, but this has nothing to do with D3D. This is showing > > off > > > BGFX in action. > > > > > > If you're on 0.172 you can run with -video bgfx -bgfx_screen_chains hlsl and TAB > > into > > > the sliders flipping Enable Adjustments to On > > > > > > This way you can at the very least see if it works on your system if you wish to > > try > > > it. > > > > > > Thanks for the reply. I tested bgfx the way you mentioned when 0.172 was released > out > > of curiosity (for example: "mame.exe -video bgfx -bgfx_screen_chains hlsl wboy" and > > it works fine that way but a bit slow on my system. > > > > I'm just having problems to get it work with the glsl shader that I'm using and I'm > > also running MAME in OpenGL mode since my video drivers and system runs much better > > with that renderer. MAME bgfx documents mentions that it is possible to use opengl > as > > bgfx_backend but I'm just not sure why it disables my glsl shader as well. > > > > > > I use HLSL and D3D on my main HTPC but for now I'm only limited to glsl and opengl > on > > my cab. It's not an ancient machine by any means but the CPU is my bottleneck as > well > > as the GPU (i5-2400S CPU ~2.5Ghz, 8GB RAM and GeForce GT 640, Win7x64). > > > > Best regards > > When you use -video bgfx you get access to only the "bgfx chains" in the bgfx\chains > folder. The older glsl and hlsl shader systems use different shaders > > This is regardless of the bgfx_backend. So you can now use the "hlsl" chain with > any/all of the bgfx backends. And that's really nice. Because shaders are now: write > one shader, available on all OS's > > But it also means that you can't run the older glsl shaders in bgfx. There is nothing > stopping anyone from porting the older shaders to the new system though. So if > someone ports crt-geom or whatever then you'd be able to use it with "-video bgfx". > But until someone does, well, you can't. > > I'm trying to get a simple scanline shader running in bgfx that runs at full speed on > my atom tablet. This weekend I'll either finish that up or give up and write one for > my faster surface pro 3. So there will be more choices for bgfx shader chains in the > future. > > And of course MooglyGuy has been porting shaders like crazy lately. So you'll have > those available too!
Thanks for the information, now I'm starting to understand how bgfx works. This sounds indeed great and will open up the door for lots of new shaders as well as many older shaders ported over in the near future. That was the main benefit of RetroArch and even some older MAME derivatives.
I've been reading about many of the changes in the recent MAME versions lately and it's really hard to keep up with the changes nowadays (http://docs.mamedev.org/) and it seems that MAME is now officially on a mission to destroy and kill all other MAME derivatives as will as many emulators and for some users even frontends by including many of the useful features but implementing it in a much better and future proof way. Many thanks to all the MAME devs for all their hard work!
My system runs HLSL just fine by it self but it seems much slower when running it through bgfx with "bgfx_screen_chains hlsl", hopefully it might be possible to improve the speed by optimization otherwise I just found a new excuse to upgrade my cabs hardware again
----
“Anyone who has never made a mistake has never tried anything new.” --Albert Einstein
Index 
Flat 
Re: A new shader for those who want to use their entire screen space
Reply
I did some changes. This is the way I like it.
