@@Ricardo-de9ju "Freeze Geometry When enabled, all geometry information, such as the radius of a parametric cube object or the point positions of a polygon object, is frozen to avoid re-translating the geometry for rendering. Changes to the geometry are no longer visible in the current render." - C4D Redshift Manual It's going to speed up the render view since you're not having to calculate these geometry updates.
Ok, what the function does is clear, it stops the render view from updating changes in the view port regarding point positions. But why would you want this, just pause the render view, update your geometry and start it again. That's why it is not clear, should have some specific usage, because it doesn't make sense. @@the-astropath
@@Ricardo-de9ju It would be very useful if you're working on a complex animation. I find it to be helpful. If you don't think you need to use it, then there's no need for it I suppose :)
This is very niche was hoping this would be a video about general performance when not working with tessellation. Redshift really struggles as your scene grows.
Compared to what? Seriously, RS is the fastest, most versatile engine out there. I was literally suffering when I was using Arnold. Octane is good, but speedwise RS is the king.
@@kratos_1335 I'll be honest, I find Octane to be generally faster than Redshift. But I like Redshifts workflow. Arnold is slow but it's mainly a CPU renderer. I will say Arnold is more stable than Redshift or Octane in my opinion. They're all great for different situations it just comes down to preference.
@@the-astropath Arnold GPU is slow as hell too. I moved to Redshift from Octane. Redshift shines on heavy scenes with lots of AOVs, where Octane just freezes at some point.
@@kratos_1335 That's great you enjoy Redshift so much! It's my main render engine but I think Octane and Arnold are worth learning for certain projects.
Note - Instead of saying displacement at the start of the video I probably should have said "Tessellation or Subdivision".
Also in the RV Renderview window you can go to View>IPR Undersampling and increase it for faster IPR updates. I keep mine on 2, nice and snappy.
That's another great tip!
Thanks for taking the time
great.. thank you :)
Not quite so clear when can we apply the freeze geometry feature.
When you're adjusting lighting and materials. Animating Cameras etc. Essentially the Look Dev phase.
Ok, but what's the relation to make it faster? The object is not moving anyway or deforming, why would you want to freeze it?@@the-astropath
@@Ricardo-de9ju "Freeze Geometry
When enabled, all geometry information, such as the radius of a parametric cube object or the point positions of a polygon object, is frozen to avoid re-translating the geometry for rendering. Changes to the geometry are no longer visible in the current render." - C4D Redshift Manual
It's going to speed up the render view since you're not having to calculate these geometry updates.
Ok, what the function does is clear, it stops the render view from updating changes in the view port regarding point positions. But why would you want this, just pause the render view, update your geometry and start it again. That's why it is not clear, should have some specific usage, because it doesn't make sense. @@the-astropath
@@Ricardo-de9ju It would be very useful if you're working on a complex animation. I find it to be helpful. If you don't think you need to use it, then there's no need for it I suppose :)
This is very niche was hoping this would be a video about general performance when not working with tessellation. Redshift really struggles as your scene grows.
Did you find it helpful? I can definitely compile a list of tips to help with overall performance.
Compared to what? Seriously, RS is the fastest, most versatile engine out there.
I was literally suffering when I was using Arnold. Octane is good, but speedwise RS is the king.
@@kratos_1335 I'll be honest, I find Octane to be generally faster than Redshift. But I like Redshifts workflow. Arnold is slow but it's mainly a CPU renderer. I will say Arnold is more stable than Redshift or Octane in my opinion. They're all great for different situations it just comes down to preference.
@@the-astropath Arnold GPU is slow as hell too.
I moved to Redshift from Octane. Redshift shines on heavy scenes with lots of AOVs, where Octane just freezes at some point.
@@kratos_1335 That's great you enjoy Redshift so much! It's my main render engine but I think Octane and Arnold are worth learning for certain projects.