[Solved] Meshlab not working in 0.8.2
It seems that the Meshlab interface in 0.8.2 is still broken, has anybody been able to get it to work?
When I select it in the GUI the screen flashes, but no file is produced and I do not get the extra duck folder.
@Mario - I know that all the documentation shows that you made the changes so it should work with the new Meshlab version.
Thanks for all the help.
download the file via ftp and use the meshlabprogram
I tested it before i released 0.8.2. In fact of the meshing fails i need a log to see what is going on.
Meshing can take several minutes. After pressing the button a message should appear. It says "Meshing started". After a couple of minutes (time depends on resolution file size of pointcloud etc...) another message should say "Meshing finished". Please keep in mind that the integrated meshing only works for simple objects like busts and so on. For more complex objects i always recommend to do multiple scans, download the ply's and mesh them external with meshlab and/or cloudcompare.
Difficult part of the object are the ears.
This rabbit was scanned by FabScan in two iterations. ( 2 single scans using 2 different positions). Pointclouds were aligned by using cloudcompare and finaly meshed by meshlab.
Here is the list of log files in the fabscanpi directory, just let me know which one you need.
pi@fabscanpi:/var/log/fabscanpi $ ls -l
-rw-r--r-- 1 root root 100 Jan 10 19:42 fabscanpi.log
-rw-r--r-- 1 root root 101 Jan 10 19:42 fabscanpi.log.1
-rw-r--r-- 1 root root 1694048 Jan 10 21:21 fabscanpi.log.2
-rw-r--r-- 1 root root 4999988 Jan 10 18:01 fabscanpi.log.3
-rw-r--r-- 1 root root 4999938 Jan 10 13:27 fabscanpi.log.4
-rw-r--r-- 1 root root 4999968 Jan 10 04:26 fabscanpi.log.5
Also, here is photo of the screen message that pops up when I press the "Start Meshing" button, this is the same if I choose .stl or .ply. It says "No News Available".
Hope this helps and looking forward to your input.
Never mind it is working now. The only think I can figure out is that I was trying too large of a scan.
This is solved, sorry for the confusion.