Itoo Software Forum
Forest Pack => Forest Pro (*) => Topic started by: link3d on April 06, 2021, 04:50:40 PM
-
Dear Itoosoft-Forum, when rendering a camera animation with Backburner and Forest 7.0.9 Forest does NOT update the camera clipping on the render slaves!
Forest objects = generate, no distance falloff, camera clipping=5% on
same problem with both camera clipping to viewport= off and on
Any help please,
Thanks a lot, Matthias Link
-
Hi,
What render engine ? Each renderer uses a different implementation...
-
Carlos, thanks a lot for your reply. We are quite desolate because the scene with backburner network rendering worked fine until (i suppose) 7.0.4 (switched to 709 some days ago).
we are working with 3ds max 2021, vray 5.1001, backburner 19005
when rendering locally everything renders fine. when using backburner the render servers ignore the movement of camera clipping - with slow architectural camera movements the first frames are running fine because 5% camera clipping, but then the forest trees are not added to the new moving cameraview.
i´ll try to upload an example scene
matthias
-
i sent a scene to helpdesk@itoo but here its reproduceable with any scene since forestpro 709
vray or max scanline renderer same problem
just take an animated camera with any forest objects and use forest camera clipping and render with backburner.
Matthias
-
We are running into camera clipping issues too but it happens via batch render on local machines also.
Attached image with forest popping in late after being half missing for previous frames. That scene has three forests, inner, mid and outer and the mid forest is actually half visible... so it's not the entire forest just a large part of it.
-
eg4043, same here! But i only tested on backburner....
-
confirmed the frame runs fine if manually set to single frame on one that failed before.
-
Experiencing same issues here over backburner, V-ray5, Max 2021, Fp 709
Trees render fine on single computer, but randomly disappearing at the edges of the frame over backburner
We also have buildings scattered with Fp exhibiting the same behavior over backburner
-
Well, it is not just Back burner, nor just related to batch render.
Have one machine that renders it fine locally and a nearly identical machine that does not.
Also seeing random differences between nodes on the farm.
Wondering if it might be an issue with the forest pack being originally a fp6 setup... Will try rebuilding it in fp7 from scratch.
-
I'm fairly certain the issue is the camera clipping does not work properly when you render a fp6 forest with fp7.
I screenshotted all the forest settings and created a new one and basically copied the old forest to make a whole new forest from scratch and the issue is gone. I did it for a single forest only to test and that forest is working fine but the older ones still have clipping problems.
I think when FP7 renders an FP6 forest the camera clipping does not update beyond the first frame expansion area so if you move outside of it it is not generating assets.
A work around might be sending the job to backburner with every 100 frames or some subset range so you stay within the clipping zone.
If i start a new node from the farm on the job mid way, it has different clipping issues to the node that was rendering from the start, which somewhat confirms this theory.
-
We could reproduce the problem with Scanline rendering, but not with V-Ray.
Anyway, we found a couple of issues that would be related.
They are fixed in FP 7.1.0 (https://forum.itoosoft.com/announcements/forest-pack-litepro-7-1-0/). Please, test it and tell us if that helped.
-
I will test tonight - if it does not fix things I'll get the scene over to you guys.
-
Seems to have fixed it! Check your scenes guys with 7.1.0. I'll come back if there is another problem.
-
Glad to hear that!
We are ready to solve any issues You have asap. And thank You for submitting Your issues, so we can improve software for everyone.
-
still NOT working here with 7.1.0 with backburner. it seems to be a bit less worse, but there are still some random trees missing sometimes on some machines with moving camera. changed the camera clipping % from default 10% to other settings, but no difference.
Matthias
-
Would You please send (https://forum.itoosoft.com/faq/how-to-send-a-file-to-itoo-software/) us the scene to test it here.
-
Roca, just take the same one I sent on Wednesday 7 April, Forest standard Date Palm animation. I also created a new Forest, same problem.
-
Can You please tell me, if You can reproduce the issue on one pc submitting and rendering via backburner server/manager on one PC ?
-
Roca, I will create a brand new scene now from scatch and test with backburner. Maybe there is any "old" forest information from 6.0.9 left behind in the scene....
Matthias
-
Don't bother Matthias, finally we could reproduce the problem here using Scanline. There was a stupid bug, which is not completely solved in FP 7.1.0.
Although for some reason, everything is working fine in our tests with V-Ray.
We're completing several tests yet. I will send you a custom patch tomorrow, so you can test it as well.
Apologies for all the inconveniences.
-
Carlos, Rocas,
completely new 7.1.0 scene WORKING FINE on backburner now. we tried also a mixed backburner setup with one OLD rendernode running the forest 7.0.7 version (that was the last one working fine here).
We are running an real existing project with forest objects created sometime ago with backburner and forest 7.1.0 tonight an see what´s happening there.
Matthias
-
Hi I have a related issue, not sure if I should start a new topic though:
on any orthogonal or perspective view, when I scroll the frames in the timeline the camera moves but the far clipping plane doesn´t automatically update. It only works in the camera Viewport and only if the Viewport is selected.
Same problem even if the "View to Render" is locked on the camera Viewport.
It would be nice to have it fixed on the next update.
Thanks!
3dsMax 2020, Vray 5.1
-
Carlos, Rocas, we had a "complex real project" Backburner job now rendered with 7.1.0, everything fine, no plopping trees even with generate mode!
Matthias
-
Glad to hear that. Weird that we could not reproduce the issue here with 7.0.9 and Your scene.
-
That's great. Anyway, the problem with Scanline was not completely fixed in 7.1.0.
It should be solved with next update.