Home Creators Posts Import Register Favorites Logout
haven't archived this post yet. have a subscription? use the importer!

Content

Playing with the new RS 3.0 Trace Depth values, its a subtle difference but that extra ray depth adds nicer reflection/refractions inside of the Diamonds, and the interiors almost "glow" with more bounce light occurring. I think people who render a lot of glass shots with close-ups will greatly benefit from the 4x higher trace depths, the addition of the environment exit color also helps.

In the older 16 Trace Depths complex refractive objects ray trace depths terminated to black much sooner.

This first build includes the following updates with more tech arriving soon.

 

Higher Trace Depths

Redshift will now support up to 64 diffuse, reflection, refraction bounces and 256 transparency levels. While this sounds like a trivial change (as in “we just changed some limits”), that’s not actually the case! We had to rewrite a lot of Redshift internals which, as an added bonus, sped up the rendering core by a good few percentage points! You should notice better GPU utilization as part of that, too!

Sampling/shading optimizations

This initial release will not enable (yet!) the automatic sampling feature because we discovered some issues with it. But there are other optimizations in place (part of automatic sampling) which will help speed up rendering further. It goes without saying that we’ll continue working on automatic sampling and once we feel it’s consistent enough (as: renders with both great visual quality and faster than before), we’ll release it. This is one of the most high-priority items currently!

RTX (RT core) support

There have been a good few posts about that one already. The support is still not on 100% parity with the legacy CUDA-based ray tracer. Certain features might not work (like light/mesh links or trace sets) but we’re working hard to either make them work or to transparently fall back to the legacy tracer (with some warnings). The good news is that the RT cores will work for the majority of features and they will work well. There are very very few cases where we found RTX to render slower than our own code. The “typical worst case scenario” is for RTX to not render that much faster compared to the legacy ray tracer. With your help, we hope to find and fix any problematic cases!

Lighting AOVs through transparencies and refraction

Some of the work we had to do to achieve higher trace depths has opened the possibility for having lighting-related AOVs (diffuse/specular/etc) visible through transparency and refraction. Comp ninjas know that this was not possible in Redshift (except for custom AOVs) until now.

Improved secondary ray clamps

Even though this system was revamped on 2.6, there could still be some cases where secondary rays could be clamped in a wrong way which could produce energy loss. The secondary ray accuracy has been increased in 3.0.

Improved light group AOV fidelity

Similar to the above, the light group AOV math was, in some cases, producing precision inaccuracies, resulting in ‘ghosting’ artifacts in the final comp. This inaccuracy has now been addressed.

Coming soon: DeepEXR improvements

The increased trace depths and the modifications in the core has produced a few issues with our Deep EXR tech so we’ll be looking at revamping it. Some people have complained about the amount of memory it uses as well as other things like the lack of VDBs in it. We’ll use this as a chance to revisit and fix those topics.

Coming soon: NVLink support

Once RTX support solidifies a bit more, we’ll be enabling NVLink. We’ve already done some preliminary tests and and we think it’ll work pretty nicely. There is a bit of a performance hit but it beats either 1) Going excessively out of core (which is a bit hig) or 2) Totally failing to render the scene (which can happen with VDBs)

Coming soon: Native C4D noises, without baking (on all 3d apps!!)

This is a nice benefit of the Maxon deal. Cinema4D’s powerful noise nodes will make an appearance in Redshift! And our goal is to have these available not only in C4D but on all 3d apps!

RedshiftRT

While still not ready to show anything yet, progress has been nice on that front. The main effort with it is to make sure that it works (and looks) as similar to the “full” Redshift as possible. Except in realtime. This is a very technically challenging project but things are moving nicely and we hope to be able to at least tease something in the next few months.

Others

Work has already begun on OSL support as well as “full” OCIO support (for textures, etc). The aforementioned automatic sampling support is also just the first step in a more general “revamp Redshift’s sampling” task. The goal there is to have a system that achieves cleaner images with as few rays as possible. This includes scenarios like ray traced caustics, many light situations and others. Much more stuff in the works still.

Enjoy the update!

Files

Previews only

Comments

Oliver Banasiak

Do you know of any good resources to dig into regarding OSL? Preferably for someone without a degree in computer science! I would love to be able to understand what can be achieved before it arrives!

Saul Espinosa

Just read about it from the Arnold OSL page or from the Sony Imageworks Github page. Its a shading language similar to C#, very powerful and very useful. Once OSL drops two of my shader wish list requests are fullfilled just by having OSL. (iridescent shader and flakes shader) Check this video as it gives a rough run down on what it means and can do. (all these open-source 3dsmax OSL shaders for example will work in RS when full OSL with closures arrives) https://youtu.be/SJZWAqlzqS8

Matt Barker

Thanks for these updates!

zoubein

Exciting stuff, but I am not sure about the Redshift RT what does it mean? Dont we already have that? or is that for unreal and unity.

Saul Espinosa

Redshift RT is short for Redshift Real-Time, which is going to be something like Unreal Engine with Raytraced shadows, Gi, etc. It is more like an advanced game engine mode like Unreal/Unity/Eevee for lookdev and viewports etc but can also be used for final renders if the quality is good enough for the user. The idea is you will be able to switch between RS RT and RS Ray-tracer (what we have now) seamlessly and using the same shaders etc. Redshift RTX RT Core support is something completely different and that has already arrived in RS 3.0