Hey, I rendered with 2 different virtual machine, the exact same scene. But see the sky clouds:
They jump to different position, but stars stay put.
So I cannot render with multiple sessions / VM machines scenes with Night Sky environment?
interesting. are you using cloud time at all, Pekka? also, are there any components of the sky that you are animating?
do you mind testing something (since i don’t have access to multiple machines to prove it out)? i am curious if by activating cloud time inside the SkyMaterial or shader could ‘lock’ the position of the clouds across machines. since these clouds are mostly likely procedurally generated like in UE.
just throwing ideas out, it may not fix the issue.
Sure. just give me to this test…
THX @Simplychenable !
You are engaging Weather and using the “Randomize” command. Hence never the same, random, not repeatable. This is a dynamic random effect applied at render time. Different machines are going to run their own random version. Please try turning this Weather off.
1 Like
Thanks!
It looks like it is something else too, that makes those seams/jumps on rendering.
See here I have the Weather tick ON:
you can see there is a seam on renders. This was done locally on my workstation, I just re-booted Omniverse and rendered the same scene again.
Then I took the tick OFF from Weather:
But still there is a seam:
What could this be?
And to be clear this jump only occurs when rendering across multiple machines ? If that is that case please just render on one machine until we identify the bug. You could render on multiple machines with the sky hidden and render with an alpha channel and then just render the sky only on one single machine and comp them together.
Sorry but answer is NO, this was done with my single A6000 GPU.
Only few minutes of delay and Composer reboot in the middle…
1 Like
Ok so its a single machine BUT not a continuous render output. You broke it into TWO separate render sessions ? It seems like this has some kind of really random element that needs to be rendered out directly and continuously in one output stream.
Can you try one more render, this time straight out all the way, even on low res, just to test. Then I know exactly how to file the bug.
ok, good news.
There is no seam with the Random -feature turned OFF.
I checked it two times:
so it was my mistake. It works as it should :)
Pekka
Great !! Yes I thought that would fix it. So I am glad you got it working. Random is certainly “random”
1 Like
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.