Come on guys, I emailed you and told you that until you add OS X integration, there's no reason for me to upgrade to v3. So stop spamming me several times a week with different "offers" to upgrade. It got old two months ago.
So, I noticed a while back that the readme.txt has the following info (and still has it in the current version): "-If you are using a VPN to connect to office resources from home, you will not be able to connect to secondary machines on your local network. It's possible that using a direct Firewire connection, a second NIC, or configuring split tunneling support with your VPN (if allowed by your security settings) can work around that." Under the TCP/IP advance
I had similar issues to what you are describing on two XP machines.. I did the free upgrade to 1.2, and my problems went away.
I not only have a similar situation, except with teamspeak, but I have found that with multiplicity, TeamSpeak goes into a mode that it doesn't accept any input (from mouse on the menus or from keys) after going to the secondary computer a few times. This happens even when I don't have push-to-talk turned on (i.e., using voice activation). The only input that works is to close it. I think that a key binding that would be set on the primary but carry over from the secondary back to the primary
Maybe I wasn't clear. The actual network connection hadn't dropped, but watching the "Multiplicity Tray Icon" on the primary computer I could see that Multiplicity kept dropping connections. The actual network status of the secondary machine showed a steady connection, and I wasn't experiencing weird latency issues in WoW, either, which I would have if my NIC had been dropping connections. Here's the weird thing: I used to use a laptop for a very long time w/ Multiplicity. about 2 we
Well, I messed with it a bit more, and switched my network cable from jack #1 to jack #2, and that fixed it. I'd checked that the cable was plugged in all the way on jack #1, and I wasn't getting a 'network disconnected' status on the secondary machine, so I don't know that that was necessarily the problem, but since jack #2 had a different IP address and everything it is working fine again (so long as I leave it on jack #2).
Yes, I noticed the problem in WoW. Then I went back to my desktop, and noticed that the problem was on my desktop, too. In looking at it further, it appears that my multiplicity connection to my secondary machine keeps turning on and off (it'll be on for several seconds, then turn off for a moment, then turn on for several seconds). I'm talking about the little red / green icon turns 'black' (disconnected). I updated to 1.2 tonight after reading in the forums and noticed that
Actually, when I don't lose my mouse altogether, and I am typing, what will sometimes occur is that all of a sudden my pointer will switch back to my primary machine (on the far side of the screen away from the secondary), and then when I drag the pointer back to the secondary, the last key I had typed a few seconds previous gets put into the right position. After I mess with it for a bit trying to type on the secondary and keep moving the mouse over there, the mouse becomes "stuck" on the seco
Ironically, I also had this same problem occur, starting today. It's been working like a champ - was playing WoW with it last night. Went to play this morning, and all of a sudden I can't get control off my secondary PC. It works fine for a couple of seconds, then the mouse starts hitching, and all of a sudden I can't get back to the primary PC.