Updated Configuring touch screens as subscreen (markdown)

bicarus
2026-08-23 22:03:56 -07:00
parent a476fdc569
commit e16ffc3d05
-8
@@ -67,14 +67,6 @@ Do the same as above, but don't "lie" this time, let Windows know that your touc
Touch monitors are finicky things, and a lot of the times, devices do not properly implement the correct touch API needed, resulting in missed touches, duplicated touches, inability to use multi-touch, not recognizing taps, not recognizing swipes, etc. It's the wild wild west out there, but Spice has a few options to deal with them.
### Workaround for touches not registering properly (-iidxnativetouch / -sdvxnativetouch)
If you have issues with touches not registering properly (e.g., requiring "double tap" for touches to register, swipes not working, etc), use `IIDX native touch handling (-iidxnativetouch)` or `SDVX native touch handling (-sdvxnativetouch)` options.
* As a side effect, mouse support will be disabled; i.e., clicking with your mouse will no longer register as touches.
* Not all monitors need this, but turning it on is safe for all monitors.
Note: as of `spice2x-26-07-24` this is no longer needed; things should just work.
### Refresh rate issues
Assuming you have a 120Hz monitor as the primary monitor and 60Hz monitor as the sub screen, if you forcibly enable V-Sync, the game may incorrectly launch at 60Hz on both screens. To fix this, make sure to use default V-Sync settings. For example, in NVIDIA Control Panel, you want to set V-Sync settings to `Use the 3D application setting`. You also need to ensure that FreeSync and G-Sync are **OFF**.