OctaneRender™ Standalone 2.00

[emihich]

Sorry - here is the pertinent information:

NemesisCGI wrote:
What is the reason for the 12 GPU limit for the network render?
I have a friend who has 3 systems each with 6 GPU's
Is there any way to upgrade to more than 12 GPU's?


We are working on a number of different options for network rendering in the coming months:

1) Cheaper node license (especially if you are not using standalone and just want a render node)

2) High end network version of OR that can support unlimited render nodes over 10GE boxes designed for render farms. This will be identical to the Cloud Edition we have shown off in the past.

First option is only logical, Option 2 would be Life Savior !!
p.s: please make it easy to use and access ,from the Octane or plugin interface, unlike the former octane Cloud.
Hope this match other users needs.

[abstrax]

Just a quick heads up: I updated the installers to quickly solve 3 issues. You can find the changes in the release notes and decide for yourself if it's worth updating or not.

[radiant]

Dont know if this has been said yet but,

When testing out dis maps, i find that when im in the scene geo with a certain height (lets say 0.5) and i go to the material ball (purpose or by accident) it does not change the scale within the material ball scene thus causing my computer to freeze or crash.
I find that we should have the option to enable the material ball on or off.

[riggles]

Rounded edges seems to be a dud for me, can't get it to work. Either in the MODO plugin or in the Standalone. Simple cube, nothing happens at any value large or small.

[Tugpsx]

Playing with displacement map, not a very pretty picture, but interesting how well it deforms DAZ characters. Heading of to test this on aged characters.

O2SALdisplacement.JPG

[matej]

The translation values in the 2D Transformation node, have no nice sliders like the rotation & scale. When you try to "drag" the value, it just goes in manual input.

sliders-missing.png

(on the pic the value is zero, but it doesn’t show the slider even if it's >0). The Transform Value node also has no visible slider for translation, but when you try to "drag" the value, it works as it should (it doesn't go into manual input mode).

[ROUBAL]

Hi, I have done some tests with the demo : Displacement crashes the GPUs (GPU fail) very often. Selecting the render target also crashes the GPUs. Only selecting an obj node or a geometry group node allow to render... with no control on camera.

[LudovicRouy]

the crash seems to be related with mesh density and scale, and with displacement amount (must startvery low)

[ROUBAL]

the crash seems to be related with mesh density and scale, and with displacement amount (must startvery low)

Yes. I also noticed that images basic parameters like Power, invert, gamma have no influence at all in displacements, and their sliders seem to be useless here.

[smicha]

The translation values in the 2D Transformation node, have no nice sliders like the rotation & scale. When you try to "drag" the value, it just goes in manual input.

sliders-missing.png

(on the pic the value is zero, but it doesn’t show the slider even if it's >0). The Transform Value node also has no visible slider for translation, but when you try to "drag" the value, it works as it should (it doesn't go into manual input mode).

+1