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

[wimvdb]

I definitively prefer the plugin to store the octane changes in the scene itself
If I load a scene again I want exactly the same result as I had before

I often use the Save as Poser material as a base to experiment further with the materials. Overriding that during save of the scene would make that impossible.

[aRtBee]

hi Paul,

though about that too, but in my personal opinion the "robust'' and existing solution is the much preferred one as indeed there are so many ways (and tools) to ruin the Poser Mat Room. So storing Octane Material defs back into Poser Mats should be a secondary tool, to be used when saving / retrieving those figures / props / scenes into/from the Library and eventually to safeguard them against losses of any unexpected kind.

Well, the plugin already has a tool for doing so at the figure / prop level, and I suggested something alike on the scene level (looping through all scene objects) plus eventually the ability to trigger that function when closing the plugin panel (which then gets triggered too on closing the Pose scene or the Poser program). Even in a more luxury setup: the option to have that in "auto" mode (don''t ask) or in "manual" mode (to be confirmed yes/no each time, meant for very large scenes). See earlier posts from people that tend to remind vital actions when it''s too late.

Just thinking out loud.

In addition to all this, one has to remind that clearing all Octane settings from the Poser scene will not clear the Mat Room defs, in my view. Poser Mat Room has a tool for clearing (removing) detached nodes, per material or even per figure / prop, but lacks the ability to do so for the entire scene. This is why I suggested a script for that as well.

aRtBee

[Ken1171]

I have installed version 2.23.2.54 and noticed the material nodes have become unresponsive during editing. When I click a material node to change a value, CPU activity goes high and the plugin becomes unresponsive for like 5-10s. It keeps doing that for every material node I click. Today I have started a new scene and the same thing happened again. This only happens on the materials tab. Sometimes the entire panel goes blank for 5-10s.

Has anybody else experienced this?

[face_off]

I have installed version 2.23.2.54 and noticed the material nodes have become unresponsive during editing. When I click a material node to change a value, CPU activity goes high and the plugin becomes unresponsive for like 5-10s. It keeps doing that for every material node I click. Today I have started a new scene and the same thing happened again. This only happens on the materials tab. Sometimes the entire panel goes blank for 5-10s.

Ken, I suggest rebooting and reinstalling the plugin. What Nvidia drivers do you have installed? Which version of the plugin did you update from?

Paul

[aRtBee]

I don't have any of these issues, sorry. Works fine.

[mlru]

I have installed version 2.23.2.54 and noticed the material nodes have become unresponsive during editing. When I click a material node to change a value, CPU activity goes high and the plugin becomes unresponsive for like 5-10s. It keeps doing that for every material node I click. Today I have started a new scene and the same thing happened again. This only happens on the materials tab. Sometimes the entire panel goes blank for 5-10s.

Has anybody else experienced this?

yeah, I noticed that, too. not as long as 5-10s, but a noticeable lag in selecting nodes. I thought, it was due to the tooltips now popping up and was about to ask if they could be disabled in the settings (it's a nice help, but in most cases I don't need them)

[face_off]

yeah, I noticed that, too. not as long as 5-10s, but a noticeable lag in selecting nodes. I thought, it was due to the tooltips now popping up and was about to ask if they could be disabled in the settings (it's a nice help, but in most cases I don't need them)

I wonder if it could be the new Dial Linking mechanism? This feature was introduced in 2.23.2.53. You could test this by installing 2.23.2.52, seeing if the pause is present - then installing 2.23.2.53 and again checking for the pause.

Paul

[mlru]

will check when I get home this evening.

[wimvdb]

I don't see the delay. Response time is immediate, no delay whatsoever
I am using PP2014 game dev, latest SR and NVidia driver 353.30

[ThetaGraphics]

I've been experiencing that delay as well, not very consistently, but sometimes it freezes up for several minutes. Always happens on nodes set to Greyscale Color, especially when you first open the plugin I think...

Hmm, after a bit of testing, it seems the delay is longer the deeper the node is in a material mix hierarchy. At the first level, (such as a simple glossy node), the delay is only about a second, but the deeper you go, (in this case, several material mix levels into a RedSpec shader, the delay is a couple minutes.