|
Re: Got a message asking me to report to mame developpers
08/25/17 04:46 AM
|
|
|
> If the Direct3D drivers for these GPUs dont support the necessary features but the > OpenGL and GDI options do work, maybe the answer is to detect the lack of support on > Direct3D and either A.Switch to OpenGL or GDI mode (possibly with a message saying > something like "Direct3D not supported on this hardware, switching to OpenGL mode" or > something) or B.Print a message and then give people the option to pick OpenGL/GDI > mode.
The argument is the fact that MAME worked perfectly with Direct3D all the way up until 0.180 where the D3D stuff was abruptly changed for no apparent reason (it was not for compatibility with new video cards, they worked just fine with older versions of MAME up to and including 0.179).
> That way its clear that MAME doesn't work in Direct3D mode on that hardware and that > MAME will work just fine in the other modes (and also the user doesn't need to do > anything difficult or special to switch to a mode that will work)
Code can coexist, it doesn't have to be deleted in its entirety so that another piece of code can be added - if it ain't broke, don't fix it. This video code was changed simply for the sake of shiny code. I could understand if MAME was somehow bought out by Nintendo or Apple or whatever and they had to port the entire codebase (minus the games they can't license) to a completely incompatible device such as the Switch or iOS etc. and it didn't matter if the PC-based stuff was deleted entirely.
The next step would most likely be removing support for 32-bit CPUs, just for the sake of doing so of course, not because it would completely break MAME if they ever had to compile it for more than one CPU type, but because shiny code.
|
|