Mouse scroll or clicks on both pc's.

Hi

Using Multiplicity to scroll or click on the second pc whilst playing Microsoft Flight Simulator 2020 on the first pc, causes MSFS to scroll or click.

Basically all mouse operations are duplicated on the first pc, is there a fix or option to prevent this?

Many thanks

17,654 views 16 replies
Reply #1 Top

Hello,
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 #3 Top

Nothing yet, I re-forward it to Support.

Thank you,

Basj,
Stardock Community Assistant

Reply #5 Top

Basically all mouse operations are duplicated on the first pc, is there a fix or option to prevent this?
End of quote

Unless this was written wrong, or I am reading it incorrectly, normally it would be this option:

Where all keyboard input on the Primary would be duplicated on all Secondary PCs.  You have written that anything on the Secondary is duplicating on the Primary - is that accurate?  Does that option off help?

Sean Drohan
Stardock Support Manager

Reply #6 Top

Hi Sean

Thanks for the reply, that option is not checked. This issue only appears whilst I am using MSFS2020, it does not happen at any other time. 

In MSFS 2020, as an example, if I scroll up or down on the secondary pc, the cockpit will zoom in or out, or if I am on the world map looking for a location the world will zoom in or out.

It is not restricted to zoom, if I click the left mouse button on the secondary pc, this is also felt on the primary pc.

It is acting as if the checkbox you highlight above is checked but again only whilst using MSFS2020

 

Hope that clarifies a little more.

 

Thanks

Garry

Reply #7 Top

That is not the first time we have heard of issues with MP and MSFS2020.  

MP sends simulated keystrokes \ mouse moments to any Secondary that has focus.  What MSFS2020 seems to be doing is digesting them on the Primary when it should not.  I would normally suspect anti-cheat software as well but I cant see that being used in MSFS.

I can see what the dev team has to say about it but I would not expect anything soon if at all.

Sean Drohan
Stardock Support Manager

Reply #8 Top

I see this issue still exists and has never been addressed for a year now. 
This is still happening in any program that has full screen on the primary.

 

Reply #9 Top

Quoting redmace, reply 8

I see this issue still exists and has never been addressed for a year now. 
This is still happening in any program that has full screen on the primary.
End of redmace's quote

We have not seen this be the case with any other app.

Again, this is the main item you want to check if keystrokes (not mouse clicks) are being replicated from the Primary to other PCs:

Sean Drohan
Stardock Product Lifecycle Manager

Reply #10 Top

None of this is checked and was the first thing I checked.

 

Reply #11 Top

I'm also having the same issue, and my settings are the same that SDrohan has displayed with the box unchecked. Its not the primary broadcasting to the secondary's, its when playing Everquest and mouse dragging on the secondary's is broadcasting back to the promary

Reply #12 Top

Quoting brunlin, reply 11

I'm also having the same issue, and my settings are the same that SDrohan has displayed with the box unchecked. Its not the primary broadcasting to the secondary's, its when playing Everquest and mouse dragging on the secondary's is broadcasting back to the promary
End of brunlin's quote

Please see:

https://forums.stardock.com/510351/page/3/#3842229

Sean Drohan
Stardock Product Lifecycle Manager

Reply #13 Top

I would like to report that this issue regarding Microsoft Flight Simulator has now magically been resolved. I don't know if it was Windows 11 22H2 update or the recent Microsoft Flight Simulator Sim Update 10 that fixed this "bug", but my mouse now properly releases when I move off to a second computer. When I use the scroll wheel on a secondary computer the camera zoom is no longer affected on the primary computer. I also don't accidentally click items in the flight deck when my mouse is manipulating the secondary computer. This proves this issue was either caused by MSFS 2020 itself or the Windows 11 operating system. Glad this issue is resolved. It was very annoying. 

Reply #14 Top

Quoting bjzx3, reply 13

I would like to report that this issue regarding Microsoft Flight Simulator has now magically been resolved. I don't know if it was Windows 11 22H2 update or the recent Microsoft Flight Simulator Sim Update 10 that fixed this "bug", but my mouse now properly releases when I move off to a second computer. When I use the scroll wheel on a secondary computer the camera zoom is no longer affected on the primary computer. I also don't accidentally click items in the flight deck when my mouse is manipulating the secondary computer. This proves this issue was either caused by MSFS 2020 itself or the Windows 11 operating system. Glad this issue is resolved. It was very annoying. 
End of bjzx3's quote

Thanks for the update, bjzx3.

Sean Drohan
Stardock Product Lifecycle Manager

+1 Loading…
Reply #16 Top

Quoting garrycormack1175, reply 15

Sadly this is not replicated on Windows 10. 
End of garrycormack1175's quote

I'm sorry to hear this is still a problem for you. I did participate in the MSFS Sim Update 10 beta for 2 or 3 months. I've had this mouse problem the whole entire time. Coincidentally Microsoft released Windows 11 22H2 update September 20th 2022. The very next day September 21st 2022, Microsoft released MSFS Sim Update 10. I nuked my entire system and did a fresh install of Windows 11 22H2, then did a fresh install of MSFS 2020 sim update 10. This is when I noticed the mouse problem with Multiplicity went away. This leads me to believe the fix is on the Windows side instead of the MSFS side, however I can't prove it, unless I go back to Windows 11 21H2, which I don't want to do as that is a lot of work and wear and tear on my SSDs. I do know there will be a Windows 10 22H2 update released sometime in October. Maybe this new update for Windows 10 will finally resolve this issue on Windows 10. If it does, you should report back here so anyone else who runs into this problem might find the solution.