it's probably going to be called the "crashes-be-gone-edition" (yet to be proven true
)NOTES
the new versions .3410 and .3413 did use multithreaded materials and textures processing. unfortunately there is no way to make that work reliably for the majority of users, so this is now finally dumped.
the good thing: the plugin won't work notably slower because of that, nor does this notably increase the time to load materials.
the bad thing: the plugin will block the studio ui when processing quantities of maps; until now you could work in studio while the plugin was processing stuff in background - this is no longer possible. if you don't plan to work with the plugin right away you may want to turn auto mats off, to save a bunch of seconds extra waiting.
note: if you don't have the plugin pane open all the time, you will of course only notice that because the ui is blocked; i'll add an additional progress popup for this case in a next version.
btw, there is an action (usually in the render menu), that you may ideally also place into a toolbar (to have it at hand quickly), it is called "OctaneRender Materials":
it toggles between:
- full auto mode ... the plugin creates/deletes octane materials whenever the scene content changes
- manual mode ... the plugin doesn't catch up to content changes by itself, instead you need to use the "missing" button in the mat tab to create oc mats for changed contents
- .duf only ... the plugin doesn't create octane materials automatically, but will still load new oc mats from saved .duf contents (if there are any embedded).
FIXES
- the plugin should no longer block daz render settings dimension/ar adjustments, as long the octane vp is closed
- fixed mismatched vram size display when usage is > max. available vram (hopefully)
- fixed wrong auto-rayepsilon updates when changing render settings
- fixed wrong auto-rayepsilon updates when resizing the viewport
- non-standard daz materials should no longer receive a zero opacity (hopefully)
- fixed a bug causing no oc mats to be created for content entirely loaded before the plugin is fully initialised
- fixed explicit unlinking oc mats not working when done from within the oc mat tree
- emitters are correctly placed into the emitters group when loaded (scene + preset)
- recalling recent folders (as well as maps) in the image menu will work for long folder names/paths
- removed mistakenly multiplied entries in the image menu (for the scene objects sub menus)
- the locked viewport when having a scene with no oc mats and no camera should be resolved
- saving a scene with unlinked daz surfaces will no longer freeze ds
- removed wrong node type selector when switching from *.* to a value node in the nge
- fixed a bug causing orphan render settings/environment entries after loading a scene
- fixed a bug that caused a render restart when switching between the render settings/environments tabs
- fixed a bug causing render settings and environments to be randomly selected after loading a scene;
note: this is only completely solved after re-saving a scene saved with an older version. - fixed a bug causing the post processing state to be not saved with the scene
FEATURES
- added an "unlinked only" filter to the daz surfaces tree filter box
- added another keyboard shortcut: ctrl-shift-u to unlink currently selected oc materials
KNOWN ISSUES
- preview rendering is temporarily turned off to find a better method for rendering preview updates in background (as this was causing issues in the nge).
- when having the nge (or main plugin pane) floating, the image preview might shift the active window state in a way the floating pane gets hidden behind other panes; could not clearly reproduce this yet.
- under some circumstances scene contents are duplicated each time a scene is loaded again - if this happens to you, pls drop me a note as i currently only have 2 reports about that, and no definitive single reason why it happens; most probably when loading a full scene with the content browser (you may try file > open instead) but it might also have other reasons yet to be found out.
- if i didn't catch up with a particular issue, or if you still have some issues that you had reported already - pls report back once again... thanks!
CHANGE HISTORY
- please refer to this post: http://render.otoy.com/forum/viewtopic.php?f=44&t=30137
GET IT!
