Descriptive Problem Summary:
Single clicks on atoms are not recognized by Dream Seeker but are recognized by the webclient. Doubleclicks register as two single clicks and as a doubleclick.
Single clicks register properly for menus, in the text field, etc.
Cannot be a hardware issue because the mouse works perfectly (with about two seconds lag, like everything else in the webclient) in the webclient.
See also https://github.com/d3athrow/vgstation13/issues/11206
Issue occurs in 510.1347, 511.1350, 511.1352.
Numbered Steps to Reproduce Problem:
1. Connect via Dream Seeker
2. Click an atom
3. Nothing happens
4. Connect via webclient
5. Click an atom
6. Something happens (if clicking is supposed to do something)
Expected Results:
Clicking does something.
Actual Results:
Absolutely nothing happens.
Does the problem occur:
Every time? Or how often?
Every time.
In other games?
There are no other games worth playing.
Issue occurred when tested on TGstation, /vg/station, and the /vg/station test server.
In other user accounts?
On other computers?
Others are encountering this issue: https://github.com/d3athrow/vgstation13/issues/11246
When does the problem NOT occur?
In the webclient.
Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit http://www.byond.com/download/build to download old versions for testing.)
Previously worked fine in an earlier version of 511, and in 510.1347. Stopped working for no apparent reason: Did not update BYOND, Windows, hardware drivers, or browsers, nor change any other settings that seem possibly related to the issue. Did not test downdating stable BYOND because all stable versions predate the issue and worked fine before July 26th.
Workarounds:
Usage of the webclient.
ID:2130413
Aug 11 2016, 1:58 pm
|
|||||||||||||
| |||||||||||||
Aug 11 2016, 1:59 pm
|
|
Correction, Firefox version is 47.0.1, forgot I had that scrambled.
|
This is a system-specific issue that has happened to some SS13 users. As far as I can tell, your system is incorrectly sending the wrong messages to the window, and that's what's causing this problem.
|
Are you saying you need more information, or that you are unable to solve the issue? Or do you believe the issue is in some piece of SS13 code?
|
I don't know. All I know is, the wrong messages must be getting sent to the window, because the way BYOND handles clicks shouldn't make this possible. Other users have had this issue, and while it appears to be happening just to SS13 users I think that's just a coincidence.
|
I consistently get this in WINE on linux when running DreamSeeker or DreamMaker (map editor) on a secondary monitor. Maybe it's something similar on windows?
|
IIRC one of the other users who mentioned this had an issue with secondary monitors.
|
http://www.byond.com/forum/?post=2024193
http://www.byond.com/forum/?post=2045958 edit: I just did the testing I said I'd do in the first link above; this definitely looks DM issue and not a Windows/Wine/Linux/etc one, at least on my system; Code: /world Output (my comments after the //) MouseDown // Double click, primary monitor |
As of this morning I no longer encounter this issue. I did not update BYOND, IE, windows, firefox, or do anything at all.
|