Multiplicity and Everquest I

Mouse becomes captive of program window on Primary Machine

Hello,

 

I am running latest version of Multiplicity and Everquest on both primary and secondary machines. The issue is that EQ is running in a windowed mode and captures the mouse cursor and will not relinquish when you attempt to seamlessly track the mouse to the secondary machine. You have to click on the primary machine anywhere outside the EQ program window(on desktop space not covered by EQ window or on window taskbar) and then you can track seamlessly as you are supposed to be able to do. 

Both machines are windows 10. The network  is wireless and Multiplicity is for the 2 machine license. I have a pro version running upstairs on 4 computers without issue.

Any thoughts on how to fix this issue?  

 

 

12,453 views 25 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.

 

AzDude
Stardock Community Assistant

Reply #2 Top


I have a pro version running upstairs on 4 computers without issue.
End of quote

What does that mean - that different PCs that are running EQ, earlier versions of MP, and they don't have an issue?

Sean Drohan
Stardock Support Manager 

Reply #3 Top

It means I have two licenses to run Multiplicity.

One of for more than 2 PCs to be controlled and it is operating within an Ethernet connect environment and the other license is a two workstation license running between two computers running in a wireless network environment.

Although I do not think that the network type matters at all since if, within the 2 PC multiplicity installation, I can get the seemless tracking of the mouse to work IF I click outside of the program window for Everquest that is running on the primary client. Or, if I click on the windows taskbar on the primary machine. 

 

Reply #4 Top

Ok, so the other set does not act differently.

That said, I dont believe MP is actually the issue here. 

windowed mode
End of quote

See about running the game with a 'borderless window'

Sean Drohan
Stardock Support Manager

Reply #5 Top

What does "borderless" mode mean in the context of EQ? I have never made a setting adjustment with anything like that in that game. I have seen it in other titles. 

Fullscreen mode results in the same behavior with Multiplicity not allowing for any seamless tracking from primary to secondary computer. 

Reply #6 Top

Quoting 666cronus666, reply 5

What does "borderless" mode mean in the context of EQ?
End of 666cronus666's quote

https://forums.daybreakgames.com/eq/index.php?threads/everquest-in-windowed-mode-but-without-the-framing.220206/

https://www.redguides.com/community/threads/eqfullscreenwindow-borderless-v1-0.65341/

Sean Drohan
Stardock Support Manager

Reply #7 Top

Neither program worked. Whenever EQ "has the mouse" it is like multiplicity acts like there is no mouse. 

Reply #8 Top

Quoting 666cronus666, reply 7

Neither program worked. Whenever EQ "has the mouse" it is like multiplicity acts like there is no mouse. 
End of 666cronus666's quote

Again, it does not appear to be an MP thing - as you can see from those threads, other EQ users have had similar complaints.

Sean Drohan
Stardock Support Manager

 

Reply #9 Top

I can see you are not willing to help. I will redirect my prior contact and request for an email to the community manager. 

Reply #10 Top

An application can request that the mouse is contained within a zone such as a specific window.  If this happens the mouse will never hit the edge of the screen and thus not switch.

That is assuming the cursor always stays inside the window?

If not it could be the game is blocking the capture of the mouse for some sort of anti cheating thing possibly.

You could try setting a hotkey to switch computers and see if it switches successfully.

It is unlikely to be a bug in Multiplicity as it cares not what applications you are using.

Reply #11 Top

Quoting 666cronus666, reply 9

I can see you are not willing to help. I will redirect my prior contact and request for an email to the community manager. 
End of 666cronus666's quote

Unwilling to help? I went through the game's forums in that very effort - to help you...

Sean Drohan
Stardock Support Manager

Reply #12 Top

The difficult part to understand is that literally the only difference is one working application runs in a connected ethernet network setting while the installation that is not working is operating in the same U-verse internet environment but is operating on wireless. 

 

The appliction(EQ) is configured the same. It works well in the wired\connected situation but will not work in the wireless instance. 

Reply #13 Top

One other though, is Multplicity installed off Program files (x86) on the primary on the non working computer?

Reply #14 Top

Quoting 666cronus666, reply 12

The appliction(EQ) is configured the same. It works well in the wired\connected situation but will not work in the wireless instance. 
End of 666cronus666's quote

MP does not care about the network medium (as long as its IP).  Something has to be different for the installation \ config \ settings of the one PC set that works.

If you need to test this, if possible, change the Ethernet PCs to wireless and see if you still see the issue.

Sean Drohan
Stardock Support Manager

Reply #15 Top

Multiplicity installs are identical except for the license. One license (not working) is for just two computers. The other is for 2 to 9 I think and it works well on all four computers I have on the ethernet connection. 

Reply #16 Top

In the setup for secondary computer on non-working 2 machine setup do I need to force Multiplicty to resolve by IP vs. machine name?

Reply #17 Top

Quoting 666cronus666, reply 16

In the setup for secondary computer on non-working 2 machine setup do I need to force Multiplicty to resolve by IP vs. machine name?
End of 666cronus666's quote

It should not matter.

Sean Drohan
Stardock Support Manager

Reply #18 Top

That's like two replies that basically say "it doesn't matter"..... "it should work." 

 

Excellent. 

Reply #19 Top

Quoting Neil, reply 13

One other though, is Multplicity installed off Program files (x86) on the primary on the non working computer?
End of Neil's quote

 

The machine is an older one(Primary used to be windows 7 but free upgraded to Win10 when Microsoft offered that upgrade cycle).. It used to be a secondary machine and a part of the working ethernet install of Multiplicity I have. I will try and reinstall Multiplicity and see if that helps. 

Reply #20 Top

Quoting 666cronus666, reply 18

That's like two replies that basically say "it doesn't matter"..... "it should work." 

Excellent. 
End of 666cronus666's quote

Yes, that is indeed what I was saying, either connection option works to connect two PCs.  If you need me to expound on that, why one would use one vs the other, and in what circumstances, please say so.

What I was not doing was dismissing your question.

We want to solve your issue as much as you do.  Please stay on topic in that effort. 

Sean Drohan
Stardock Support Manager

Reply #21 Top

Just posting here to thank Azdude for his suggestion sent via PM. It worked and I do appreciate his examination of the issue from enough angles to assist. 

Reply #22 Top

Quoting 666cronus666, reply 19
Quoting Neil Banfield,


One other though, is Multplicity installed off Program files (x86) on the primary on the non working computer?

The machine is an older one(Primary used to be windows 7 but free upgraded to Win10 when Microsoft offered that upgrade cycle).. It used to be a secondary machine and a part of the working ethernet install of Multiplicity I have. I will try and reinstall Multiplicity and see if that helps. 

End of 666cronus666's quote

Neil's question is still outstanding, however. Is MP on any non-working PC installed in a location other than the default:

C:\Program Files (x86)\Stardock\Multiplicity

Sean Drohan
Stardock Support Manager

Reply #23 Top

Quoting 666cronus666, reply 21

Just posting here to thank Azdude for his suggestion sent via PM. It worked and I do appreciate his examination of the issue from enough angles to assist. 
End of 666cronus666's quote

So a purge and reinstall, the one from the FAQ here:

https://forums.stardock.com/486104/multiplicity-support-faq#reinstalling

Worked to resolve your issue - is that what you are saying?

Sean Drohan
Stardock Support Manager

Reply #24 Top

Quoting sdRohan, reply 23


Quoting 666cronus666,

Just posting here to thank Azdude for his suggestion sent via PM. It worked and I do appreciate his examination of the issue from enough angles to assist. 



So a purge and reinstall, the one from the FAQ here:

https://forums.stardock.com/486104/multiplicity-support-faq#reinstalling

Worked to resolve your issue - is that what you are saying?

Sean Drohan
Stardock Support Manager

End of sdRohan's quote

 

Your failed attempt at trolling is right up there with handing a customer a lengthy manual and then proudly telling whoever you report to that you have "supported them." 

Good try...end of conversation for me. I reported you to hopefully someone who will listen and act on your lack of professionalism. 

Reply #25 Top

AZDude has told me that indeed you reported to him that the purge \ reinstall worked for you - very pleased to hear that.

Sean Drohan
Stardock Support Manager