DMDX Help.

Input Device Keyword

<InputDevice text [N1[,N2[,N3]]]>
<id text [N1[,N2[,N3]]]>
<InputDevice tcpip [address[:port]]>
<id tcpip [address[:port]]>

    Parameter to select an input device. text must be the name of an existing installed DirectInput device (as enumerated by the TimeDX input test) or the name of one of the internal devices built into DMDX (see Input), such as "PIO12" (the built in MetraByte PIO12 (or clone) interface), "DigitalVOX", "RecordVocal" (see Audio Input) or "tcpip". Once a device is selected there is no way to deselect it without starting a new item file which can be done with the chain keyword, you can however unmap all the devices' buttons with <UnMapButtons>.  Names with spaces in them must be in quotes.

    One problem is devices having cute little symbols as part of the name making it very hard to get the name of a device into an item file.  To combat this version of DMDX dumps the names of available input devices into the diagnostics, not only that it also checks a parsed version of the name that has unusual characters removed from it that is also printed in brackets. 
<Testmode 10> can also be used to combat weird naming problems.

   Certain devices come with preinstalled button mappings, see Input and <MapRequest> etc.
    Certain operating systems preclude the use of certain input devices. Most notably Windows NT (not that anyone would want to use DMDX under it), Windows 2000 and Windows XP and later (Vista, Windows 7, 8 and 10) preclude the use of devices that involve direct access to I/O ports. While InstaCal drivers can be installed and used for the PIO12 devices no such thing was available for the RawJoystick device until version of DMDX where support for inpout32.dll was added (see the PIO test documentation for details, to use it you will first need to run InstallDriver.exe in the DMDX program folder with administrative access to install the ring 0 kernal mode driver interface for the DLL).


DMDX Index.