![]() I tried various compression settings but even setting compression level to 0 is worse than entirely disabling it this way. The codec cache command: /codec-cache:įor which rfx seems to provide by far the best resultĪnd also disabling compression -compression I tried all 3 settings, RFX had the most stuttering, AVC420 had less stuttering, AVC444 had even less stuttering. The most impactful settings were the gfx (encode) command: /gfx,mask:]] This is the command I’m using: xfreerdp /d:"WORKGROUP"/u:"$USER" /v:192.168.122.2:3389 /w:1920 /h:1015 /bpp:32 +clipboard +fonts /gdi:hw /rfx /rfx-mode:video /sound:sys:pulse +menu-anims +window-drag /gfx:avc444 /codec-cache:rfx -compression I get a smooth 60fps cursor in xfreerdp however the rendering experience is considerably downgraded, I get what I believe are frame delays (stuttering) extremely frequently, I also tried to use alternatives to spice as well to see if I could get a better experience, but no dice there either… xfreerdp var/lib/libvirt/qemu/nvram/Windoze_GVT_VARS.fd I thought maybe since the rendering results are so good, if I’d fully passthrough the mouse I could work around the issue that way, but no dice, cursor still behaved the same. But for some unknown reason, the cursor seems to be locked to low framerates, it might be 30fps but it’s possibly even lower than that. My current Mountain Lion/Mightly Mouse combo is okay, but I’ll still be closely watching SmoothMouse.I set up a vm with gvt-g in virt-manager and it works fantastic, I’m getting 60fps rendering output when I playback video and even games. The Magic Trackpad and Magic Mouse feel pretty laggy (probably due to Bluetooth), and non-Apple mice appear to be treated differently than Apple mice and still feel weird. Using the wired Mighty Mouse is bearable. Just to end things on a slightly more positive note, ever since OSX Lion the mouse movement has actually felt much better. Improvements in OSX Lion & Mountain Lion: While it does makes sense that this would add some lag, I don’t think it’s sufficient to explain what makes this so frustrating. ![]() I’ve also used Linux with Compiz, again with no noticeable mouse problems. I’ve used Windows Visa and 7 with Aero enabled and don’t recall noticing any issues. However, I don’t think John Carmack’s guess that it’s due to window compositing is correct. The idea that’s actually due to lag makes a lot of sense to me, since I’ve tried so many different drivers (which are supposed to remove or change acceleration) without any satisfaction. The conventional wisdom has been that the unpleasant cursor movement is due to the acceleration curve. Why this lag thing is surprising (and exciting): ![]() Certainly not like the otherwise miserable Lenovo with Windows XP that I have to use at work. The various mice and drivers made the cursor movement feel different, sure, but not necessarily better. I’ve tried Steermouse, USB Overdrive, and the Mouse Acceleration Preference Pane. I’ve installed the Microsoft mouse drivers and the Logitech Control Center. some other wired Logitech mouse whose model name escapes me.Microsoft Wheel Mouse Optical (best feeling mouse ever made, if you ask me).Here’s a good, in-depth explanation, although it was written in the Tiger or Leopard era (mouse acceleration changed in Lion, as I discuss below): Īnyway, my quest for Windows-like mouse movement has led me down a crazy path. Usually the problem is blamed on OSX’s acceleration curve, which is supposedly very different than Windows. This is not, to put it mildly, an uncommon complaint. It’s like I’m fighting against the mouse, where on Windows it’s seamless extension of my hand. It’s not unusable, but there’s a constantly feeling of struggling to hit small targets. Like a lot of ex-Windows users, the mouse movement in OSX bugs me. Carmack suggests that this is due to OSX’s window compositing manager (the Windows 7 tests were done with its compositing window manager, Aero, disabled). He tested this on a Windows system and found essentially no lag. Even being generous with exactly which frame the mouse started moving on, I never counted less than 10 frames (at 240 hz = 42 milliseconds) and sometimes as many as 17 from the time the mouse moved to the time the pixels on the screen started to change.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |