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

[Ken1171]

I think common slave or internal dial names are: PBM, FBM, JCM, ERC, and so on. JCM is just one of many kinds of ERC, so there might be more prefixes that define slave dials that are not controllable by the end user (assuming the creator used proper standard prefix names - this is not mandatory). Legacy DAZ3D figures (mainly Mil.3 and Mil.4) use a different prefix naming for "reserved" channels that modern figures no longer use. When these dials are not used, they will retain the default prefix, but I don't remember that that was. I believe all these prefixes should be filtered out.

Sounds like a great idea to set dial linking to OFF by default, in addition to filtering unnecessary morphs (internal, slave, unused reserved, etc).

[mlru]

Paul,
for me it definitely happened in the step from 2.23.2.48 to 2.23.2.52.
.48 is responsive, .52 and .54 aren't. it isn't depending on a scene, although with bigger scenes with figures in it and the viewport open it get's more noticeable.

[wimvdb]

Other morphs which can be removed are EMPTY and null morphs (it seems it takes hidden dials as well)
The max delay i get with a figure like V4 is about 1 sec, so I certainly want to keep the feature, but the ability to turn it on or off in the configuration is fine with me

[face_off]

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

2.23.2.55
- Add configuration option to turn Dial Linking ON (this is OFF by default).
- Only visible dials are now included in the Dial Linking combobox. This fixes some of the lag issues associated with the Dial Linking feature

Thanks

Paul

[Ken1171]

Awesome, thanks Paul! That should help a lot without the delays on every click. ^_____^=b

Now what can be done about my saved defaults not sticking when I start the plugin?

[face_off]

Now what can be done about my saved defaults not sticking when I start the plugin?

Did you see my comment above regarding this?

Ken, this might be happening because you having saved the Octane settings in your startup scene. If you tick "Launch to factory scene" in the General Preferences->Document that may fix that problem.

Paul

[Ken1171]

Did you see my comment above regarding this?Paul

My Poser default scene doesn't even have a figure loaded by default, so I imagine it can't be that.

I actually got curious from where it was getting those particular materials from, so I checked the figure on scene and she doesn't have them. Even if I reset all materials from the scene (plain white), the plugin still loads the figure with these textures. Using the plugin's "Load from Default" fixes all this, but only until I start a new scene. Here again, none of this was happening for the last 2 years, it only started about 2-3 updates ago. I didn't even change my Octane Plugin saved defaults - it was still the same I have been using for about a year. Until then, whatever state I saved the plugin defaults to, that's what would load up in the plugin defaults next time, but not anymore. The Octane plugin is starting up with values different from what the whatever I have saved as the "defaults". This includes the lighting model and the render dimensions - not just the materials.

If I have saved the plugin "defaults", shouldn't that setup load next time I run the plugin?

[wimvdb]

If you use the "Set Preferred Scene" button in Posers General Preferences, it saves all the materials, cameras, lights, props and figures. This includes the Octane plugin's scene settings.
So if you have an empty scene and have used that scene in Octane with a figure, it will save the material settings of that figure in the Octane scene settings in the preferred scene if you press that button - even if you deleted that figure from the scene.

I think that is what Paul is referring to

It is easy to see if this is the case: Open the preferred scene pz3 file and check if there is an addonData line for Octane (usually the last line in the scene file)

[Ken1171]

Thank you, wimvdb. That makes sense now, thanks for explaining. Where is the preferred state file stored at?

[wimvdb]

preferredState.pz3 is in c:\users\<yourname>\Appdata\Roaming\Poser Pro\10