September 19, 2021 at 5:23 am
I’m well versed in having to send the tracer out through Alembic (and then merging that file back in) to get the traces (with a hair shader and no spline sweep) to show in the Picture Viewer Render (it always renders just fine in the viewport). And in the Picture Viewer, on the odd time it will render, it usually traces from the frame you are sitting on, not from the beginning, so it doesn’t match the view port.
But today, in a rush, I just hit render to check it, made some tweaks and then realized I shouldn’t have been able to do that. The traces showed up, and showed up as though being baked from the beginning.
I checked another project from earlier in the day and sure enough the traces weren’t showing in the renderer.
Initially I thought it was because in one project I used a vanilla emitter and the other used TP, so I switched it up. No difference. That older project won’t let the traces show in a real render.
I had assumed this was a limitation (it always used to be) but now I’m wondering if there is a trick and I just stumbled over it. Now I just wish I knew what that was I tripped over.
I did notice once when deleting an alembic, it kept rendering that geometry even though I had since changed things, so I got to wondering if it was a cache issue.
Am running R24 on Win 10
September 19, 2021 at 3:52 pm
I can’t recreate your issue, at least with older versions of C4D (R19-R22) and simple setups using the Standard or Physical renderers. When I create a hair material, “Hair Render” is automatically added and enabled in the Render Settings, and the tracer renders fine both in the Viewport and Picture Viewer. Are you using another renderer? If not, could you upload a simple example where you experience this so I can try it on my system?
September 19, 2021 at 6:41 pm
I think it might have to do with the Field Force object I’m using. I’m afraid I can’t test on earlier versions as we went straight from R20 to R24 and the middle versions never got installed. (we’re finally past those legacy projects, Yay!)
The field force object got introduced in R21 or R22 I think.
(I don’t think I can save back from R24 – if there’s a way let me know and I’ll send a version for you to try)
There seems to be an inconsistency that points to either expresso or field force that might be causing this and I’m just about to type another post or two on the subject.
Just the standard renderer and physical for now with the tracer. I was going to run this with Vray but I couldn’t get the Vray hairshader to behave as well as the standard.
Am about to try the Redshift hair and see if that makes a difference – As a sidebar, we’re
just trying to pick a new render engine for a project but can’t seem to
get Redshift to install properly. Vray has been the mainstay but I’m not
sure we’re getting all we could out of it now. ( I was hoping Redshift would be native by now and I wouldn’t have to shell out for it as an extra).
Cycles and Redshift look
great while working but the noise in the final renders is a little
concerning. I’ve read that by the time you get all the settings correct for theatrical output (I know… what’s a theater?), sampling, reduced noise, colordepth etc, Cycles and Redshift bog down to the speed where the other big boys run (Arnold, Octane, Vray). When we started with Maxwell back in the day, it was the
best of anything but only for stills and the denoisers were obvious when
blown up on a big screen. I don’t relish going through that pain again.
September 19, 2021 at 8:31 pm
Other than simple stuff, I’m basically ignorant concerning TP and your projects are definitely over my head. Good luck.
Log in to reply.