[Scummvm-tracker] [ScummVM :: Bugs] #17305: ANDROID: Mouse support issue on Amerzone testing version (2026.3.1git32032-g71cb05b1c03) (was: Mouse support issue on Amerzone with the android testing version (2026.3.1git32032-g71cb05b1c03))
ScummVM :: Bugs
trac at scummvm.org
Wed Oct 7 18:40:33 UTC 2026
#17305: ANDROID: Mouse support issue on Amerzone testing version
(2026.3.1git32032-g71cb05b1c03)
----------------------+----------------------------
Reporter: cartman69 | Owner: (none)
Type: defect | Status: new
Priority: normal | Component: Port: Android
Version: | Resolution:
Keywords: | Game:
----------------------+----------------------------
Changes (by antoniou79):
* component: Engine: PhoenixVR => Port: Android
* summary:
Mouse support issue on Amerzone with the android testing version
(2026.3.1git32032-g71cb05b1c03)
=>
ANDROID: Mouse support issue on Amerzone testing version
(2026.3.1git32032-g71cb05b1c03)
Comment:
This is also an issue on Myst 3 (that I tested today, coincidentally, for
another bug report on the forums), which also uses mouse movement to pan
the image per "bubble" node.
So it's not specific to PhoenixVR games.
I am also quite sure that this was working (on Myst 3) for using a
physical mouse, but still not quite right, a while back when I also
addressed the lack of this support on the touchpad / direct mouse modes.
So it's probably some regression.
The "not quite right" part refers to the limitation, that seemed to come
from Android itself, that mouse could not be moved infinitely outside the
borders of the screen. At some point it would stop "moving" and thus you
could not spin the image indefinitely (maybe not even up to a full
circle), but you'd need to somehow reset / center the mouse position
first. Anyway, I remember not being too happy about it, but not really
finding a smart way to resolve that either.
--
Ticket URL: <https://bugs.scummvm.org/ticket/17305#comment:1>
ScummVM :: Bugs <https://bugs.scummvm.org>
ScummVM
More information about the Scummvm-tracker
mailing list