I made a video: https://youtu.be/HrfNp2LD2ws
As the word is made as: TextSide, TextFace and TextBevel there are three surfaces. If only one surface has fibers activated everything is ok, but if all three surfaces have fiber activ, the error occurs. If two surfaces have activated fibers sometimes nothing happens and sometimes the error occurs.
critical error in Lightwave when render is ready
Moderator: juanjgon
The crash is finally a LightWave problem, but anyway the issue is that your object has degenerated polygons, probably due to the beveling process, that FiberFX can't process. As you can see in the attached images, the object has polygons with a lot of problems (crossing edges and so on). If you triangulate the mesh the render works fine, but the triangulation is not right due to this degenerated polygons.
The only way to avoid this crash is to fix, remove or triangulate the polygons with problems.
-Juanjo
The only way to avoid this crash is to fix, remove or triangulate the polygons with problems.
-Juanjo
- Attachments
-
-
-
marcusstaffel
- Posts: 9
- Joined: Fri Apr 10, 2015 3:16 pm
The funny thing about it is, that the render is ok. I just have to save it in the Lightwave image viewer where the picture is ok, before acknowledging the critical error dialog from lightwave. So the picture seems to be ok even if lightwave is crashing.
In my opinion the result of one function may be undefined because something went wrong (perhaps not closed surface or something like that), but this happens at the end of the task, that it's 99,9% complete, but not 100%. So the result is undefined or not ok, but the buffer of the picture can be interpreted by the picture viewer.
I will try to correct the forms of the beveled Text. (Some charactersets are not well designed for raytracing, because they have this degenerated polygons right in their design.)
Thank you for your research.
In my opinion the result of one function may be undefined because something went wrong (perhaps not closed surface or something like that), but this happens at the end of the task, that it's 99,9% complete, but not 100%. So the result is undefined or not ok, but the buffer of the picture can be interpreted by the picture viewer.
I will try to correct the forms of the beveled Text. (Some charactersets are not well designed for raytracing, because they have this degenerated polygons right in their design.)
Thank you for your research.
Yes, the problem is that Layout crash after finish the Octane render. It is a FiberFX issue while cleaning the data used by the external render plugin. I will report this bug to the LW team to know if it can be fixed.
-Juanjo
-Juanjo