OcDS UPDATE v1.0.113.2313 - OBSOLETE

DAZ Studio Integrated Plugin (Integrated Plugin maintained by OTOY)

Moderator: BK

Forum rules
Please keep character renders sensibly modest, please do not post sexually explicit scenes of characters.
User avatar
t_3
Posts: 2871
Joined: Tue Jul 05, 2011 5:37 pm

this is an update release for v1.0.111.2049 (and all other subsequent releases)

FIXES
  • "shutting down threads" spinner pops up and won't go away - should be definitely gone.
  • animation rendering stops: the command sequence which restarts octane after every frame is now changed, what hopefully allows to finish animations. the exact reason why this happened is still unclear, but some tests with the changed version did now finish without problems.
  • possible lock-ups when ending the animation right after starting it, or closing ds quickly after stopping animation rendering should be sorted out.
  • possible lock-ups when trying to move the viewport during frame forwards should be sorted out.
  • problems to reset the maxsamples after a animation rendering ends should be fixed. such problems did also occur for cues which mistakenly altered rendersettings if an override maxsamples number was used.
  • a missing embedded file which is needed for the texture (auto-)reload function to work is now included.
  • if the viewport was locked and modal, it did re-open non-modal after once closed.
ENHANCEMENTS
  • smoothing & other background activity that may affect geometries: there is a new checkbox in the "preferences" tab, which tells the plugin to delay geometry reloads until any background activity is finished. a typical example are smoothing iterations (if the "interactive" switch of the smoothing modifier is set to its default state - "off").
    note: there is no way for the plugin to find out what exactly caused background activity; it will happen if smoothing iterations are calculated, but may also happen because of other things (even 3rd party plugins). this might help in particular animation renderings, as the frame forward is held back until any other background activity stops, but may cause missing geometry rebuild during normal rendering (which would then need to be forced by clicking "reload").
  • if the viewport is modal (when the "full" lock is activated, or while animation rendering), minimizing the viewport will also minimize daz studio.
  • misc. additional tooltips and some corrections.
NEW FEATURES
  • it is now possible to hide bones individually.
STUDIO 4.6 COMPATIBILITY
  • from the feedback about the last version, it looks like there are no problems specific to daz studio 4.6, but this still needs some observation.
KNOWN ISSUES
  • under some circumstances material linking may stop working; this is top priority and will be fixed soon.
  • merging a saved scene (which contains octane data) with itself will result in missing octane materials and also missing surface links (basically the resulting scene is just messed up and it is not recommended to continue up from here) - a fix is expected for the next update.
  • opening studio with a scene or opening a scene (or even adding content) quickly after starting daz studio might cause the plugin to fail finally; signs: empty mats trees, empty dropdown boxes for render- and environment settings. if that happens it is recommended to close studio and try it again, waiting a little longer after it has fully opened. from there on it should work fine.
  • if any of the material lists (octane material tree list, daz surfaces tree list) in the “materials” tab is filtered (by text or object), some operations that would tangle materials not in the current scope might fail; so if there are problems dragging something to somewhere, it is advised to check if there is a filter active on the top of the 2 columns.
  • trying to download Live DB materials when offline will still silently fail.
  • there is still the need to provide a mechanism, that allows to get octane/the plugin online manually (or at least allow it trying to do so).
CHANGE HISTORY GET IT! HOW TO INSTALL?
  • if you have already updated the 4 base files (from the last .2305 release), you only need to copy the plordazs.dll from the "plugins" folder, otherwise proceed as follows:
  • please unpack the included files into your daz studio application directory – the zip file contents mimic the needed folder structure; please make sure, that you overwrite all 5 old files in the respective folders with the new ones included in the zip file, and that there are NO DUPES after updating. for a standard install install this looks like so:
    ...\DAZ 3D\DAZStudio4\octane.dat
    ...\DAZ 3D\DAZStudio4\octane.dll
    ...\DAZ 3D\DAZStudio4\OctaneACM.exe
    ...\DAZ 3D\DAZStudio4\vcomp100.dll
    ...\DAZ 3D\DAZStudio4\plugins\OctaneRender\plordazs.dll
  • if you have troubles getting that done, please post here or write me a pm!
HAVE FUN! :D
The obvious is that which is never seen until someone expresses it simply

1x i7 2600K @5.0 (Asrock Z77), 16GB, 2x Asus GTX Titan 6GB @1200/3100/6200
2x i7 2600K @4.5 (P8Z68 -V P), 12GB, 1x EVGA GTX 580 3GB @0900/2200/4400
badmilk69
Licensed Customer
Posts: 122
Joined: Sat Sep 03, 2011 4:24 am

Thank you t_3, just in time! :D
i7 2600, 16 GB RAM, 2x Evga 670 SC 4gb, dual boot win7/osxML, 2 SSDs, 3 HDs.
User avatar
larsmidnatt
Licensed Customer
Posts: 499
Joined: Tue Sep 25, 2012 12:28 pm

thanks for another update. The built in update checker is quite handy :)

Good to know the materials issue is a top priority.
Win10 x64
i9 10900k 64GB
2080S 8GB
DS 4.15 OcDS Prime ^_^
User avatar
Hakankrakan
Licensed Customer
Posts: 9
Joined: Sun Mar 31, 2013 6:06 pm

Thanks! :)
User avatar
orion_uk
Licensed Customer
Posts: 713
Joined: Tue Oct 25, 2011 2:56 pm

Hi t_3 :D

Running an animation sequence now and (so far) the FFRWD issue has NOT shown its ugly head, am currently on frame 600 of 800...

And, Some mats that will not drag n drop in to the Plugin rendering window WILL apply if you drag them from LDB to the surfaces list in the mat tab :D

EDIT: Animation completed with success.
http://www.Neil-Isted.com
Intel i7 870/2.93 GHz
RAM 16GB
1x Titan (6GB)
2x GTX 660Ti 2GB
Win10 Pro 64-bit
Carrara 8.5 Pro
Carrara - OR4C
OctaneRender™ for Blender
Ds pro
OR Standalone V4
Poser Plugin
User avatar
bluerocket
Licensed Customer
Posts: 31
Joined: Fri Mar 29, 2013 2:37 am
Location: Portugal

Thanks t_3

Good work :D

Regards
Asus Rampage IV Extreme | i7-3930K | 32GB | 2x GTX TITAN | 2x GTX670 4Gb | Win 64x
jimgale
Licensed Customer
Posts: 230
Joined: Fri May 03, 2013 5:27 am

giving feedback:

My animation that was originally freezing and rendering the same frame to end, is now doing this instead:
1. frame 332 out of 630, it bombed even DAZ (straight closing, no error window).
2. [unknown if related or not]: I have a jacket on the model which in most frames (of the 333 rendered), fails to 'fit' properly (never had this issue before). [does this now require the 'wait for non-plugin related background tasks'? - if so, that's off at the moment [probably should be on as default so first experience for users is good] - will try].
3. [unknown if related or not]: On at least 1 of the frames, a random firefly appears in an eye - never happened before.

Thanks,
Jim
3dmania
Licensed Customer
Posts: 87
Joined: Fri Apr 05, 2013 9:49 am

Hi T_3,

thanks for implementing the hide bone feature
User avatar
t_3
Posts: 2871
Joined: Tue Jul 05, 2011 5:37 pm

jimgale wrote:giving feedback:

My animation that was originally freezing and rendering the same frame to end, is now doing this instead:
1. frame 332 out of 630, it bombed even DAZ (straight closing, no error window).
2. [unknown if related or not]: I have a jacket on the model which in most frames (of the 333 rendered), fails to 'fit' properly (never had this issue before). [does this now require the 'wait for non-plugin related background tasks'? - if so, that's off at the moment [probably should be on as default so first experience for users is good] - will try].
3. [unknown if related or not]: On at least 1 of the frames, a random firefly appears in an eye - never happened before.

Thanks,
Jim
regarding 2: yes - it is that switch. it defaults to off since i'm still searching for a ~ proper way to generally wait for background tasks, and i don't know yet, if this switch causes other problems; if it turns out to work as expected, i'll change the default. the previous version activated the "interactive" switch in the modifier, but this did only work for animations (if at all), is not guaranteed to help for unknown other background activity, and esp. didn't work for stills (since you usually don't want to have this switch on then). the general wait for background tasks handles both, but i just can't say what else might happen because of it.

regarding 3: was it one of the earlier frames, or one of the last frames that showed the firefly?

regarding 1: how long was rendering going on until reaching 332? did you have any animation before, that rendered close to that frame count? a crash of this sort looks a bit like something system or at least memory related. animations cause some stress not only for the gpu, but cpu/system memory also (because of repeated geometry building... can you pls give me some additional specs (cpu/ram/psu, scene size - triangles/vram, render time/frame, ...). also if you still have the log file from this try it might help; any message from the engine that might appear in the message window ("system" tab) will also get written to the studio log file. what might also reveal something is to watch the memory utilization in the taskmanager - if it constantly grows, there might be a memory leak somewhere. btw, did you watch gpu temps?
The obvious is that which is never seen until someone expresses it simply

1x i7 2600K @5.0 (Asrock Z77), 16GB, 2x Asus GTX Titan 6GB @1200/3100/6200
2x i7 2600K @4.5 (P8Z68 -V P), 12GB, 1x EVGA GTX 580 3GB @0900/2200/4400
Andrey79
Licensed Customer
Posts: 14
Joined: Fri Sep 21, 2012 5:14 pm

t_3 thank you for update!
Post Reply

Return to “DAZ Studio”