OctaneRender™ Standalone 2.03

[abstrax]

Hi all,

This is a maintenance update for version 2, fixing more bugs and issues reported on the forum.

Changes since version 2.02:

• Improved displacement rendering speed in those cases where the displacement texture does not change much over the surface of a triangle.
• Fixed various displacement render issues (e.g. black triangles on the eye lids of characters).
• Fixed kernel hangs due to displacement mapping.
• Fixed incorrect texture preview of bump mapped materials.
• Fixed kernel failure when a mesh emitter with zero scale and non-zero translation is rendered.
• Fixed Octane incorrect conversion of the Alembic import preference "flip face normals" (versions <= 2.01) to the new preference "winding order" (versions >= 2.02). This should fix issues like http://render.otoy.com/forum/viewtopic. ... 92#p193992.

Download

Windows
- 64-bit installer
- 32-bit installer

Mac OS X
- 64-bit installer

Linux
- 64-bit archive

Happy rendering,
Your OTOY NZ Team

[merid888]

thank you for new update

[prodviz]

Cool, cheers.

The untonemapped .exr output is still dark.

And the cap on the PMC depth is still 32.

[mib2berlin]

Thank you, have more time for Octane now.

Cheers, mib

[gordonrobb]

Does the displacement fix, fix the issue when using displacement fro ZBRush? Ie ones you have to dial bak the shift to allow for the fact that some of the displacement is mean to be negative?

[ROUBAL]

Great, Thank you !

I have just tested the Side by side Stereo mode. I needed that for a while, and it is a great feature, but to be fully usable, a Crossed eyes Mode would be welcome !

To look at large stereo images on a regular screen without special equipment , the simplest method is by crossing the eyes. So the ability to generate an image with left view on right side and right view on left side is required.

Human eyes can't diverge, but can easily converge.

Please could you implement this in a future release ?

[aLeXXtoR]

Fixed Octane incorrect conversion of the Alembic import preference "flip face normals" (versions <= 2.01) to the new preference "winding order" (versions >= 2.02). This should fix issues like http://render.otoy.com/forum/viewtopic. ... 92#p193992.

Yes, that fixed, thank you!

But... I've found one another issue... It's pretty strange but works this way for me: there are some meshes in my scene created with Marvelous Designer (coat and it's details in my example) imported via OBJ-files and others are created in Blender internally (the cap, for example).

So if I turn off the displacement for the materials of the Marvelous Designer's meshes, everything is rendered fine, the stuff like motion blur, depth of field are present on the image: http://f6.s.qip.ru/Dbzb2GXx.jpg
But if I turn on their displacement, render starts look like this: http://f6.s.qip.ru/Dbzb2GXz.jpg (no MBlur, DoF, etc. Moreover if the number of passes reach the value of 600 and higher (if it even reaches), my videocard drivers may fail and Octane shuts down (and this is the tragedy of this story).

The most confusing thing here is that there are some materials that work fine for the meshes created with Blender, but doesn't work for the meshes by Marvelous Designer, which is strange, because I can't really say where's the difference if I use OBJ to transfer meshes. For example Zhukov's cap uses the same materials, that set to his coat (http://f5.s.qip.ru/Dbzb2GXy.jpg for example), but the cap is rendered fine in both cases.

This problem appears in all Octane 2.xx versions. I used Blender integration plugin 1.55/4.10 to create the alembic file.

I've sent the Octane package link via PM, maybe it will help.
Thank you!

[Rikk The Gaijin]

[*] Fixed various displacement render issues (e.g. black triangles on the eye lids of characters).

Unfortunately for me, the issue is not fixed...
It's better than before, but I still get artifacts around eyes and ears...

bug.jpg

[Karba]

At least

It's better than before

We are working on displacement. It is no so easy to make as in CPU renders.

[aLeXXtoR]

We are working on displacement. It is no so easy to make as in CPU renders.

Indeed it is! Thank you for your work! Noone blames you, I think. We're just reporting the issues.