http://bugs.winehq.org/show_bug.cgi?id=10382
Summary: Tribes 2: must double-tap for in game chat Product: Wine Version: 0.9.48. Platform: Other OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: wine-directx-dinput AssignedTo: wine-bugs@winehq.org ReportedBy: spock128@gmail.com
When in game, the chat keys must be pressed twice after the first use. For example, I can press 'u' (global chat) once to bring up a text entry box to say something in the global channel (correct operation). After that, I must hit 'u' twice to bring up the text entry box. In-game console shows the error:
DInputDevice::syncKeyboardState - DIERR_INVALIDPARAM
Switching out of the game window and back will reset the condition - it works for first use then must hit twice.
http://bugs.winehq.org/show_bug.cgi?id=10382
--- Comment #1 from Vitaliy Margolen vitaliy@kievinfo.com 2007-11-11 00:02:05 --- Can you try native dinput.dll to check if it has the same problem or not? Also attach (as a file) output with WINEDEBUG=+dinput,+event.
http://bugs.winehq.org/show_bug.cgi?id=10382
--- Comment #2 from spock128@gmail.com 2007-11-15 11:37:35 --- Created an attachment (id=9170) --> (http://bugs.winehq.org/attachment.cgi?id=9170) builtin dinput.dll debug output
http://bugs.winehq.org/show_bug.cgi?id=10382
--- Comment #3 from spock128@gmail.com 2007-11-15 11:38:33 --- Created an attachment (id=9171) --> (http://bugs.winehq.org/attachment.cgi?id=9171) native dinput.dll debug output
http://bugs.winehq.org/show_bug.cgi?id=10382
--- Comment #4 from spock128@gmail.com 2007-11-15 11:39:36 --- Using the native dinput.dll, chat operates correctly.
http://bugs.winehq.org/show_bug.cgi?id=10382
Lei Zhang thestig@google.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #9170|application/octet-stream |text/plain mime type| |
http://bugs.winehq.org/show_bug.cgi?id=10382
--- Comment #5 from Austin English austinenglish@gmail.com 2008-06-16 16:07:46 --- Is this still an issue in current (1.0-rc5 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=10382
spock128@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #9170 is|0 |1 obsolete| |
--- Comment #6 from spock128@gmail.com 2008-06-16 21:01:33 --- Created an attachment (id=14122) --> (http://bugs.winehq.org/attachment.cgi?id=14122) builtin dinput.dll debug output
testing again with wine 1.0-rc5:
the problem still exists, although the behavior has changed slightly. The DIERR_INVALIDPARAM message no longer appears in the game console.
However, double-tapping is still required for chatting. Furthermore, when it does respond with one keypress, the key (occasionally multiple keys) to the left will be entered into the keypress stream.
For example, in the debug log attached, I rebound the "fire weapon" key to 't'.
After starting the game, I hit the 'u' key to global chat and entered the phrase "first message". Afterward, both the team chat box comes up and I start firing. I enter a message and I stop firing. Then I hit 'y' to team chat, enter a message and start firing again. In all cases, the message contained the letter 't'.
Like before, using a native dinput.dll fixed everything.
http://bugs.winehq.org/show_bug.cgi?id=10382
--- Comment #7 from Austin English austinenglish@gmail.com 2008-12-15 13:55:30 --- Is this still an issue in current (1.1.10 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=10382
spock128@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #14122|0 |1 is obsolete| |
--- Comment #8 from spock128@gmail.com 2008-12-15 20:50:40 --- Created an attachment (id=17978) --> (http://bugs.winehq.org/attachment.cgi?id=17978) builtin dinput.dll debug output
Yes, behavior is the same as for 1.0-rc5 (using 1.1.10)
After some further experimentation, it looks like the specific chat message entered has no bearing on which extraneous keys are being reported.
http://bugs.winehq.org/show_bug.cgi?id=10382
--- Comment #9 from Austin English austinenglish@gmail.com 2009-06-16 14:21:33 --- Is this still an issue in current (1.1.23 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=10382
spock128@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 |P4 Version|0.9.48. |1.1.24
--- Comment #10 from spock128@gmail.com 2009-06-22 22:00:50 --- Bug behavior is unchanged (wine 1.1.24)
http://bugs.winehq.org/show_bug.cgi?id=10382
spock128@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Platform|Other |PC-x86-64
http://bugs.winehq.org/show_bug.cgi?id=10382
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|1.1.24 |0.9.48.
--- Comment #11 from Dmitry Timoshkov dmitry@codeweavers.com 2009-06-23 03:38:37 --- Adding a comment is enough.
http://bugs.winehq.org/show_bug.cgi?id=10382
--- Comment #12 from Austin English austinenglish@gmail.com 2010-01-04 12:16:47 --- This is your friendly reminder that there has been no bug activity for 6 months. Is this still an issue in current (1.1.35 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=10382
--- Comment #13 from spock128@gmail.com 2010-01-09 21:24:44 --- There is no change when using wine 1.1.35.
Though I doubt it's worth the effort by now - the game isn't played much anymore. Even Vista doesn't run it correctly.
http://bugs.winehq.org/show_bug.cgi?id=10382
--- Comment #14 from Austin English austinenglish@gmail.com 2011-03-29 19:30:46 CDT --- This is your friendly reminder that there has been no bug activity for 6 months. Is this still an issue in current (1.3.16 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=10382
--- Comment #15 from spock128@gmail.com 2011-03-29 21:45:56 CDT --- no change in wine 1.3.16
http://bugs.winehq.org/show_bug.cgi?id=10382
--- Comment #16 from butraxz@gmail.com 2013-09-15 07:47:48 CDT --- This ticket has not been updated for over 900 days. Development recommends to check the status on your bug every release or two and let to be known if the bug is still present. If not, mark it fixed. If you are no longer able to put effort to this ticket, you can abandon it.
Is this still an issue with 1.7.2 or higher ?
https://bugs.winehq.org/show_bug.cgi?id=10382
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |ABANDONED
--- Comment #17 from Austin English austinenglish@gmail.com --- Abandoned.
https://bugs.winehq.org/show_bug.cgi?id=10382
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #18 from Austin English austinenglish@gmail.com --- Closing.