OctaneRender for Carrara 2.24.0079 [Test] Tweet

[Sighman]

WARNING: This version has had limited testing. Use at your own risk!

Changes in 2.24.0079

• UV Mapped Hair is now working.
• Octane shaders used in hair can now be renamed without loosing the link.
• Added a Lock Octane Shaders command. This command creates hidden instances for all the hair shaders in use. This allows you to use the 'Remove Unused Masters' commands without loosing your hair shaders.
• Mapped the Carrara Fractal Noise shader to the Octane Noise shader. Although it's far from perfect it does give better results in most cases.

Quick Notes:
Carrara hair is now rendered in Octane using the Octane hair system. Note that this feature is now considered complete. There is an Octane Hair effect that allows you to edit the Octane material used by the plugin if you are not happy with the auto-generated one as well as an option to enable UV mapping on the hair. Do not replace the Carrara Hair Shader with an Octane Shader because it will break the hair rendering.

To get hair to work I had to use the same geometry used by the Carrara viewport. This means that what you see in the Carrara view port is what you see rendered. Many hair models do not display all the hairs in the viewport by default so you need to enable 'Show and Calculate Generated Hairs' and set the 'Display Percentage' to 100%.

As usual, please let me know if you find any other issues.

ATTENTION: This version is based on Octane 2.24. That means you need to update your NVIDIA graphics drivers to at least version 344.x

Happy Rendering...

Download Links:
OctaneRender for Carrara (64-bit) 2.24.0079
OctaneRender for Carrara (32-bit) 2.24.0079

[Sighman]

UV Mapped Hair (YIPPY!)

Meow

[PhilW]

Thanks for the latest update, great work, it all seems to be working well from my initial tests. Much appreciated!

[dustrider]

Thanks Sighman!!

[wendyluvscatz]

I really must visit here more often, but then I was without my PC a few days, got a 980ti in it now though too so gonna render fur fur fur!!! wheeeeeeee
many thanks and hugs Sighman

I seemed to have lost the live data base upgrading though (did motherboard too to i7) hope can fix with this install too, is all still activated, I keep finding weirdness since the mobo swap all over the place though in different programs so kinda relieved that's all that went awry.
My non functioning stereo mic the worst symptom so far, and my screaming bee software, Carrara and Octane came through relatively unscathed considering.

[PhilW]

Hi Sighman, I just loaded a few shapes to test something and noticed something odd. All the shaders in this scene are Carrara's default, and so should be perfectly smooth, but they look like they have noise applied. I know that you did something with noise in the last update so I am wondering if this is applying a bit of noise, even where there is none in the original shader?

[PhilW]

The concentric rings on the plane are relative to the camera and appear more pronounced as the camera angle gets steeper (more overhead). They should not be there, there is just flat shaders and Realistic Sky. Plus noise on the spheres.

[Sighman]

Can you export the scene and load it into the standalone to see if the same thing happens there. I have a feeling this is a scale issue or perhaps it is something specific to Octane 2.24

[PhilW]

Hi Sighman, You were right - I had Carrara's scene scale set to large having been doing some terrain mapping stuff, when I set the scene to medium, all is normal again. I don't really see why that should give these artifacts though? But at least it has cleared up my immediate issue, so thanks (once again) for that!

[Sighman]

This phenomenon has to due with the precision of floating point values and the Ray Epsilon setting in the kernel. If we had infinite precision we would not need an epsilon since all calculations for ray bounces would be perfectly calculated however this is not the case. Octane uses single precision floating point values which means there are only about 7 digits of precision. The default epsilon (.0001) was chosen for "medium" sized scenes where you are dealing with an area less than 100 meters in size. When you pick a large scene you need to increase epsilon to prevent floating point rounding errors from distorting the bounces (say .001 or .01). If you are interested in very small scenes or extreme close-ups then you should decrease epsilon (.00001 or .000001) so that you capture the fine details.

http://fuzzyphoton.tripod.com/rtref/rtref_e.htm