It doesn’t matter whether I download today or on any other day,the speeds are consistently slow. I’m not sure what file you tested with, but if it was under a couple hundred MB, it shouldn’t take 90 seconds. A file like the Start 11 update should only take a few seconds. If you’re using a CDN, it may be worth evaluating another provider. If you’re not using one, I strongly recom
Wow, a 50.40 MB file took over 10 minutes to download. This is almost dial-up speeds, it's 2025 and this has been a problem for at least a year or more. Can we get some actual updates on this other than "We appreciate your feedback and patience."
I don't have the Windows Clipboard Syncing enabled, but I'll try disabling file and image sharing in Multiplicity and see if I have any issues.
Yeah, I've checked what you have posted up there, was already on, still getting that error message. I even turned on "Run as Administrator" in compatibility mode, hoping it was an issue maybe with permissions and where the dmp file is located. I have been able to get it to crash pretty consistently, if I move the cursor back and forth between the 2 machines quickly. Will usually crash within 15-20 seconds. Was doing this to try and get the debugger to work. Normally it will just crash
So I'm getting this error message when Multiplicity crashes
I'm having this same issue. Happens at random times, sometimes when gaming, sometimes when vmware workstation is running, and sometimes when Firefox is running. Bascially, it's random. I've formatted and reinstalled on both machines and still persists. This is happening on my main computer, and restarting the service does fix it. I'm on Windows 11. Having some better logging inside the app would help. Faulting application name: Multipl2.exe, version: 3.0.0.0, time stamp
Stardock Multiplicity Pro 1.21 and yes, same on both computers.
When typing on the secondary machine, the text will show up on both the primary and secondary machines. Most all keystrokes cause this except things like the return and ctrl keys. Any one else had issues like this? I had this problem awhile back, but an update fixed it. Now with the new(er) update, it's starting to do it again.