search

cnr-isti-vclab / meshlab

The open source mesh processing system
http://www.meshlab.net
GNU General Public License v3.0
4.59k stars 817 forks source link

A lot of bugs after update to v2021.05 (Kubuntu 18.04.5 LTS) #999

Closed tttmaksko closed 2 years ago

tttmaksko commented 3 years ago

Hallo all!

I've used MeshLab for visualization some intermediate calculation (for debugging purposes). Different calculation steps are dumped as a separate layers in Wavefront OBJ geometry format (https://en.wikipedia.org/wiki/Wavefront_.obj_file). So I often use such feature as "reload layer" and "reload all layers". Also I use different visualisation settings for different layers. After update I found the lollowing issues:

  1. (may be not bug, but annoying behavior) after reload all layer settings are set to default... and I am obliged to restore all settings manually
  2. visibility of vertices and edges are resetted but this is not reflected in layers dialog
  3. tool "Get info" selects faces on the layer which is not visible and not selected in layers dialog (I'm not sure, but it may be always first layer...)

Also, I do not know how to change defaults layer visualization params (f.ex. shading and color for faces, edges and vertices; back-face visualization params for faces etc). Is it possible?

tttmaksko commented 3 years ago

Upd for 3. It is possible that the problem is also in visualization after reloading -- meshlab draws old scene, but for selecting use reloaded...

alemuntoni commented 3 years ago

I can confirm 1 and 2. I cannot replicate the 3. Could you please list the actions you make to replicate it?

Also, I do not know how to change defaults layer visualization params (f.ex. shading and color for faces, edges and vertices; back-face visualization params for faces etc). Is it possible?

Nope, it is not possible at the moment, sorry. Shading options are a bit problematic in the codebase of meshlab, I'll try to solve these issues.

tttmaksko commented 3 years ago

See my update for 3. (I think layer reloading is the actual reason)

How-to-reproduce

  1. download and unpack file faces1.zip
  2. create new project in meshlab and import this obj-file to project as layer. (Note: one surface is duplicated -- we should pay attention to it)
  3. try to use tool "get info"
  4. download and unpack file faces2.zip
  5. replace old file faces_0000007_splt_0.obj with new one
  6. in meshlab reload layer
  7. try to use tool "get info" again (it works incorrectly on the duplicated surface)
  8. try to create new project and import second file again.
  9. compare it with "reloaded" version (spoiler: this file doesn't contain duplicated surface)
tttmaksko commented 3 years ago

Note: I use the following options for visualization

  1. back-face option for faces: Double
  2. show edges: on
  3. show vertices: on
alemuntoni commented 3 years ago

Thanks again for the detailed reports, I'll look into them asap!

alemuntoni commented 3 years ago

Hi, all these three issues should have been resolved in the last commits. They were all related with an uncorrect behaviour related with shading options (and therefore mesh visualization). Could you please try the last nightly build and let me know if issues are solved? You can find here the instructions to download the last nightly.

tttmaksko commented 3 years ago

Could you please try the last nightly build and let me know if issues are solved

Super! The issues are fixed! Thnx a lot! :)

BTW, I found one more issue :) It's not very important for me, but may you'll be interesting in it :)

  1. create new project and load several layers
  2. set all layers invisible except one
  3. reload all layers
  4. set some invisible layer to visible state (all layers marked visible (but its not true))
  5. deactivate meshlab main window and activate it again -- visibility layers marks are set to correct state

Thanks!

alemuntoni commented 3 years ago

Hi, sorry for the late reply. I actually tried the last issue you reported, but I'm not able to reproduce it..

stale[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had recent activity. The resources of the VCLab team are limited, and so we are asking for your help. If this is a bug and you can still reproduce this error on the last release of MeshLab, please reply with all of the information you have about it in order to keep the issue open. If this is a feature request, and you feel that it is still relevant and valuable, please tell us why. This issue will automatically be closed in the near future if no further activity occurs. Thank you for all your contributions.