#348 Vertex/Face selection problem make meshlab unusable (win7 64bits)

[philippeB]

I have the same issue described by Dan here:
https://sourceforge.net/p/meshlab/discussion/499533/thread/4f7a15c4/?limit=50
"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. When it recovers, either none of the mesh is selected, or occasionally, a few vertices/faces are selected."

This makes meshlab impossible to use on computers that seem to be common (mine is a lenovo x230). Three different hardware configurations with the same issue are listed in the discussion:
Win7/8 x64, i7-3520M, 8GB RAM, Intel HD4000/Nvidia 640M LE 2gb
Win7 x64, i7-Q 840, 16 gb RAM, ATI FirePro M7820.
Win7 x64, i7-3520M, 8GB RAM, Intel HD4000 (mine, latest graphic driver).
It is present with various versions of meshlab.

Any fix would be great (I can try to troubleshoot provide more info if needed).
Thanks

[Jason Smith]

I also have this problem. Let me add my configuration:
Win7 x64, i7 3667U, 8GB RAM, INTEL HD4000 (windows running on macbook air hardware)

(Is meshlab still supported/actively developed?)

Does some form of bounty help?

[philippeB]

Dear developpers (if you read this message):

Bump. It is now 1.33 and it is still not working I guess.
Right now, on the same card (hd4000), I just segmented part of an 8 million polygonal mesh (with a couple of more displayed on top) without any issue in cloudcompare (http://www.danielgm.net/cc/). It is not a power issue (but I have to lug around an old laptop with an older 8400gt if I want to use meshlab away from the desktop).

The bug affects more people than you think. Intel had 65% of the GPU market share in Q4 2013 if I read this correctly:
http://jonpeddie.com/press-releases/details/gpu-market-upintel-and-nvidia-graphics-winners-in-q4-amd-down/

and it is becoming difficult to buy a not huge laptop with something else.
It may be an issue with Intel, or microsoft, or whatever but a response would be nice.

Please???

Thanks
Philippe

PS: since you ask to cite 3D-coform on your webpage, just for context, I am not currently doing polygonal meshes of my cat but working on a FP7 collaborative EC funded project where, among others, we deal with geometrical meshes and are trying to process large amounts of CT scan data for shape analysis.

[Paolo Cignoni]

We have just committed a version that solve this issue for vertex selection.
The version for face selection is a bit more complicate. But do not lose your hopes...

[Hans]

Do you have a link to a source code with this fix? I use Linux, so I need to compile.

[philippeB]

Cool. Thanks a lot.

I will wait until there is a new compiled win64 version released (I could not find a alpha/nightly so I assume I need to wait for a beta).

Philippe

[philippeB]

Fantastic! Thank you so much.
I tried the beta version. It works great!
Even with a model with 25 million faces, no crash, the selection is fine.

I have a favor to ask you.
Could you tell me in a couple of sentence how you fixed it?
Imod suffers from what looks like the same bug and I would like to post there too (if I can give pointers on how to fix it to the developpers, that may help).
Thanks again
Philippe

[RuthP]

Great, finally!! Works for me, too. Thank you SO much!
/Ruth

My config: Win7 x64, i7 4600U, 16GB RAM, INTEL HD4400

(Edit1 deleted, I was just too stupid to save properly :) )

[Mark Fuller]

I tried the 1.3.4 beta and it solved the select for me. Now I just have to figure out the selection logic better. Broken geometry with folds tends to make selection of only the folds difficult.
My config: Win8.1 i3-3217U, 4GB ram, Intel HD4000