Probably should have increased the AA a bit more.... 49 mins at 1920 x 1080 with Cache + Estimator in GI

Daz, > excellent job on the sky. My rendering is a screen capture. exporting a higher resolution, I'm sure would be a little nicer. I went with a different look, not as exciting as yours and Majoâ€™s . I focused on the water and changed a lot of settings. Because I changed the water material I think the water plants need some work before I use them.I did a default quality Global illumination fine > 3522 secs on my laptop. It's a really nice drawing to work with and Turbo acted well

Looks good Dean.... the higher sun position does highlight the material bump mapping better. I see the fish

The sun locations in all RSE and RSL settings I played around with trying to get the same as the original and like I have mentioned before, we can use larger numbers which give us more accuracy with positioning see attached:

I used Bryce 7.1 Pro to create the background image and applied it to a large single facet rectangle (Draw a Rectangle/Modify 3D object/Create Surface/From Profile)with the same IOR (1.001) as the trees so the transparency works with tone mapping. I added 50% burn also.

I was trying to create the same mood as per Majo's link to the original render:

I too downloaded and rendered this drawing. Absolutely beautiful. I am hoping to find time to dissect the settings, such as materials, luminance, and scenes to learn more about REDSdk rendering.

My render times: Using the settings under 'active drawing' which is whatever Majo set rendered in 35 minutes. Setting to Quality or Advanced render Ray Trace Fine was about 384 seconds, GI fine was about 464 secs. I tried setting to "Use GPU', but I got errors saying "Server Busy". After hitting "Retry", it began to render, but seemed to be in an infinite loop during the Raytrace phase. Could be a problem with my system, or my GTX 660 just isn't capable of this level of rendering. OR, TCad is still not ready for 'Real time rendering'. (sure like to get my hands on a new GTX 1070).

This is Global Illumination Fine. It took 354 seconds to render to screen (1598x877) and 516 seconds to render and save to file (1920x1080); it would have been 523 seconds if scaling by image resolution.

I couldnâ€™t resist, making this a good test for 2106 converting redstuff materials to lightworks materials and rendering with the LW plugin. Being that the file consisted of surface objects I was able to do this in Deluxe 2016 in a reasonable amount of time. Without the water lilies it rendered in 34 secs, with the lilies 540 secs.Itâ€™s a screen capture,I used lightworks quality full render style.Thanks again Majo, for supplying us with an excellent file to work with.

I couldnâ€™t resist, making this a good test for 2106 converting redstuff materials to lightworks materials and rendering with the LW plugin. Being that the file consisted of surface objects I was able to do this in Deluxe 2016 in a reasonable amount of time. Without the water lilies it rendered in 34 secs, with the lilies 540 secs.Itâ€™s a screen capture,I used lightworks quality full render style.Thanks again Majo, for supplying us with an excellent file to work with.

You are welcom Dean ( all this is not my merit ) and nice work with LW, I stopped working with it 2-3 years ago

I took Majo’s updated pavillon_barcelone_v1.3_TC2018.TCW and rendered it under Redsdk for the following 4 configurations:Quality / Global Illumination StandardQuality / Global Illumination FineAdvanced / Exterior_ with the GPU radio button OFFAdvanced / Exterior_ with the GPU radio button ON

The Use GPU radio button is found under the Ray Trace window pane in the RedSDK / Edit popup. It had been there under TurboCAD 2016, but disappeared under 2017 (which, from my investigations, selected the CPU for Quality renderings and GPU for the Advanced renderings).

Majo, and a few others, can explain how the Exterior_ setting differentiates from GI Fine far better than I, so I won’t even try.

What is most noticeable is that the timing and results between CPU and GPU are so different. Previously, GPU renders (at least, with graphics cards sporting significant capabilities in this area) resolved significantly faster than CPU renders, but that is not the case here.

The time for the file Majo provided, when rendered to a 1200x900 JPG file, is 1482 seconds (24 min, 42 seconds).

If the Use GPU radio button is activated, the time is 7160 seconds (40 seconds less than 2 hours).

GPU rendering is not going to give good results as the following from the Redway3D Docs explains:

"The rendering of the realistic material on the GPU is quite slow due to the complexity of the parameters it handles. Most parameters are properly supported on the GPU except the transmission glossiness texture and the reflection glossiness texture that are both ignored if the material is rendered using a GPU."

Well, that is annoying. The entire purpose of a GPU is to get better results, faster, not worse results, slower. What was RedWay thinking?

Jeff

It is early days for GPU with RedSDK but with each build they are improving the performance and options available. Many render engines that offer both GPU and CPU render options have quality differences as they handle approximations, materials and lighting differently...With Majo's drawing the materials that have high glossiness for realistic values, which if the GPU cannot perform the roughness approximation, then the materials become to reflective as one example.All these things could be improved by adjusting the render settings, setting up the render manager to preview the material using the GPU etc but it currently depends on what your priorities are speed vs quality results.