Wow a full month(I set a reminder to check back) and nothing... you guys dropped the ball and really should abandon this website instead of spending man hours on it for no reason. Nothing matters here and I wasted my time... a little disappointing as often we need to pay people to find issues but not uncommon today as the signs were all there from the get go. Not my kind of crew after all but likely points to far larger issues that no one wants to, isn't allowed or technically can address. Time to shop for similar MP functionality as this product is clearly at the end of it's life cycle and doesn't follow standard engineering practices.
Now you can point to a specific case of how/when confidence was lost in MP as clearly as I can if ever asked. No hard feelings and I wish you all well. No need to reply as I won't be back and feel free to delete all this to protect the hive/nest.
Take care and thank you for your past service.
Having looked over your posts you seem to have initially posted complaining about the version numbering system we use which, with the greatest respect, is an internal matter.
You have however in past posts insulted support staff, game developers and the development team of Multiplicity and suggested that because the versioning system is one you do not like that somehow Stardock have been hacked?
The only issue that has been reported by yourself is the audio sending side does not hide the passcode on a secondary in the UI when you lock settings. As we have said this we have assigned to a bug and it will be addressed with the next update. This isn't a high priority update because in 99% of cases the user could if really needed just click on the unhide passcode button anyway to read it as locking settings is rarely used by customers.
We prefer to avoid putting out too many releases for tiny issues unless there is good reason (a security hole would for example be a good reason or crashes) because this can irritate customers.
Instead we are currently investigating reports of a possible KVM mode dpi scaling issue from the 3.55 release and once we have determined if that is a problem with the update, or something thats unrelated to Multiplicity itself we can decide what a future 3.56 update will contain.
I am sorry if you feel we have not responded in the time frame which you would like and I am sorry that we somehow gave the impression that it was considered an urgent update which we would rush out. I promise that the update with a tweak for this issue will be put out, but even Google Chrome works to a six week schedule.