wyora

Mouse clicks not working on EverQuest 64-bit servers

Mouse clicks not working on EverQuest 64-bit servers

I use Multiplicy KVM to play EverQuest on multiple computers, and with the recent EQ upgrade to 64-bit servers, Multiplicity is "broken" now. Keyboard works fine, but if I use the mouse to move (right click) or look around (left click), it duplicates that action on all other connected computers. This was happening on the Test server several weeks ago, and is now happening on the Live server after today's patch/update. I'm not the only person having this issue.


Update: If EQ has indeed prevented Multiplicity from functioning properly, there is nothing we can do about it.


Update: The changes for EQ were incorporated into Multiplicity 3.60


You can review the thread history for context.

Sean Drohan
Stardock Support Manager

264,814 views 104 replies | Pinned
Reply #101 Top

Quoting redmace, reply 102

Let me repost the ORIGINAL post for this issue.  As I said.  This has NOT been fixed.  It is still happening and after your FIX it is doing the same thing not only in Everquest but in any program that steals focus on the primary computer.    So one more time, your calling this fixed, even though several people are still having the same issue.  Just wanting to confirm this.


I use Multiplicy KVM to play EverQuest on multiple computers, and with the recent EQ upgrade to 64-bit servers, Multiplicity is "broken" now. Keyboard works fine, but if I use the mouse to move (right click) or look around (left click), it duplicates that action on all other connected computers. This was happening on the Test server several weeks ago, and is now happening on the Live server after today's patch/update. I'm not the only person having this issue.


 

I am sorry you are experiencing problems.

As requested please post in your own thread as you are having issues which are not being experienced by others so that support may assist you further.

The original post was specifically about everquest.  This issue has been resolved as confirmed by multiple users and on our test systems and we know the exact cause and the exact solution.  Given your report of it happening with multiple applications it is extremely likely there is another factor involved here a not a single person has reported similar thus personal support in your own thread is the correct course of action.

Please also be aware I am not technical support.

 

Reply #102 Top

This issue is now considered resolved and this thread will be closed.

Sean Drohan
Stardock Product Lifecycle Manager