ui/analogipt.cpp: Fixed bar graph display for fields with ranges
that wrap through zero.
emu/inputdev.cpp: Separateed analog axis deadzone and switch threshold
settings, reduced default deadzone, and fixed a potential division by
zero if the deadzone and saturation settings are equal.
emu/ioport.cpp: Fixed behaviour of absolute analog fields where range
passes through zero - it previously only worked for specific
combinations of mask, minimum and default. Removed a workaround from
universal/getaway.cpp that is no longer necessary.
emu/input.cpp: Fixed unintuitive behaviour when an absolute field is
assigned an OR combination of a relative control folled by an absolute
control (e.g. Mouse X or Joy 1 LSX). Also fixed reading axis input
sequences where an axis code is followed by a switch code (these can
only be produced by manually editing configuration files, not through
MAME's UI), and fixed the returned type when multiple relative axes sum
to zero.
osd/modules/input_dinput.cpp: Fixed hat switches being stuck in up
position when input is suspended in the background
taito/taitoio_yoke.cpp: Give throttle control a distinct type, and don't
auto-centre.
osd: Added option to select MIDI provider module (currently only
PortMidi and the dummy module are available). Also put various things
in namespaces, and fixed builds including SDL sound module with native
Windows OSD.
emu/validity.cpp: Added check to catch I/O port fields using UI input
types.
emu/inpttype.ipp: Renamed inputs that were causing confusion. "Bill"
and "Track" were causing confusion for translators and hence likely
causing confusion for many users, especially those who are not native
English speakers. "Track" as an abbreviation for "Trackball" was
frequently being mistranslated, e.g. in the sense of a CD track
selection button or even in the sense of a railway track. There's no
reason to abbreviate it. "Bill" in the US English sense as a banknote
is too ambiguous and was causing confusion for translators. It's better
to use the less ambiguous "Banknote". Corrected Greek translations of
"Trackball".
Don't run GitHub Actions on issue template changes.
..[#JIPAutoWindows] On Windows, auto will default to ``winhybrid``.
..[#JIPAutoWindows] On Windows native, auto will default to ``winhybrid``.
..[#JIPAutoSDL] On SDL, auto will default to ``sdlgame``.
@ -1002,6 +1002,21 @@ Example:
mame mk2 -joystickprovider winhybrid
.._mame-commandline-midiprovider:
**-midiprovider***<module>*
Chooses how MAME will communicate with MIDI devices and applications (e.g.
music keyboards and synthesisers). Supported options are ``pm`` to use the
PortMidi library, or ``none`` to disable MIDI input and output (MIDI files
can still be played). The default is ``auto``, which will use PortMidi if
available.
Example:
..code-block:: bash
mame -midiprovider none dx100 -midiin canyon.mid
.._mame-commandline-cliverbs:
@ -2092,35 +2107,35 @@ Core Video Options
Generally Available:
| Using ``bgfx`` specifies the new hardware accelerated renderer.
|
| Using ``opengl`` tells MAME to render video using OpenGL acceleration.
|
| Using ``none`` displays no windows and does no drawing. This is primarily present for doing CPU benchmarks without the overhead of the video system.
|
* Using ``bgfx`` specifies the new hardware accelerated renderer.
* Using ``opengl`` tells MAME to render video using OpenGL acceleration.
* Using ``none`` displays no windows and does no drawing. This is primarily
intended for benchmarking emulation without the overhead of the video
system.
On Windows:
| Using ``gdi`` tells MAME to render video using older standard Windows graphics drawing calls. This is the slowest but most compatible option on older versions of Windows.
|
| Using ``d3d`` tells MAME to use Direct3D for rendering. This produces the better quality output than ``gdi`` and enables additional rendering options. It is recommended if you have a semi-recent (2002+) video card or onboard Intel video of the HD3000 line or better.
|
* Using ``gdi`` tells MAME to render video using older standard Windows
graphics drawing calls. This is the slowest but most compatible option on
older versions of Windows or buggy graphics hardware drivers.
* Using ``d3d`` tells MAME to use Direct3D9 for rendering. This produces
better quality output than ``gdi`` and enables additional rendering
options. It is recommended if you have a 3D-capable video card or onboard
Intel video of the HD3000 line or better.
On other platforms (including SDL on Windows):
| Using ``accel`` tells MAME to render video using SDL's 2D acceleration if possible.
|
| Using ``soft`` uses software rendering for video output. This isn't as fast or as nice as OpenGL but will work on any platform.
|
* Using ``accel`` tells MAME to render video using SDL’s 2D acceleration if
possible.
* Using ``soft`` uses software rendering for video output. This isn’t as
fast or as nice as OpenGL, but it will work on any platform.
Defaults:
| The default on Windows is ``d3d``.
|
| The default for Mac OS X is ``opengl`` because OS X is guaranteed to have a compliant OpenGL stack.
|
| The default on all other systems is ``soft``.
|
* The default on Windows is ``d3d``.
* The default for macOS is ``opengl`` because OS X is guaranteed to have a
Vas Crabb
10 months ago