Mouse alignment

Hi,

I am having problems when moving my mouse from 1 screen to another.

When i move the mouse from 1 screen to another it will always appear at the right move edge regardless of how far left i place the mouse.

Have uploaded a video, hopefully it shows the issue i am facing clearly. https://vimeo.com/281224257

Also tried using multiplicity's in app alignment but it only fixed 1 way mouse movement and not the other.

Also attached a screenshot of my screens' resolution.

Mouse problem persist between top right and bottom right screens.

Please assist. TIA

38,353 views 28 replies
Reply #1 Top

Hello,

Sorry to hear you are having issues. Have you try our Multiplicity FAQ section? : Maybe this can help you : https://forums.stardock.com/486104/multiplicity-support-faq#seamlessmonitor

Please try those and if you still need assistance please report back,

Thanks

Basj,

Stardock Community Assistant.

Reply #2 Top

Quoting basj, reply 1

Hello,

Sorry to hear you are having issues. Have you try our Multiplicity FAQ section? : Maybe this can help you : https://forums.stardock.com/486104/multiplicity-support-faq#seamlessmonitor

Please try those and if you still need assistance please report back,

Thanks

Basj,

Stardock Community Assistant.

Thanks for the reply.

I have read thru the FAQ section and tried the suggestions.

Have also done a search on "Mouse" and went thru the threads.

Any other suggestions would help pls?

 

Reply #3 Top

Hello,

I have forwarded your problem to Stardock Support team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

 

Basj

Stardock Community Assistant.

Reply #4 Top

Hello,

Sorry to hear you are having trouble.

While I cant see how you were able to film that (the Seamless transition with no monitor bezel / border visible), as a test, try matching the resolutions on each (so they are the same).

Also, while you indicated you had altered some, there are many options here to try:

Reply #5 Top

Quoting sdRohan, reply 4

Hello,

Sorry to hear you are having trouble.

While I cant see how you were able to film that (the Seamless transition with no monitor bezel / border visible), as a test, try matching the resolutions on each (so they are the same).

Also, while you indicated you had altered some, there are many options here to try:

Reduced 31%
Original 962 x 642



Reduced 31%
Original 962 x 642


thanks for the replies. 

I have tried the alignment within too. It doesnt resolve the problem. 

Reply #6 Top

Quoting Ladious, reply 5

I have tried the alignment within too. It doesnt resolve the problem. 

That is hard to fathom, however, you should also experiment with resolutions to see if that affects the issue.

+1 Loading…
Reply #7 Top

I have the exact same problem.   I have four monitors, all the same resolution and arranged with the primary as top-left, and secondaries in top-right, bottom-left and bottom right positions (2x2 configuration).  When I mouse from the top-left (primary) monitor to the secondary below it, the cursor moves from one monitor to the other in relatively the same position. For example, If i move the mouse down in the center of the bottom border of the top left screen, it will appear in the center of the top border of the bottom-left screen, and vice-versa.  Likewise, If i move left-to-right or right-to-left between the top two or bottom two monitors, the mouse pointer transitions between them at whatever point along the border that I cross. 

However, when trying to move from the top-right to the bottom-right monitor or vice versa, no matter at what point across the common border i chose to move the mouse, it appears on the rightmost common corner on the other monitor.  For example, If I move from the top-right monitor to the bottom left monitor by moving the mouse pointer down in the center of the bottom border of the top-right monitor, the pointer will appear in the top-right corner of the bottom-right monitor.  This happens regardless of at what point along the common border i try to transition the mouse.   Likewise, If I move from the bottom-right monitor to the top-left monitor by moving the mouse pointer up in the center of the top border of the bottom-right monitor, the pointer will appear in the bottom-right corner of the top-right monitor. 

No amount of trying to change the alignment settings has changed this behavior.

Ladius' video in the original post on this problem above shows the exact problem quite clearly.  You do not need to see the bezels to understand that moving the mouse from one monitor to the other is not working correctly.
Reply #8 Top

Quoting rich8n1982, reply 7

I have four monitors, all the same resolution and arranged with the primary as top-left, and secondaries in top-right, bottom-left and bottom right positions

Just remember, MP does not care about monitor placement, it cares about PC placement, what the main monitors are in Windows, and will NEVER allow diagonal movement.

If you have 1 PC with 3 monitors in a 4 monitor grid, its mouse movement is not going to be natural.  Another feature people are not aware of but is damn handy is:

  

The rest of the wording is just too hard to follow without images, something like this and video.  I would also need to see how you have your MP grid, how you have your monitors placed in Windows itself and what are the mains in Windows

PC 1:

PC 2:

Reply #11 Top

Quoting Mike3rd, reply 10

Hello.
Is there any update on this topic?
I have the exact issue the threadstarter mentioned.

Hello,
Sorry to hear you are having issues. I have forward your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Basj,
Stardock Community Assistant

 

Reply #12 Top

Quoting Mike3rd, reply 10

Hello.

Is there any update on this topic?

I have the exact issue the threadstarter mentioned.

We need to know if you have tried any of what has been mentioned here, what version, and more details about your setup - perhaps a video as well.

One other setting change I would mention would be:

Sean Drohan
Stardock Support Manager

Reply #13 Top

I think the topic starter has pointed out the problem very comprehensibly.

But I made a video now: 

https://mega.nz/file/GLoBSAzI#tBJYVRbCeppCL_ToYehrvvZr12wtAkk0pMzR5Qluh3c

 

For information:

1. We have a system, as in the video, arrangement several times. Two months ago everything was normal, now about 60% are affected.

2. The systems are arranged 2x2 in Multiplicity. Top left is primary.

3. (In our case) Only the systems after the primary system are affected. Means: Everything directly above or below the main system works (as you can see). Every following system is affected by the error. Even if I e.g. arrange all 4 systems under each other, every system after the primary will be affected.

4. Swapping the system arrangement in Multiplicity does not help. It is always like in point 3.

5. Reinstalling Multiplicity on all systems does not help.

6. Since we have a mix of W7 and W10, we tried it without W7. Same problem.

7. Your suggestion did not solve the problem unfortunately. But as I said, it worked before without any option.

 

Reply #15 Top

Quoting Mike3rd, reply 13

7. Your suggestion did not solve the problem unfortunately. But as I said, it worked before without any option.

What suggestion exactly?

Sean Drohan
Stardock Support Manager

Reply #17 Top

Quoting Mike3rd, reply 16

Please don't play for time.

Huh?

Quoting Mike3rd, reply 16

Your suggestion one post before of course.

I will pass it on to the developers.  Thanks for your feedback.

Sean Drohan
Stardock Support Manager

Reply #18 Top

We have this problem now on many PCs with Multiplicity. The problem itself was discovered by the OP in 2018. Was there never a solution?

What does it mean, that it will be pasted to the developers? Will they write here or give an update? What are the next steps to analyse this?

 

 

Reply #19 Top

Quoting Mike3rd, reply 18

What does it mean, that it will be pasted to the developers?

They will be made aware of the issue and the four clients that seem to be experiencing it.

Quoting Mike3rd, reply 18

Will they write here or give an update

Yes and\or it will be part of a changelog posted when there is an update to the application, example:

https://forums.stardock.com/503946/get;3800715

Quoting Mike3rd, reply 18

What are the next steps to analyse this?

We will post if\when we need more information.

Thank you for the feedback.

Sean Drohan
Stardock Support Manager

Reply #21 Top

Quoting Mike3rd, reply 20

Hi. Any news from the Dev-Team on this Topic?

No, not yet.

I want to be clear on something - this issue is not preventing you from using the product, correct?

Sean Drohan
Stardock Support Manager

Reply #22 Top

I have the exact same issue. For my uses, it was inconvenient enough to make me stop using the product and find an alternative solution.

Reply #23 Top

Quoting sdRohan, reply 21

I want to be clear on something - this issue is not preventing you from using the product, correct?

Sean Drohan
Stardock Support Manager

We can use it but it makes it really hard to work efficiently with the systems (we have more than 40 with it) and causes fail clicks.
Also on some PCs the mouse curser will not change it's form when stretching a window for example. But only on some machines. With an additional mouse attached directly, there are no problems here.

 

 

Quoting kemilyon, reply 22

I have the exact same issue. For my uses, it was inconvenient enough to make me stop using the product and find an alternative solution.

Hi, what was the alternative solution?

 
Reply #24 Top

1 month later and nothing happened.

One would think for an investigation the developers would send a patch for testing ask more questions about the problem. It only not happens if nobody cares. Seems to be the case here.

Bad customer support. We will stick with the problem for now but will never come back to this company if we need software like this in the future.
Sorry for the other people with this problem. It won't be fixed.

Goodbye.