Odd blocks appearing

A forum where development builds are posted for testing by the community.
Forum rules
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
User avatar
FrankPooleFloating
Licensed Customer
Posts: 1669
Joined: Thu Nov 29, 2012 3:48 pm

treddie, why is this bg not a plane?.. why is there thickness? I have done bg ramps as a plane with one UV and never had anything but smooth-as-butter renders...

Also, it does not look like it is getting smoothed in deep channel.. is that normal?

Do you indeed have a UV in this bad-boy?
Win10Pro || GA-X99-SOC-Champion || i7 5820k w/ H60 || 32GB DDR4 || 3x EVGA RTX 2070 Super Hybrid || EVGA Supernova G2 1300W || Tt Core X9 || LightWave Plug (v4 for old gigs) || Blender E-Cycles
User avatar
FooZe
OctaneRender Team
Posts: 1335
Joined: Tue May 15, 2012 9:00 pm

What happens with just the backdrop and daylight rather than your lighting?
Also what about the shading normals? (i'm guessing you posted the geometric
normals? - Frank, this could be why it's not showing smooth).

Thanks
Chris.
treddie
Licensed Customer
Posts: 739
Joined: Fri Mar 23, 2012 5:44 am

Well, alas, the normals are perfectly fine. So it's something else.

Here it is with Daylight, and no custom lights:
Empty Set v1.2 (Cam Pulled Back) DAYLIGHT ONLY.png
treddie, why is this bg not a plane?.. why is there thickness? I have done bg ramps as a plane with one UV and never had anything but smooth-as-butter renders...
That is because this studio was built eons ago for another renderer. As I recall, I was having issues with simple one-sided surfaces. So the polys are unnecessarily high now, but it should still work.
Do you indeed have a UV in this bad-boy?
Only a standard flat projection from C4D, which is only holding a flat white bg (no texture, per say). In Octane, I am not applying any bitmap texture to it.
C4D Setup.jpg
Win7 | Geforce TitanX w/ 12Gb | Geforce GTX-560 w/ 2Gb | 6-Core 3.5GHz | 32Gb | Cinema4D w RipTide Importer and OctaneExporter Plugs.
User avatar
FooZe
OctaneRender Team
Posts: 1335
Joined: Tue May 15, 2012 9:00 pm

That looks to me like scale along the way has become a bit messed up.
Does tweaking the ray epsilon help (smaller or larger?).

Thanks
Chris.
treddie
Licensed Customer
Posts: 739
Joined: Fri Mar 23, 2012 5:44 am

That looks to me like scale along the way has become a bit messed up.
Does tweaking the ray epsilon help (smaller or larger?).
Ray Epsilon was it ! WOO-WHOO!

I had to kick it way up to .06. Also sped the render up a zillion-fold:
Empty Set v1.2 (Cam Pulled Back) CUSTOM LIGHTS ONLY, RE.06.png
Win7 | Geforce TitanX w/ 12Gb | Geforce GTX-560 w/ 2Gb | 6-Core 3.5GHz | 32Gb | Cinema4D w RipTide Importer and OctaneExporter Plugs.
User avatar
FooZe
OctaneRender Team
Posts: 1335
Joined: Tue May 15, 2012 9:00 pm

This probably means your scene is huge and it might pay to scale it down or change the obj import parameters to get it smaller.
(Although as you may have noticed before, if you do this too much and you have really small triangles you run into problems the other way as well - being so small they run into floating point precision errors).

But you should be able to find a scale that fits.

Thanks
Chris.
treddie
Licensed Customer
Posts: 739
Joined: Fri Mar 23, 2012 5:44 am

You're right. The scale was massively messed up. I was working in meters, and I STILL had to scale the seamless up 1000% to get it to match the scale of the rest of the studio. I'm going to rebuild the thing to get it to jive with the real world. Probably explains a number of issues I have been having.

Thanks Chris and Frank!
Win7 | Geforce TitanX w/ 12Gb | Geforce GTX-560 w/ 2Gb | 6-Core 3.5GHz | 32Gb | Cinema4D w RipTide Importer and OctaneExporter Plugs.
Post Reply

Return to “Development Build Releases”