The edge-length parameter doesn’t seem to work after 5.0 EA…resulting in really long thin polys which is an unwanted result…EA result is working correctly…here dividing the geo into max 1cm edge-length. Is it a known bug?
//Digifolkesson
It is expected behaviour.
We changed the CAD library used in 5.X. 5.0EA still use library from 4.27.
For 5.0 you have only one tessellator and it does not support max edge length yet. We omitted to grey the option, that should be fixed in an upcoming version. You can only work on the two other tessellation settings: chord tolerance and normal tolerance
For 5.1, you have two tessellator. The default one is the same than in 5.0 so no max edge length.
But you can toggle other tessellator: you need to change a CVar, type “ds.CADTranslator.DisableCADKernelTessellation False” in the command line.
Then you will need to do a full reimport of your part.
Hi ,
thank you for your information, it’s still the case in 5.2 the edge length is not working
the problem if I don’t be able to set the edge length and I try to export the static mesh on Blender (FBX) for example the normal is faceted on someplace and is unusable.
I tried with the CAD Kernel the Edge-Lenght is working but the result is unusable
ds.CADTranslator.DisableCADKernelTessellation 0
i tried on multiple objects but i have almost always had strange results and holes in the mesh.
i found this on the 5.2 Relase note
" * The ability to bypass the Max Edge Length setting on very large flat surfaces."
it will be nice to have a check box to choose if we want to bypass, because sometimes i need them because some normal artefact on large triangle.
Thank you for feedback, that is well appreciated.
- What CAD file format are you importing? Can you share some of the geometries that shows hole on import with us so we put them in our library of files to test CADKernel against?
- Are the holes you see real holes (geometry missing) or are those flipped patches?
- Regarding normal issue with default tesselator. What about regenerating normals in UE or blender on the mesh imported? does that correct the issues you see?
- I am checking with dev what this thing in the release note means. You can try to put 0 on the max edge length settings
Hello Flavien,
thank you very much for your reply
Sorry for the delay, I hadn’t seen the notification,
-
here’s the same file I used for the screenshot above
https://kdrive.infomaniak.com/app/share/116394/f17b3b47-94af-4920-a067-c8ae2bf105f7 is a step file received from my client -
no there’s no hole it’s a closed volume, if I use the default tessellation it works fine, but as the “Max Edge lenght” option doesn’t work it’s annoying. on the other hand if I use the CADKernel, the Edge Lenght works, but it creates weird holes like in this case. and also on the other parts I have most of the chamfers have disappeared (I have a hole instead of a chamfer)
-
I’ve tried to fix the normal in blender and I’ve managed to correct some parts, the problem is that I often receive jewelry pieces in CAD format, and the curvature must be perfect and it’s impossible to correct by hand, the normal vertex is crucial.
it would take me hours to correct (without being able to do it perfectly) for something that should work anyway. and also I’d like to use visual dataprep to automate my workflow, but if I have to start retouching each part in order to correct the normals. It becomes useless and I’d have to use a program other than Datasmith, which is a pity because I think it’s really great and there’s not much missing to make it perfect.
That’s why I think the option “The ability to bypass the Max Edge Length setting on very large flat surfaces” is a bad idea, because this function is precisely designed to divide a large surface, and if the surface isn’t flat it will be automatically cut by the other parameters (like angle or chord). -
when I set 0, the function is disabled and therefore doesn’t cut the part in relation to its length, which is why I’m going back to point 3, because for me this function should cut the part to the desired length anyway, because in the advice you give for using nanite or for light bake is not to have a large polygon to avoid rendering artifact. so with this option, we don’t have the possibility of being able to subdivide the face if it’s flat.
What would also be interesting to have in the import window is to be able to have a global scale of the object, because as I often work on milimeter-sized parts when I import them, I often get artifacts because the part is too small.
Thank you so much for taking our ideas into consideration and making such a beautiful program.
Best Regards
Daniel
Thank you Daniel, I reproduced your missing patch with CADKernel and I created a bug in our system. Will see with dev to get it fixed soon.
I note your idea to have an idea about the size of the model when importing, but it is not something we can do yet as we would have to do some, potentially long, reading and processing of the file before showing you the import dialog window.
1 Like
Perfect , Thank you
- i understand
question, where can I see if the bug has been fixed?
which would allow me to download the latest version of unreal to give my feedback,
Have a nice day.
Best regards
Daniel
The link is here but it will take some time before it becomes active