Octane Render 1.022 beta2.2 RC1 available [obsolete]

[Faizol]

Obj exported from Blender appeared to be black when smooth boolean is enabled, but obj exported from other software doesn't have that problem so far.

Did you check the scale ?

the obj exported was not scaled. I tested out further with Blender's obj export parameters variations, and I found out that this happened when HQ Normals is checked. The black areas didn't appear if just Normals is checked in Blender, or if both Normals and HQ Normals are checked in Blender's obj exporter.

[enricocerica]

Obj exported from Blender appeared to be black when smooth boolean is enabled, but obj exported from other software doesn't have that problem so far.

Did you check the scale ?

the obj exported was not scaled. I tested out further with Blender's obj export parameters variations, and I found out that this happened when HQ Normals is checked. The black areas didn't appear if just Normals is checked in Blender, or if both Normals and HQ Normals are checked in Blender's obj exporter.

Yeah, at least Normals should be activated or both which is the default in the export script we provided.

[YoonKyung]

Focus is different between 8GPU and 1GPU settings;

[eyeinthesky]

Hello,
I also have problems with the 64bit beta 22_RC1 scene very dark vertical stripes in both directlight and pathtracing ..

thanks anyway for your good work

[YoonKyung]

WinXP 64, i7 950, 3x GTX480

Speed is decreased. 11.20 M samples / sec --> 10.49 M samples / sec.

Day light simulation and turn table animation do not display anything, when motion blur is off and multi-gpu is on.

Exit takes long time.

[Felix]

I have no problems so far. Rhino-objs which previously crashed octane are imported correctly now. Vertex normal interpolation stuff works now as expected too. thanks!

[joviper]

Great job ! my multi-GPU device works also with SLI mode enabled.

[radiance]

Hi Guys,

Thanks for all the tests, we've indentified various problems obviously and we will work towards an RC2 with hopefully all these issues fixed and better multi-gpu performance.
I'd like to thank everyone for helping us test this.

Please stop posting known issues here for now, if someone finds a new problem, post it here

Yours,
Radiance

[Dragonian]

Hi! Here is some bugs i've encountered with this build.

Some functionalities lost witch relaying on "float" values
for Example
- Bump map works with Normal map set to "float" value not "floattexture"
- Normal maps ignores "Power" value if it's "floattexture" (if "float" - works fine)

temporary workaround for this: replace "floattexture" with "float" in node editor
or open scene created in previous version all values imported will be "float"
(not converted to "floattexture") that's why bump work in scenes from previous builds


I've noticed problem with Render Viewport,
it happens from time to time while dragging splitter between viewport and node editor,
it looks like RenderView is properly resized but lost its coordinates...
while draggin splitter up - RenderView Goes down (including Rulers) revealing empty space between rulers and "Render Viewport" toolbar
while draggin splitter down - it reveals some "Garbage"
If this happens - only workaround i've found - to save, close and Reopen Octane Render


Opening scene with command line - works fine
(actually i'm just dragging scene over Octane Render Shortcut to launch it)
But than i click "save.." in Octane Render, it opens "Save As.." Dialog, like it's a new scene
(Searching original file with "save as" dialog and hitting "yes" to overwrite - is bit uncomfortable)


Problem with nodes in Graph Editor, step by step:
1. Add two Diffuse materials, and one RGBSpectrum Texture
2. Connect Texture to both materials as Diffuse
3. Delete Connection For Second Material

Consequences:
1. In Node Inspector Diffuse channel of Second Material is Gone Now (as if never exist), and material is seen as Black Color in "Render ViewPort"
2. Connection between Texture and First Material can't be removed at all (even with paused render)
3. Moving Nodes in Graph Editor causes rebuild of Preview after each move,
and it causes eat up GPU RAM after each click or move till all RAM Gone

Tested with 64bit build on Win7 with 197.45 Nvidia drivers

[InfoBrain]

On the first look, this RC is faster then the old version. The mix function is great.
Resolution changing during the rendering dont work with my system, but with this problem, i can live.
My system: Win 7 64 bit, GTS 250, Octane 1.022 beta2.2 RC1 64bit

@ Radiance. You and your team make an great Job.

thanks, but we definately should see if we can fix that... it's quite stable on our hardware setups. (changing res on the fly)

Radiance

Resolution changing during render working here but when using 2 GPU's it seems your new memory manager is not cleaning up after a rez change up or down, new memory is allocated each change and the old RenderFilm Target area not released. I think this is only on 1 GPU because after enough rez changes to max memory, and getting the simplify scene dialog, 50%, the right half of the screen still renders fine, left half is black