summaryrefslogtreecommitdiff
path: root/vmware
diff options
context:
space:
mode:
author81.233.209.157 <81-233-209-157-no17.tbcn.telia.com>2012-01-13 21:18:38 +0000
committer81.233.209.157 <81-233-209-157-no17.tbcn.telia.com>2012-01-13 21:18:38 +0000
commit4f9e816e0f6ef3d9fa4139018724cb321cde1818 (patch)
treece208e3c5e5d0e87ffc523292e2742663ef26d32 /vmware
parenta0a7de2ba6cc478a70ff2dbf4d95a26038c6c169 (diff)
Add vmx options
Diffstat (limited to 'vmware')
-rw-r--r--vmware/vmware3D.moin12
1 files changed, 9 insertions, 3 deletions
diff --git a/vmware/vmware3D.moin b/vmware/vmware3D.moin
index 48be322d..13207298 100644
--- a/vmware/vmware3D.moin
+++ b/vmware/vmware3D.moin
@@ -1,5 +1,4 @@
= Support for 3D acceleration and RandR12 in xf86-video-vmware =
-
== What's needed ==
* xf86-video-vmware >= 11.9.x. The stable release will be named 12.0.0
* A linux kernel with the post-stagin version of the vmwgfx driver enabled. The vmwgfx driver version should be 2.3.0 or higher.
@@ -10,8 +9,15 @@
== Generic User Notes ==
* Due to the way software- (2D) and accelerated (Video, 3D) contents are mixed, certain operations may be slow when both accelerated contents and software contents overlap. A good such example is shaped windows on top of 3D or video. (Xine with unscaled OSD). Mixing software- and accelerated contents in a virtual environment is tricky and we've tried to optimize the driver to give the best possible interactive experience for most use cases and the new 3D-enabled compositors.
* XRender will usually not be accelerated unless operating on previously rendered 3D- or video surfaces. Therefore setups that use XRender for big operations, like XRender-enabled compositing managers, may not perform well on large screens.
- * On multi-monitor setups the glxSwapBuffers operations are still a bit slow. This will be addressed in future Workstation / Fusion releases. To somewhat work around this problem, it's possible to reduce the Workstation / Fusion GUI update frequency using the following option:
- * Applications that warp the cursor, like games or the Compiz spinning cube will not work well with VMmouse enabled, since it uses the host cursor. If this becomes a problem for you, please use the following option to disable VMmouse, and use the VMware relative USB mouse instead:
+ * On multi-monitor setups the glxSwapBuffers operations are still a bit slow. This will be addressed in future Workstation / Fusion releases. To somewhat work around this problem, it's possible to reduce the Workstation / Fusion GUI update frequency using the following option:<<BR>>
+ {{{
+svga.frameRateLimitUS = 15000
+}}}
+ * Applications that warp the cursor, like games or the Compiz spinning cube will not work well with VMmouse enabled, since it uses the host cursor. If this becomes a problem for you, please use the following .vmx file option to disable VMmouse, and use the VMware relative USB mouse instead:
+ {{{
+mouse.vusb.enable = "TRUE"
+}}}
+
* The VMware absolute USB mouse device may be detected by the kernel as a joystick. This may lead to games moving the cursor to the upper left corner or the game constantly registering a leftward-upward motion. To work around this, please disable joystick use in the game's setup, or if you have another joystick, select that one instead.
* If you use fancy RandR12 features, like rotation and / or scaling and at the same time use VMMouse, cursors may don't behave as expected. In that case, set up the relative USB mouse as described above. The driver is only capable of displaying a single hardware cursor at a time, so if more cursors need to be displayed, like when cloning outputs, the driver will automatically revert to software cursors.