I figured this is because in VMWare, the graphics is entirely software rendered, avoiding some kind of 3D acceleration problem, so I tried running Meshlab in Ubuntu with various options to disable 3D acceleration. The program generally runs at a slightly slower frame-rate than on Ubuntu, but region selections are no slower than any other operation. I installed Meshlab in the virtual machine as a test, and selection works comparatively great. If I am patient and wait for the display to update before releasing the drag, the selection does eventually work but it is unusably slow.įor some other work I have installed a Windows 7 virtual machine running in VMWare. Even if the region doesn't intersect with any polygons, the framerate drops to <0.5fps. Meshlab works fine until I try to select a region by clicking and dragging. I have what I think is this same problem on a Thinkpad X220 with "Intel(R) Sandybridge Mobile (GT2+)" (according to my Xorg.0.log), running Ubuntu 13.04. Installing older versions of Meshlab: same problemįorcing Meshlab to use either the Intel or Nvidia GPU: same problem I had the same issue prior to upgrading from Win 7 to 8, so that isn't the cause.īoth the 32bit and 64bit versions of Meshlab: same problem ![]() I don't have this problem on my desktop (Win7 圆4, i7-920, 6gb RAM, Nvidia 8800GT 512mb), or my old laptop (Win7 圆4, Core2-5450, 4gb RAM, Intel X3100). When it recovers, either none of the mesh is selected, or occasionally, a few vertices/faces are selected. When I try and select a set of points within a pointcloud, or an area of a mesh, the selection reticle never appears instead, Meshlab stops responding for about 10 seconds while consuming between 11% and 13% of the CPU time. ![]() The vertex/faces selection tools aren't working for me on my new laptop (Win7/8 圆4, i7-3520M, 8GB RAM, Intel HD4000/Nvidia 640M LE 2gb).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |