Chaos Corona for Cinema 4D > [C4D] General Discussion

3.25 Gb file renders without crashing Mac OS/Studio

(1/3) > >>

frv:
Hi,
just to keep the enthusiasm for CR. I rendered a file yesterday with lots of Maxtree assets up to 3.25 Gb and my Mac Studio 128Gb rendered it all without crashing once even during all the iterations before the final render.
I used the edge trimmer for the grass which works very well since C4D allows you to select the texture opacities and set them on edge trimming all at once.

C4D became  slow though, I could only handle the file in wireframe view . Scene preparing by CR also takes a while, a few minutes.  I wonder if other render engines for GPU rendering would allow for much faster iterations and save time to first pixel. The render times for the final high res renderings are less meaningful to me. Since overall most of my time is spend on modelling, vegetation placement and render interations on low res.

BigAl3D:
Good to know. Sadly, C4D is notorious for slow viewport with large scenes. I don't have the latest version, but haven't seen anywhere that issue has been addressed. I know r25 is snappier than r20.

If your lighting didn't change after initial setup, you can render a low-pass iteration with the GI solution saved to file. Then switch it to Load from File for the remaining iterations. This will save some time, just not sure how much with your scene. If it saves one minute of time to first pixel, that can add up or over many test renders. If you change the lighting, then you need to recalc that file.

Overall a nice image. I do have a few thoughts if you don't mind a fresh set of eyeballs on it. For some reason, the foliage feels over-sharpened. Not sure if you added sharpening in post or in tone mapping, but that how it appears to me.

You may want to fix the corner of the hedges in Photoshop. The bit going parallel to the path is obviously repeating the leaf pattern there. Some carefule rubber stamping easily fixes that.

An odd halo effect on the tips of the branches, especially over the sky.

frv:
Files this big will never really be fast in viewport. Sketchup and Vectorworks are far worse. No idea how 3DSmax is though.
I will check your suggestion on GI from file. This project took about 15 hours modelling vegetation and texturing the buildings, iterative rendering and so on. Getting the libraries from Maxtree took about 2 hours, they really have a slow website... Updating the textures from Maxtree also took some time. I would say that if Maxtree libraries had been easier to obtain, the time to first pixel had been fast and the viewport in C4D was a lot faster this image could be made in a few hours. I charge for these images somewhere between 3 to 400€. It's not my main job and do about  one or two images per month.  This pays for the apps and libraries I use for my own architectural practise.

The image has a purpose but it's not great image on itself. Indeed the hedge could be better and there is a halo around the vegetation near the sky. I can't really get that right since the alpha channel is not that good. I added the sky in PS. I sharpened in Corona and in Lightroom and indeed a bit too much. Adding more hours to this job would improve the image but they liked as it is so left it there.
tx for your comments, greatly appreciated !

BigAl3D:
Yeah, it would be nice if more asset sources would be made available in C4D + Corona. Converting or rebuilding materials is tedious.

You could always use the Corona Clouds feature. Did you use the Sky Replacement tool in Photoshop?

TomG:
You could also try the "Force path tracing" option if time to first pixel is an issue, as this disables calculating the cache in IR only (leaving your final render settings untouched), the purpose being to reduce time to first pixel. If you use an Interactive Viewport (rather than the VFB), you can lower the quality there, it defaults to 50% which should be good, which means it renders the image at half size and upscales it (in a non-AI, everyday way) - may be good enough for doing things like placing vegetation, etc. For the VFB, you could try setting the resolution to half size, and in Corona Preferences raising Image upscaling factor to 2 - same thing, makes the image half size but upscales (non-AI, everyday) it in the VFB though in this case, remember to set the final resolution back before doing a final render unlike the viewport version.

This will depend somewhat on what is taking the time to process, if it's some pre-parsing like calculating displacement or geometry etc. these things may not help as much; about the only thought I have there is to group the scene in such a way that you can turn off elements that are not required when working on certain things.

Navigation

[0] Message Index

[#] Next page