I had rendered for 12-ish hours straight and all of a sudden Octane refused to continue render due to an error (and "check your log" message).
I tried restarting the render, but I kept getting the same error.
What I did next was restart LightWave, and continue where it left off. The random colors node for the trees did of course.. randomize.. Which left the render useless.
I thought some of the reason there's a given seed you can input, that the colors won't change from startup to startup. Something to look into, or.. I don't know.. Be able to save some information to load the next time, and especially in case of re-renders anyway.
Render stopped - random colors randomized on continue
Moderator: juanjgon
Hi,
So do you say that if you put a seed number (not 0) in the RandomColor Texture node and you restart the render, the colors change like in the posted video? This can be a bug, or a problem in the LW instancing system and it's random seed system.
Thanks,
-Juanjo
So do you say that if you put a seed number (not 0) in the RandomColor Texture node and you restart the render, the colors change like in the posted video? This can be a bug, or a problem in the LW instancing system and it's random seed system.
Thanks,
-Juanjo
- Attachments
-
Yes I'm quite sure I click-dragged the button next to the text field to generate a seed.
I will double check when I'm back home in a few hours to confirm.
I will double check when I'm back home in a few hours to confirm.
Modo & LightWave 3D | Win 10 x64 | RTX 2080 Ti | Threadripper 2920x | 128GB
Here's a screenshot of the surface setup for the leaves.
I performed a F9 render of frame 20 which I then compared to a frame from the animation, long before the animation render failed. They did not match.
Then I compared with another F9 render, after the shift in the animation render. The new F9 render I just performed and frame 186 (about the place where the shift happens in the video above), match.
So I'm thinking; every time I close the scene, even if I have just opened it, I'm prompted whether I want to save the object. Perhaps that does something to the seed? All though the number itself doesn't change, something does? Speculation of course. But I just cannot understand why this'd happen.
If in doubt, I can assure you I had absolutely no interest in going into the surface editor and change the seed when the animation failed to render completely in one go, and I found the only way to get Octane to behave again was to shut down LightWave and re-open the scene, edit the starting frame number and hit F10.
Then I compared with another F9 render, after the shift in the animation render. The new F9 render I just performed and frame 186 (about the place where the shift happens in the video above), match.
So I'm thinking; every time I close the scene, even if I have just opened it, I'm prompted whether I want to save the object. Perhaps that does something to the seed? All though the number itself doesn't change, something does? Speculation of course. But I just cannot understand why this'd happen.
If in doubt, I can assure you I had absolutely no interest in going into the surface editor and change the seed when the animation failed to render completely in one go, and I found the only way to get Octane to behave again was to shut down LightWave and re-open the scene, edit the starting frame number and hit F10.
Modo & LightWave 3D | Win 10 x64 | RTX 2080 Ti | Threadripper 2920x | 128GB
Interesting.. it looks like the trees shading changes by an offset (down & right,, or depending how you look at it) almost like it wraps a scrolling counter like in the old scrolling computer days (where I could see this happen as well) Not saying it is anything like that at all.. just that it reminded me of it.