path: root/docs
diff options
authorGravatarGravatar Firehawke <>2018-10-19 16:47:47 -0700
committerGravatarGravatar Firehawke <>2018-10-19 16:47:47 -0700
commitae97f80cb3be8b9326d58f4676f2f6d8a78b2622 (patch) (github)
tree2092c784f789b120a978b7591c1f0a3ec613377f /docs
parent6a07b0151925be20af650a658c37dedec62d80cf (diff)
Update FAQ (nw) with HLSL/BGFX update info, old external OPL2 support information
Diffstat (limited to 'docs')
1 files changed, 13 insertions, 3 deletions
diff --git a/docs/source/usingmame/commonissues.rst b/docs/source/usingmame/commonissues.rst
index f8d5602cbe9..2cd6c63b0b6 100644
--- a/docs/source/usingmame/commonissues.rst
+++ b/docs/source/usingmame/commonissues.rst
@@ -24,7 +24,7 @@ Common Issues and Questions (FAQ)
18. :ref:`Ultracade`
19. :ref:`Blackscreen-DirectX`
20. :ref:`ControllerIssues`
+21. :ref:`ExternalOPL`
.. _rapid-coins:
@@ -39,13 +39,15 @@ In either case, the game would display an error for the operator to look into th
.. _broken-package:
-Why is my non-official MAME package (e.g. EmuCR build) broken?
+Why is my non-official MAME package (e.g. EmuCR build) broken? Why is my official update broken?
In many cases, updates to various subsystems such as HLSL, BGFX, or Lua plugins come as updates to the external shader files as well as to the core MAME code. Unfortunately, builds that come from third parties may come as just a main MAME executable or with outdated external files, which can break the coupling between these external files and MAME core code. Despite repeated attempts at contacting some of these third parties to warn them, they persist in distributing broken MAME updates.
As we have no control over how third parties distribute these, all we really can do is disclaim the use of sites like EmuCR and say that we cannot provide support for packages we didn't build. Compile your own MAME or use one of the official packages provided by us.
+You may also run into this problem if you fail to update the HLSL or BGFX folders when you update your MAME install with a new official build.
.. _faster-if-X:
@@ -233,3 +235,11 @@ By default, MAME on Microsoft Windows tries to do raw reads of the joystick(s),
One thing you can try is setting the keyboardprovider, mouseprovider, or joystickprovider setting (depending on which kind of device your input device acts as) from rawinput to one of the other options such as dinput or win32. See :ref:`osd-commandline-options` for details on supported providers.
+.. _ExternalOPL:
+What happened to the MAME support for external OPL2-carrying soundcards?
+MAME added support in version 0.23 for the use of a soundcard's onboard OPL2 (Yamaha YM3812 chip) instead of emulating the OPL2. This feature was never supported on the official Windows version of MAME and was dropped entirely as of MAME 0.60 because the OPL2 emulation in MAME had gotten advanced enough to be a better solution in almost all cases as of that time; now it's superior to using a soundcard YM3812 in all cases.
+Unofficial builds of MAME may have supported it for varying amounts of time as well. \ No newline at end of file