OTOY Forums

have we fixed the "Turn All Displacement Nodes Off" problem yet... going through a Stonemason scene is so tedious finding the displacement nodes that have been set to displacement... time for some global settings that work... like... "Turn All Displacement Nodes to How things were before button"

I'm not aware of any problems with the "Convert Displacement Maps" Setup option. What is the specific issue are you having?

Paul

face_off wrote:

have we fixed the "Turn All Displacement Nodes Off" problem yet... going through a Stonemason scene is so tedious finding the displacement nodes that have been set to displacement... time for some global settings that work... like... "Turn All Displacement Nodes to How things were before button"

I'm not aware of any problems with the "Convert Displacement Maps" Setup option. What is the specific issue are you having?

Paul

This....
First set "Convert Displacement Maps" to checked
Load prop
Errors....

This....
First set "Convert Displacement Maps" to checked
Load prop
Errors....

Deane - what release of the plugin are you running?

Paul

face_off wrote:

This....
First set "Convert Displacement Maps" to checked
Load prop
Errors....

Deane - what release of the plugin are you running?

Paul

2.20.0.39

2.20.0.39

If you reconvert all materials from Poser using that release of the plugin, it will stop those errors from occurring on that scene. And I believe that the next release of Octane will also suppress that log message. It is caused by Poser props having a negative displacement.

Paul

face_off wrote:

2.20.0.39

If you reconvert all materials from Poser using that release of the plugin, it will stop those errors from occurring on that scene. And I believe that the next release of Octane will also suppress that log message. It is caused by Poser props having a negative displacement.

Paul

Yes true... I think this has been discussed before... but for the blokes and blokesses out there.. can we start to think how we can create a global preferences file... like... turn this off, turn that on... only that feature... not displacement... turn that on... bugger that... yep turn that on... sort of thing... or maybe I'm just lazy and should go through each prop and figure and change all the trillion of nodes I don't want set to what default Octane for Poser sets them to.

RGUS wrote:

face_off wrote:

2.20.0.39

If you reconvert all materials from Poser using that release of the plugin, it will stop those errors from occurring on that scene. And I believe that the next release of Octane will also suppress that log message. It is caused by Poser props having a negative displacement.

Paul

Yes true... I think this has been discussed before... but for the blokes and blokesses out there.. can we start to think how we can create a global preferences file... like... turn this off, turn that on... only that feature... not displacement... turn that on... bugger that... yep turn that on... sort of thing... or maybe I'm just lazy and should go through each prop and figure and change all the trillion of nodes I don't want set to what default Octane for Poser sets them to.

I have to agree Deane, it IS tedious as hell...depending on what your scene consists of. I spend way more time in the Octane than I do creating the scene in the first place! Besides what you mentioned, a multi-select/replace would sure come in handy! And since I do not back-tell to Poser, I don't care what poser's limitations are.

But from a programmatic point of view, I can appreciate the challenge. Unless Paul can come with a nifty solution, I've just resigned myself to doing it the hard way.

turn this off, turn that on... only that feature... not displacement... turn that on... bugger that... yep turn that on... sort of thing

That's not a particularly specific feature request. Happy to add enhancements to the plugin, but they need to be described unambiguously and in detail so I only need to code them once.

a multi-select/replace would sure come in handy!

This is do-able, but how does the plugin handle the situation where you have selected a material and sub-node within the material - would the "material" menu items (like "Reconvert from Poser") be available? What about if you select a boolean pin ("Smooth") and a float pin ("Roughness") - what is going to be displayed in the Node Edit box in that situation?

Paul

face_off wrote:

a multi-select/replace would sure come in handy!

This is do-able, but how does the plugin handle the situation where you have selected a material and sub-node within the material - would the "material" menu items (like "Reconvert from Poser") be available? What about if you select a boolean pin ("Smooth") and a float pin ("Roughness") - what is going to be displayed in the Node Edit box in that situation?

Paul

Yep. Like I said, I can certainly appreciate the challenge. Maybe some others can chime in and give suggestions.

Sam

BTW, I am NOT really complaining. I think your plugin ROCKS! Keep up the excellent work!!

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

2.21.0.40
- Compiled with Octane 2.21 (see Octane Standalone thread for details).
- Added Light Passes (you can now assign a Light Pass to each Emitter, and then view each light pass as a Render Pass). See http://render.otoy.com/manuals/Poser/?page_id=369 for details.
- Added Out-of-Core Textures - where texturemaps can now be stored in CPU/Motherboard RAM if graphic card VRAM is full. Enabling this sets the RAM limit to your total RAM amount. Mouseover the Viewport status panel to see out-of-core statistics
- Fixed issue where HDR Light Studio light picking was still happening when Render Region was enabled
- Added Materials tab menu options to Copy Material To Clipboard and Paste Material From Clipboard - to allow copy/paste of materials between the plugin and other Octane plugins or Octane Standalone

Paul