Thanks for the reply. Your idea could have been a decent workaround if it worked.
My colleague had the same idea and we did try it out. Apart from the fact that it is quite cumbersome to hit the exact same "minimum feature size" using the slider, even with the same "minimum feature size" the results on 2 different machines were still not matching.
Is looks like the software still does different meshes on different machines for the same "minimum feature size". Nevertheless, an option to directly input the "minimum feature size" as a value would be a great option in future.
Hope to find more ideas here to resolve this issue.
Please Login to Report Topic
Please Login to Share Feed
You are navigating away from the AIS Discovery experience