Juan, hi! Let's fix the artifact! E.g. you may look how the UV mapping works if you plug the cntlUVProjection node to diffuse slot of CentiLeo material. In cntlUVProjection you should select the same mapping type as the in the Bitmap which causes the problem. And there we will see what's going on.

Hi Juan, great thanks for file! Nice model btw! I reproduce the problem, there is something wrong either with normals or geometry translation. Investigating it further

Hi Juan, I can't yet reproduce the crash, but haven't looked very deep there because I looked on Max2019-Win7 and Max2020-Win10. Will look deeper today, probably wil rework some open/close render staff.
Did you open IPR and couldn't manually save? Or you closed the IPR and it didn't want to save anyway?

As for artifact - there is a reason: coplanar triangles in artifact area. For the whole artifact area there are 2 triangles and when secondary rays launch from one triangle they meet the z-fighting problem of the duplicate triangle. Removing unneed triangles (and leaving their duplicates) by user clears the problem. But I prefer to fix it on our part. In current version we workaround this problem analyzing triangle IDs and without ray offset. But sometimes there are scenes with coplanar triangles (like this one) and so we will introduce a ray offset render setting. At first time it will be user defined, later we will do things automatically to reduce this not very nice setting.

Quote
Juan Carlos Gutiérrez wrote: I have further feedback and suggestions if you want to hear them.

Sure, suggestions are always welcome!

Quote
Juan Carlos Gutiérrez wrote: Hey there, were you able to check on the crash error?

I hope yes, I hope it was your crash case. At least I have found that it crashed if ever in Max session CentiLeo production rendering mode was used. And a couple of other crashes were fixed. Will upload the fix soon, in 1-2 days (must fix some other things).

Damn, awesome! I appreciate it!

Hi Juan! Almost done, it seems the new solution is working, and a couple of more issues were fixed. The reason of delay is that I didn''t want to sacrifice some memory/speed and there were some conflicting pros and cons here and there (as always). Need to test and release, hopefully soon! In days

Here's an updated render:






The bug is no longer there, also saving the scene no longer crashes max as well. Thanks!