Diff: Updates.h

Revision:

39:b3815a1c3802

Parent:

35:e959ffba78fd

Child:

40:cc0d9814522b

--- a/Updates.h	Tue Jan 05 05:23:07 2016 +0000
+++ b/Updates.h	Mon Jan 11 21:08:36 2016 +0000
@@ -29,4 +29,49 @@
 // moving at high speed, allowing for more realistic plunger action on the
 // virtual side.
 //
-// 
+// Keyboard mappings for buttons: button inputs can now be mapped to keyboard
+// keys.  Joystick buttons are of course also still supported.  Some software on
+// the PC side is easier to configure for keyboard input than for joystick
+// input, so many users might prefer to map some or all buttons to keys.  If
+// you map any buttons to keyboard input, the controller device will have
+// two entries in the Windows Device Manager list, one as a joystick and
+// the other as a keyboard.  This is automatic; the keyboard interface will
+// appear automatically if you have any keyboard keys mapped, otherwise only
+// the joystick interface will appear.
+//
+// "Pulse" buttons: you can now designate individual button inputs as pulse
+// mode buttons.  When a button is configured in pulse mode, the software
+// translates each ON/OFF or OFF/ON transition in the physical switch to a
+// short virtual key press.  This is especially designed to make it easier
+// to wire a coin door switch, but could be used for other purposes as well.
+// For the coin door, the VPinMAME software uses the End key to *toggle* the
+// open/closed state of the door in the simulation, but it's much easier
+// to wire a physical on/off switch to the door instead.  Pulse mode bridges
+// this gap by translating the on/off switch state to key presses.  When
+// you open the door, the switch will go from OFF to ON, so the controller
+// will send one short key press, causing VPinMAME to toggle the simulated
+// door to OPEN.  When you close the door, the switch will go from ON to
+// OFF, which will make the controller send another short key press, which
+// in turn will make VPinMAME toggle the simulated door state to CLOSED.
+// There are other ways to solve this problem (VP cab builders have come
+// up with various physical devices and electronic timer circuits to deal
+// with it), but the software approach implemented here is a lot simpler
+// to set up and is very reliable.
+//
+// Night mode: you can now put the device in "night mode" by configuring a 
+// physical button input to activate the mode, or by sending a command from
+// the PC config tool software.  When night mode is activated, outputs that
+// you designate as "noisemaker" devices are disabled.  You can designate
+// any outputs as noisy or not.  This feature is designed to let you use your
+// virtual pinball machine during quiet hours (e.g., late at night) without
+// disturbing housemates or neighbors with noise from flippers, knockers,
+// shaker motors, and so on.  You can designate outputs individually as
+// noisy, so you can still enjoy the rest of your feedback features during
+// night play (e.g., flashers and other lighting effects).
+//
+// USB fixes: the low-level USB device code had some serious bugs that only
+// very occasionally manifested in past versions, but became much more
+// frequently triggered due to other changes in this release (particularly
+// the USB keyboard input feature).  These should now be fixed, so the USB
+// connection should now be very reliable.
+//