Opened 5 years ago
Closed 3 years ago
#11224 closed defect (fixed)
BACKENDS: Android - Right Click doesn't work in Beavis & Butthead - Virtual Stupidity
Reported by: | IXG4MEOVERXI | Owned by: | antoniou79 |
---|---|---|---|
Priority: | normal | Component: | Port: Android |
Version: | Keywords: | Right Click, Beavis & Butthead, Virtual Stupidity | |
Cc: | IXG4MEOVERXI | Game: | Beavis & Butthead Virtual Stupidity |
Description
ScummVM version (2.1.0 - Android )
Bug details, including step-by-step instructions to reproduce the bug
Language of game (English)
Version of game (CD)
Samsung Note 10+ (OS: Android Pie (9)) One UI version 1.5
How to replicate:
Start game, then when in the game, try to right click (holding down one finger and tapping with the other, and the in-game action menu will flicker. It is impossible to select another option to choose from, making the game unplayable.
Note: 1. I have tested other games like Blade Runner and this works fine.
- The game is only playable on android if phone is connect to PC, using Samsung DEX. This allows the user to actually use a proper mouse, when allows the right click to work. Touch controls do not however.
Change History (4)
comment:1 by , 4 years ago
Summary: | Right Click doesn't work (Beavis & Butthead - Virtual Stupidity) → BACKENDS: Android - Right Click doesn't work in Beavis & Butthead - Virtual Stupidity |
---|
comment:2 by , 4 years ago
Priority: | high → normal |
---|
comment:3 by , 4 years ago
Owner: | set to |
---|---|
Resolution: | → pending |
Status: | new → pending |
comment:4 by , 3 years ago
Resolution: | pending → fixed |
---|---|
Status: | pending → closed |
Closing this as fixed (as far as I can tell, and due to lack of feedback).
This should be fixed in 2.3.0git by commit:
https://github.com/scummvm/scummvm/commit/987becc5297b29fd8fb30c43aff25105e917bc08
Also look at bug report ticket for a similar issue (that should be resolved with the same commt) with the Tony Tough game:
https://bugs.scummvm.org/ticket/12011
I do have one or two things that I'm thinking about improving upon the fix, to make the behavior somewhat more intuitive if possible, but the issue should be considered resolved anyway.
Awaiting for feedback from anyone who tests with developer builds.