Multiplicity 3.5 Beta Issue Report Thread

With the Multiplicity 3.5 beta release, we are creating this thread so that users can report any observed issues.  

Obtaining the beta:

Object Desktop members can get the beta from within Object Desktop Manager with 'show beta downloads' enabled:

f

Individual purchases (as well as Object Desktop Members) can also be obtained from your an account page:

https://store.stardock.com/myaccount/products

For guest check-out purchase (no account), from this link:

http://www.stardock.com/support/productkeyretrieval

Note: Please remember that this version needs to be installed on the Primary as well as all Secondary PCs in your group.

Reporting an issue:

Please include the following for anything found:

  • Exact Windows version \ build (winver.exe)
  • Detailed steps to recreate the issue seen
  • Screenshots and videos are very helpful.  Videos can be uploaded to a cloud drive services (GoogleDrive, DropBox, OneDrive, YouTube) and links included in your post.  Images can be directly added.
  • If there are specific apps that the app does not work (well) with, please note what apps and their exact versions.  If any app is not common, a link to a trial version would be appreciated.

Thank you for your interest and any time you put into testing.

Sean Drohan
Stardock Support Manager

6,968 views 5 replies
Reply #1 Top

Changelog for Multiplicity 3.5

  • Adds a flush DNS entry to the right-click menu (for when your computer has changed IP and the OS doesn't know as it has cached it)
  • Adds a message about disabling the cloud clipboard sharing in the OS if detected once
  • Adds text about the VirtualBox network adapter breaking WakeOnLan
  • Tweaks how it handles cursors if PCs are under heavy load
  • Modifies how it polls for certain events which might make it more friendly to machines with huge numbers of CPU cores rather than potentially keeping them awake
  • Swaps the mouse buttons if you have swap mouse buttons enabled so it doesn't double swap.
  • Should address the issue with cursor shrinking in mixed dpi setups
  • Fixed issue with Drag and Drop that could have it not work consistently if Primary had a higher DPI scale than the destination Secondary
  • Fixed text clipping issues on some menus when at 125% DPI
Reply #2 Top

With the release of Multiplicity 3.5 we are closing this thread.

Thanks for the feedback.

Sean Drohan
Stardock Support Manager

Reply #3 Top

Still a major problem with MP.  NO IPV6 support.  I purchased 2 Licenses and have not been abled to use this software for the past 2yrs since i moved over to using ipv6 only.  yet when you look at MWB ipv6 is native.  Would be nice if you added this and if you have no plans too then it would be nice if you refunded me.

Reply #4 Top

Quoting ljferdinand, reply 3

Still a major problem with MP.  NO IPV6 support.  I purchased 2 Licenses and have not been abled to use this software for the past 2yrs since i moved over to using ipv6 only.  yet when you look at MWB ipv6 is native.  Would be nice if you added this and if you have no plans too then it would be nice if you refunded me.
End of ljferdinand's quote

Why have you moved over to ipv6 exclusively rather than a mixed setup?

It is unlikely refunds would be issued two years later because the product does not contain a feature that it never said it had in the first place.

IPv6 support is something that is planned for future releases, but this is likely to be a version 4 level feature not 3.x.

Reply #5 Top

I have a very complexed Network consisting of 94 devices which over half needs to be accessed externally.

 

Here are some reasons why i use ipv6

1. problems assoicated with NAT and identifing certiain devices externally.

2. private address collisions

3. Simpler header format (wont go into details here but this is important for my work)

4. IPV6 has bettter flow labeling than IPV4

5. Easier administration (GOODBYE DHCP)

6. Security.  IPV4 uses a 32-bit address whilst IPV6 utilizes 128-bit Internet addresses.

 

 

I do understand the refund situation but in all fairness ipv6 has been around for a longtime now and it isnt hard to impliment so alittle puzzled as to why MP doesnt have this.  And having to pay for a future release to have this feature is a bit of a joke tbh.