tricks for faster renders? (materials, lights)

Hasdrubal — if you render a lot of scenes with single spotlights then I'm not going to fight you, but really? Spotlights don't appear in reflections, which is a pain (in fact, physical spotlights would be a hugely useful addition since building them out is a pain).

If you actually want to render something that looks vaguely photorealistic, HDRI-driven image-based-lighting will get you there faster and cheaper than basically any other option.

The specialized shaders, like dielectric, are more efficient than the general purpose shaders like Material or PBR to do the things they do, because instead of evaluating a function call deep in the bowels of the shader (what's the diffuse of this pixel?) it's a constant. It's not a huge effect (it doesn't change the O(n) (edit weird subtitution) of the shader, but it does change its constant coefficient). Blurred reflections or caustics or extra lights have geometric costs.

Distributed rendering would be great as would GPU acceleration.

All of the tricks mentioned aren't going to make a 60h render happen super fast, but there's a big difference between 60h per frame and 2h per frame.
 
Last edited:
Pod, if you'd had roughly read what I wrote, you'd know that this is only about the topic here. For bwrtz a very simple lighting may be enough, and with the Cheetah renderer (which I never used) I thought spots should reflect. I don't think this is about getting 60 h per frame down to 2 h, but more 5 minutes to 1. For bwrtz 'photorealistic' simple is not an option, so the tips here are only usable in such circumstances. He seems to look for tricks to cut even seconds from a frame which in an animation can amount to quiet some time. So, for example, dielectric may give better results, but a very simple cartoony glass material should be faster in this case. I actually don't believe that I would like the result, but each his own. As I said before, it's not important what I like or not but that bwrzt get's the results he is looking for.

For myself I don't always use hdr but mostly. And you can get photorealistic results with area lights etc.; only in Cheetah (as I wrote before) it's almost impossible without hdris to get a good result. So, while I try to optimize my scenes to a certain degree, quality is the most important thing for me. So I don't care much if a pbr takes a few minutes longer to render instead of another material if the result is not what I'm looking for. Like I already said quiet a few times, to a certain degree I stop optimizing and use planing instead, so I can render for a few hours without being unable to do my work.

I don't think Cheetah will ever get GPU acceleration. What's possible is full GPU-rendering with ProRender, which sadly, is still not developed far enough to be production ready. I don't know what AMD did in the last couple of years, but the software is still not very far advanced, quiet a lot of materials are a problem and so on. By the way, with very simple scenes as the topic of this thread, it can even be slower than cpu rendering (it takes more time to send the date to the gpu than rendering it out in such cases). The other downside is of course the simple fact that you'd need quiet good hardware. NVIDIA has simple so far more advanced in such things that AMD is simple no match. Even AMD's denoising isn't half as good (Intel denoising seems interesting but I don't know if that really has a future on MacOS).

> Network rendering

Network rendering would indeed be a good thing, but I don't know how big the demand for it actually is. Is it really worth it for Martin to open that can of worms? It's probably enough work to do it (programming render nodes and stuff), but even when it's done perfectly well, it still doesn't work for all people because of their network, the available (usually older) hardware that they can use as nodes and so on. I remember well when I tried it the first time in Lightwave and Vue, where it took me ages, to find what's wrong with my network to get it to function. But most people don't see it that way: They usually blame the developer. Back then, for me it wasn't worth it in the end. It was better to use the older computer for 'normal' work, like writing, accounting and so on, even some graphics (that could even be painting a texture), and using the top notch computer for heavy stuff only (that included 3d, some heavy graphics and games). I could have used the 3rd pc which I usually kept as a ready reserve system, but that would have gone to far.

Today, I have to admit, I do use it a lot. I'd be in a fix without it (and had to shell out big money to get top hardware).

But all this stuff about distributed and gpu accelerated rendering is a bit lost in this topic. Not because it doesn't help bwrtz in his task (I often digress myself) but because it's about something very, very specific that's actually of no interest for most Cheetah users. I don't think bwrtz uses much that wasn't available already in Cheetah 5. It should be quiet clear that I usually never would recommend what I did here because the resulting quality is only of use for unrealistic scenes.

Network and (e)gpu rendering on the other hand would be of interest for most of the people here. This stuff shouldn't be buried in this thread.
 
* I have been using my "old" iMac27 as a pauper´s render farm. It sits just behind my desk on a separate slim filing cabinet, sufficiently elevated to be easily visible / accessible. An alternative would be one of these mobile TV bracket gadgets which can be bolted to a wall.
* The two Macs are connected via a thunderbolt cable and some adaptor, from memory a bit under €100. File sharing needs to be activated, of course. Shuffling C3D documents (.jas to the back, renders and animations to the front) is a trivial matter.
* Whenever required, I can also use this iMac #2 as a second monitor for manuals, to display research stuff or whatever.
:whistle: Not ideal, but if obsolescent but functional hardware exists, an inexpensive alternative.
 
@Helmut: I'm not sure if that's what you mean in your last point. But to use an iMac as a monitor for another computer isn't possible anymore since the 2015-series (which is a shame. Would be great to have that possibility with a new mac pro).
 
@Hasdrubal — Yeah I was talking general principles vs. specific scene, but this seemed to be how the discussion had evolved. Even so, I suspect using a "baked" HDRI would be faster than even a single spotlight (but you'd need to find or create the right HDRI).

I think you're right C3D isn't going to get GPU accelerated rendering, which is why these days I'm having more fun with Blender 2.8.

@Helmut As for using spare macs as render slaves, have you tried using "share screen"? You can directly use any Mac as a render slave by (for example) sticking your files in a shared folder and just "screen sharing" over to the other Mac and firing off the render. No cables required!

(I use screen sharing all the time to help my kids or give them "time extensions" without walking over. Also my old Mac Pro has an nVidia video card which occasionally stops working when the OS gets an update, and I screen-share over to update its graphics drivers.)
 
@ Swizel
Absolutely Beautiful Render - Wow !!!
Looks like it was well worth the wait.
Thanks for sharing.

https://www.cheetah3d.com/forum/index.php?threads/13339/post-116167

Jeanny
Ha thanks Jeanny!

I wish I could take credit for the scene design, but those were actually done by someone else. I've just been tasked with setting up the renders. Each movie is taking about 2 or 3 days to do. Wish I had more hardware to throw at it, but that's an expensive proposition as we all know. If they throw more work my way in the future, I could justify probably buying a dedicated Windows machine with several GPU's in it. I do freelance work on the side of my regular day job to support my hardware / software habit. :p

At least the easy thing with the rendering is once the render settings are in order, I can just leave the machine to do it's job. It would be nice to output them faster.
 
Back
Top