OctaneRender™ Standalone 1.14

Fri May 03, 2013 9:03 am

I'm guessing it's so that if you rename the input/ or node, you don't lose the information on what type of input/node it actually is - which I have found to be a problem in the past.

Fri May 03, 2013 9:16 am

HI roeland

Linux 64-bit link not working
The requested file does not exist.

Fri May 03, 2013 9:20 am

gordonrobb wrote:I'm guessing it's so that if you rename the input/ or node, you don't lose the information on what type of input/node it actually is - which I have found to be a problem in the past.

Maybe it can be a blank or a number instead of copyname:
"filtersize: filtersize" Could be "filtersize: 0"
A blank might be bettter, because the number might suggest something.
Or "filtersize: name"?
Greetz,

Fri May 03, 2013 9:55 am

rappet wrote:...
A blank might be bettter, because the number might suggest something.

+1

Fri May 03, 2013 11:25 am

abstrax wrote:That's not messed up, it's a feature: We display now the pin name and the node name - not only the node name, which doesn't need to be anything useful.

A feature that looks messed up then

If the names are equal why show them twice?

Fri May 03, 2013 12:27 pm

Great Thanks, for this new one ^^

lens distortion work pretty smoothly ...

EDIT: Not a big deal , but for info, I Still have Octane crashing when I Copy or paste RGB Color HEX Code...

EDIT2: It would be great to be able to add in predefined camera list all cameras nodes created inside the project.

merid888 · Fri May 03, 2013 12:45 pm

thank you, download right now !!
what means •The correct CUDA core count is shown for GTX TITANs ?

Fri May 03, 2013 12:55 pm

if(displayName == name){
displayName = "";
}

I am just going to ask: Are any of our compositing features (that we have been begging
for) going to be in 1.20?... at least Invisible to Camera?

Also, please make gradient available in SDK so plugs can have gradient.

Fri May 03, 2013 1:36 pm

Zay wrote:
abstrax wrote:That's not messed up, it's a feature: We display now the pin name and the node name - not only the node name, which doesn't need to be anything useful.
A feature that looks messed up then If the names are equal why show them twice?

The problem is the following: Previously, pin names were never displayed explicitly - only the node names. The only way to find out the name of a pin was hovering over it and waiting for the tooltip to pop up. Another problem was that if nodes weren't named properly people get confused, because they don't realize that the name could be anything. You see that for example if you create a glossy node and then swap it to specular: The pin is called "reflection" while the node is called "specular", but if you would create the specular node from scratch, the node would be called "reflection". Another even worse example is swapping a diffuse node with a specular node: Now the node connected to the "transmission" pin is called "diffuse". This is highly confusing if you only see the node name.

How about displaying only the pin name and making the node name editable in the node graph editor instead?

It gets a bit tricky with the outliner though, because there you definitely want to see the pin name as well as the node that is connected to it.

Fri May 03, 2013 1:38 pm

FrankPooleFloating wrote: I am just going to ask: Are any of our compositing features (that we have been begging
for) going to be in 1.20?... at least Invisible to Camera?

Unfortunately, code doesn't appear faster if you beg more

Also, please make gradient available in SDK so plugs can have gradient.

We will, we will. When we get to it.