OctaneRender® for Poser (Windows/OSX) 3.03.3 [OBSOLETE]

[RGUS]

But looks like you can't post video to the forum.... bugger

[face_off]

But looks like you can't post video to the forum.... bugger

Compress to ZIP and post that. Or upload to Dropbox and post the link.

And... where do i find that "OctaneDefaults.py" file again... hate Windows file structure.

http://render.otoy.com/manuals/Poser/?page_id=32

So what i'd like to be able to do, is pick the 'Mesh' say and right click and change all nodes to 'Diffuse' in one pick.

Sorry, this didn't make the next release, but should be in the one after...

Paul

[face_off]

I have refreshed the installers at the top of this thread with:

2.23.1.48
- Compiled with Octane 2.23.1 - so Kernel->Keep Environment is back
- Added Animation output save format "EXR All Passes" - to save all the render layers in separate layers in the EXR file for each frame
- Added addition error checking when processing missing texturemaps to prevent unicode encoding exceptions.
- Fixed Octane error occuring when starting to render an animation with the Viewport already open.

Paul

[mlru]

- Added addition error checking when processing missing texturemaps to prevent unicode encoding exceptions.

YAY, works like charm, thanks for that!
The prompt for the correct location is very helpful, indeed!
Just to be annoying : could you do that for material import, too? It seems in general to be a good idea for all places where textures are not found - they might have been moved to another location in the meantime?

This version also seems to have fixed my crash problem on closing. I'll keep an eye on this.
(I noticed, Poser stays quite long in memory even after it's gone from the monitor screen. Not sure, if it has always, though.)

Uwe

[face_off]

Just to be annoying : could you do that for material import, too? It seems in general to be a good idea for all places where textures are not found - they might have been moved to another location in the meantime?

Importing materials uses the same function, so searching for texturemaps should work there too. However if you import a very old material, it uses a different method, where searching texturemaps is not supported.

Paul

[mlru]

more texture stuff :
I do have some pretty complex shaders which use combinations of texture maps in the bump node (by multiply)
I can export and import these shaders with no problems, but when I right-click and try to copy/paste it directly to another material zone I get an error message about copying not allowed because of multiple bump maps.
I don't think, there's a restriction to only one bump map per shader in Octane?

[face_off]

I do have some pretty complex shaders which use combinations of texture maps in the bump node (by multiply)
I can export and import these shaders with no problems, but when I right-click and try to copy/paste it directly to another material zone I get an error message about copying not allowed because of multiple bump maps.
I don't think, there's a restriction to only one bump map per shader in Octane?

The plugin can copy a node network from one material to another, but there is a limitation in that there can only be one Image node connected to the Bump pin (and one to the Opacity pin, one to the Diffuse pin, etc). For example, you could not paste a material which merges 2 texturemaps into the Bump pin into a material which only has a single Image node in the Bump pin because it wouldn't know which Image node to use.

Paul

[mlru]

I do have some pretty complex shaders which use combinations of texture maps in the bump node (by multiply)
I can export and import these shaders with no problems, but when I right-click and try to copy/paste it directly to another material zone I get an error message about copying not allowed because of multiple bump maps.
I don't think, there's a restriction to only one bump map per shader in Octane?

The plugin can copy a node network from one material to another, but there is a limitation in that there can only be one Image node connected to the Bump pin (and one to the Opacity pin, one to the Diffuse pin, etc). For example, you could not paste a material which merges 2 texturemaps into the Bump pin into a material which only has a single Image node in the Bump pin because it wouldn't know which Image node to use.

Paul

Yes, but in this case an existing [image] node would be replaced by a [multiply] node (with 2 images attached). So there's no reason for deciding for one image because the complete node is to be replaced by a node of a different type?
The import works different compared to copy/paste then?

[face_off]

Yes, but in this case an existing [image] node would be replaced by a [multiply] node (with 2 images attached). So there's no reason for deciding for one image because the complete node is to be replaced by a node of a different type?

Hi Uwe - when you Paste (Retain Existing Texturemaps), the plugin would not know which texture to plugin into the second texture of the Multiply node. If you Paste (Use Copied Texturemaps) it just replaces the entire node structure, so the "one map per pin" limitation is not there.

The import works different compared to copy/paste then?

Import works the same as Copy/Paste. ie. Paste (Retain Existing Texturemps) is the same as Import (Retain Existing Texturemaps).

Paul

[RGUS]

How's that 'right_click_change_all_to_diffuse' update coming Paul?... haven't seen a hint of it yet.
And I suppose that flashing updating material tree with every change is still out of the question.