summaryrefslogtreecommitdiffstatshomepage
path: root/docs/source/commandline/windowsconfig.rst
blob: 1c41476854ca444505c0d311dc945ed042df751f (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
Windows-Specific Command-line Options
=====================================

This section contains configuration options that are specific to the native
(non-SDL) Windows version of MAME.



Performance options
-------------------

.. _mame-wcommandline-priority:

**-priority** *<priority>*

    Sets the thread priority for the MAME threads. By default the priority is
    left alone to guarantee proper cooperation with other applications. The
    valid range is -15 to 1, with 1 being the highest priority. The default is
    *0* (*NORMAL priority*).

.. _mame-wcommandline-profile:

**-profile** *[n]*

    Enables profiling, specifying the stack depth of *[n]* to track.


Full screen options
-------------------

.. _mame-wcommandline-triplebuffer:

**-[no]triplebuffer** / **-[no]tb**

    Enables or disables “triple buffering”.  Normally, MAME just draws directly
    to the screen, without any fancy buffering.  But with this option enabled,
    MAME creates three buffers to draw to, and cycles between them in order.  It
    attempts to keep things flowing such that one buffer is currently displayed,
    the second buffer is waiting to be displayed, and the third buffer is being
    drawn to. **-triplebuffer** will override **-waitvsync**, if the buffer is
    successfully created.  This option does not work with **-video gdi**. The
    default is OFF (**-notriplebuffer**).

.. _mame-wcommandline-fullscreenbrightness:

**-full_screen_brightness** *<value>* / **-fsb** *<value>*

    Controls the brightness, or black level, of the entire display.  The
    standard value is 1.0.  Lower values (down to 0.1) will produce a darkened
    display, while higher values (up to 2.0) will give a brighter display.  Note
    that not all video cards have hardware to support this option.  This option
    does not work with **-video gdi**.  The default is *1.0*.

.. _mame-wcommandline-fullscreencontrast:

**-full_screen_contrast** *<value>* / **-fsc** *<value>*

    Controls the contrast, or white level, of the entire display.  The standard
    value is 1.0.  Lower values (down to 0.1) will produce a dimmer display,
    while higher values (up to 2.0) will give a more saturated display.  Note
    that not all video cards have hardware to support this option.  This option
    does not work with **-video gdi**.  The default is *1.0*.

.. _mame-wcommandline-fullscreengamma:

**-full_screen_gamma** *<value>* / **-fsg** *<value>*

    Controls the gamma, which produces a potentially nonlinear black to white
    ramp, for the entire display.  The standard value is 1.0, which gives a
    linear ramp from black to white.  Lower values (down to 0.1) will increase
    the nonlinearity toward black, while higher values (up to 3.0) will push the
    nonlinearity toward white.  Note that not all video cards have hardware to
    support this option.  This option does not work with **-video gdi**.  The
    default is *1.0*.



Input device options
--------------------

.. _mame-wcommandline-duallightgun:

**-[no]dual_lightgun** / **-[no]dual**

    Controls whether or not MAME attempts to track two lightguns that appear as
    a single mouse.  This option requires the :ref:`lightgun option
    <mame-commandline-nolightgun>` to be on and the :ref:`lightgunprovider
    option <mame-commandline-lightgunprovider>` to be set to *win32*.

    This option supports certain older dual lightgun setups that work by setting
    the mouse pointer location at the moment a lightgun trigger is activated.
    The primary and secondary triggers on the first lightgun correspond to the
    first and second mouse buttons, and the primary and secondary triggers on
    the second lightgun correspond to the third and fourth mouse buttons.

    If you have multiple lightguns connected, you will probably just need to
    enable the :ref:`lightgun option <mame-commandline-nolightgun>`, use the
    default :ref:`lightgunprovider option <mame-commandline-lightgunprovider>`
    of *rawinput*, and configure each lightgun individually.

    The default is OFF (**-nodual_lightgun**).