iray error and rendering

dannagiusy64

Since yesterday evening I have encountered a rather unusual problem. As you can see, part of the rendering is not reproduced correctly. Has any of this ever happened to you? how did you solve it? ????

dannagiusy64

I have seen that changing his perspective from the bottom up there is no defect, but as soon as I move it a bit the problem returns. I don't care about this prospect

Richard Haseltine

Judging by the bounding boxes those ar previews, does the same happen in a full render? I have seen one or two othernpeople with simlar issues, but I can't recall how they resolved them.

esha

I've seen something like this when I had several non-finished renders still on the screen and DS started to run out of memory.

dannagiusy64

it often happens to me when I prepare a composition. As you can see, the compromised part is transparent when i start rendering

Richard Haseltine said:

Judging by the bounding boxes those ar previews, does the same happen in a full render? I have seen one or two othernpeople with simlar issues, but I can't recall how they resolved them.

 

Thyranq

I just had the same thing happen to me for the first time.

I went on the "Render Settings" tab, under "Editor", and then "Optimization" and changed "Instancing Optimization" from "Auto" to "Memory" and it fixed it. Changing it to "Speed" reintroduces the problem, but going back to "Memory" fixed it again. Hopefully that's all you'll need to do as well.

davidtriune

I've had this problem before. check your RAM usage. if it's pretty full, chances are it's a memory problem

dannagiusy64

I did what you told me, but the file doesn't recover. It took me a long time to put this composition together, I wouldn't want to repeat everything from the beginning 

Richard Haseltine said:

 

 

Thyranq said:

I just had the same thing happen to me for the first time.

I went on the "Render Settings" tab, under "Editor", and then "Optimization" and changed "Instancing Optimization" from "Auto" to "Memory" and it fixed it. Changing it to "Speed" reintroduces the problem, but going back to "Memory" fixed it again. Hopefully that's all you'll need to do as well.