Gernge Quick Tips - Redshift Render Settings Walkthrough | Cinema 4D Redshift
Фильм және анимация
This quick tip goes through my Redshift Render Settings Preset. We briefly cover unified sampling, the sampling overrides, global illumination settings as well as the optimization cut offs. These settings serve as a great starting point for me, usually not requiring much tweaking other than turning on and off certain Sampling Overrides as necessary.
Please use these as a starting point, and make adjustments based on the types of scenes you work with frequently! Personally I am okay with renders taking a while, usually, so I have my sampling settings higher than default.
This render setting preset only needs to be setup one time, since it can be saved and easily reloaded into future scenes.
Walkthrough the Redshift Render settings, information should apply to Redshift in other DCCs.
00:00 Introduction
00:35 Unified Sampling Settings
01:03 Sampling Overrides Explanation
02:07 Global Illumination Settings
02:34 Optimization Cut-off Thresholds
03:00 Legacy Settings & Bucket Size
03:51 Saving & Loading Render Settings Presets
__________________________
Subscribe: @gernge
My Website: gernge.com/
Twitter: / _gernge
Instagram: / gernge
Пікірлер: 16
Clearly compiled in one place and well explained. Love it.
Another hot one. I'm usually in your camp of doing bigger buckets at 256 but Rob told me to drop down to 128 on most of my stuff and really ends up saving me (on a single 3090) almost 30-40% in speeds on my work. Definitely takes pulling and pushing on values to find what works best, great overview.
@gernge
Жыл бұрын
bigger buckets can definitely be taxing on the memory! interesting balance between the bucket size vs potential Out of core memory use, but thank you for enjoying the overview. i hope this one serves well as a quick one to point users to within the community!
This is so helpful! Thank you man. Keep it coming. Straight to the point, no BS. Love it.
excellent analysis. briefly and succinctly!
Love it. Thanks Billy!
This saved me hours.
Thank you!
thank you Bro!
Nice one! Can you also list your version of redshift, c4d version and even your drivers?
@gernge
6 ай бұрын
thank you! to answer, the specific RS version used is shown in every clip during the intro title card. C4D R21 as shown at the top bar of the program, and I use 497.29 Game Driver
Interesting. Personally, I use a threshold of 0.1 during development and 0.05 to 0.01 for final renders (good enough for KZread). So far I have not encountered a scene where a smaller bucket size was faster than a larger one but I have had situations when I would need to reduce the bucket size for RS to render at all. Unless I missed it, you did not talk about RTX on or off. In my experience, RTX on is usually but not always faster.
@gernge
Жыл бұрын
those sample settings are pretty close, i'd still say! and obviously whatever works best for an individual is what i'd recommend. i just propose these as a starting point that should be decent compared to completely default settings. the bucket size topic is going to be very individual, will depend on users' scenes & their hardware i touch on the RTX setting in an upcoming tip about render interactivity. i turn ot on and off while working, but definitely always have it enabled for my final renders
Would you recommend using denoiser inside the redshift or maybe like after effects or smth, because im using Altus Dual and it not only removes some details but also takes ages!
@gernge
11 ай бұрын
i only like using Neat Video Denoiser in AE. none of the options in Redshift (for c4d) are temporally aware, that is, they don't analyze the data from frames before or after and so the result isn't as good for animation which is mainly how i work. so with that being said, i do not use any of the Redshift denoisers, and Altus Dual takes a long time because the 'Dual' mode means it renders the entire frame twice in the background, which is just far too inefficient for my needs personally. hope that info helps!!
@vitaly3415
11 ай бұрын
@@gernge Thank you for the info!