Mouselook issue is back playing everquest

They just patched the other day making windowed mode default and ever since mouse look on secondary boxes is transmitting to primary again. Only impacting everquest as far as i can tell and doing so in both windowed and fullscreen

10,038 views 14 replies
Reply #1 Top

Hello,

I have forwarded your report to the Stardock support team for their review and recommendations.

Please keep an eye on this thread for any updates.

We really do appreciate your feedback, thanks.

Reply #2 Top


They just patched the other day making windowed mode default and ever since mouse look on secondary boxes is transmitting to primary again. Only impacting everquest as far as i can tell and doing so in both windowed and fullscreen
End of quote

Please see:

https://forums.stardock.com/510351/get;3842229

Sean Drohan
Stardock Product Lifecycle Manager

Reply #3 Top

I have that build and since the patch its doing it again with that build, unless multiplicty auto updates and had a new build pushed out recently? shows version 3.57 build 00104.kvm on the about page

Reply #4 Top

Quoting jerryd87, reply 3

I have that build and since the patch its doing it again with that build, unless multiplicty auto updates and had a new build pushed out recently? shows version 3.57 build 00104.kvm on the about page
End of jerryd87's quote

There are multiple items in that thread to review - that others had to do to ensure it was working correctly.  It would be prudent to PM others in that thread to see what they are doing to maintain it in working order.

Sean Drohan
Stardock Product Lifecycle Manager

Reply #5 Top

I'm not sure your understanding what I am saying. I am familiar with that thread, I was one of the first ones to use that build in that thread and it fixed the issues I was having. The problem is the game had another update last wensday, 6 days ago that changed how the game runs(it now automatically starts in windowed mode) ever since that patch hit the build in that thread no longer works correctly. I have done everything in that thread but this is the same problem caused by a different patch and NOTHING in that thread works. Ive tried to uninstall and reinstall today, I'm using that build, I've tried changing all kinds of settings, and tried the xmouse, NONE of it works I still get secondary boxes broadcasting mouse actions to the main pc, but ONLY in eq

Reply #6 Top

just did a fresh install of the "fixed" multiplicity build on every single pc and even tried switching what box was primary. same issue no matter what pc is primary or what one im mouse looking from. secondary is always broadcasting to primary pc when playing everquest. Something changed with last weeks patch, not sure what but something.

Reply #7 Top

You may need to contact the everquest devs for assistance on this on what they have changed.

Reply #8 Top

ive had same issue and still havent received an answer on how to fix, your "fix" does not work, and needs to be revisited.

Reply #9 Top

Quoting kanjaylahn, reply 8

ive had same issue and still havent received an answer on how to fix, your "fix" does not work, and needs to be revisited.
End of kanjaylahn's quote

As mentioned by Dev on Reply#7, Have you tried contact Everquest's Dev for assistance on the issue?

Thank you,

Basj,
Stardock Community Assistant

Reply #10 Top

Hello all, I'd like to add some observations I have made in regard to this. I believe the underlying issue is when mouse control passes from the primary to the secondary PC, the Everquest client on the main PC is still focused on the primary PC. The reason that X-Controls work for some people (those who move the mouse to the screen edge) is because that program removes the focus from the Everquest client when the mouse leaves the window, and prevents the shadow controls from coming through.

For myself, I use hotkeys to pass control to my secondary PC and my mouse stays over the Everquest client. So my client never loses focus and the mouse look on my secondary PC is shadowed to my primary. I can replicate the behavior by simply clicking out of my main PC Everquest client (so it loses focus) and then passing control to my secondary PC. When I do that, it works as expected.

I don't know if this is a feasible suggestion or not, but if there were a setting in Multiplicity to defocus the active window (or a specific window name) when control is passed to a secondary PC, I believe the issue would be resolved.

Reply #11 Top

@forsythe81

Hello,

I have forwarded your report to the Stardock support team for their review and recommendations.

Please keep an eye on this thread for any updates.

We really do appreciate your feedback, thanks.

Reply #12 Top

Quoting forsythe81, reply 10

Hello all, I'd like to add some observations I have made in regard to this. I believe the underlying issue is when mouse control passes from the primary to the secondary PC, the Everquest client on the main PC is still focused on the primary PC. The reason that X-Controls work for some people (those who move the mouse to the screen edge) is because that program removes the focus from the Everquest client when the mouse leaves the window, and prevents the shadow controls from coming through.

For myself, I use hotkeys to pass control to my secondary PC and my mouse stays over the Everquest client. So my client never loses focus and the mouse look on my secondary PC is shadowed to my primary. I can replicate the behavior by simply clicking out of my main PC Everquest client (so it loses focus) and then passing control to my secondary PC. When I do that, it works as expected.

I don't know if this is a feasible suggestion or not, but if there were a setting in Multiplicity to defocus the active window (or a specific window name) when control is passed to a secondary PC, I believe the issue would be resolved.
End of forsythe81's quote

Has anyone asked the Everquest devs for their response to this issue?

If so, can a thread be posted to it?

Thanks.

Sean Drohan
Stardock Product Lifecycle Manager

Reply #13 Top

Hi Sean, I did find a forum post where this was raised, but there was no dev response. I also believe that this issue was resolved with a recent Multiplicity update, and then subsequently returned. I cannot confirm that, but I pieced it together from what I've heard/read. The link is here: https://forums.daybreakgames.com/eq/index.php?threads/issue-with-scroll-and-rmb-since-64-bit-update-when-using-kvm-software.280974/

The main issue with involving the EQ developers, is that they do not state whether using Multiplicity is against the rules on some servers. It would likely go unanswered, as the previous posts have. I can tell you that it is enough of an annoyance that I have stopped using Multiplicity and I would be happy to help troubleshoot or provide any information needed.

If your thought is that the issue is 100% not with Multiplicity, I would be willing to start another thread on the EQ bugs to see if there is a reply.

Reply #14 Top

Quoting forsythe81, reply 13

Hi Sean, I did find a forum post where this was raised, but there was no dev response. I also believe that this issue was resolved with a recent Multiplicity update, and then subsequently returned. I cannot confirm that, but I pieced it together from what I've heard/read. The link is here: https://forums.daybreakgames.com/eq/index.php?threads/issue-with-scroll-and-rmb-since-64-bit-update-when-using-kvm-software.280974/

The main issue with involving the EQ developers, is that they do not state whether using Multiplicity is against the rules on some servers. It would likely go unanswered, as the previous posts have. I can tell you that it is enough of an annoyance that I have stopped using Multiplicity and I would be happy to help troubleshoot or provide any information needed.

If your thought is that the issue is 100% not with Multiplicity, I would be willing to start another thread on the EQ bugs to see if there is a reply.
End of forsythe81's quote

Every developer has a very challenging task of just keeping up with what MS changes for Windows.  When it's an issue with a much smaller product (EQ) with unresponsive developers, there is not much we can do. 

Sean Drohan
Stardock Product Lifecycle Manager