Daz Studio Pro BETA - version 4.12.2.60! (*UPDATED*)

1141517192074

Comments

  • marblemarble Posts: 5,869
    marble said:

    Does anyone know how to view the graph editor in the new timeline? I can see I have a split panel - the top one with keyframes (so I assume this is the replacement for KeyMate) but the bottom panel is unpopulated and I can't figure out how to view the content.

    In the top part of the pane, the Dopesheet, select a property by clicking its name - the lower part of the pane will then show the graph. You can also quickly see the graphs by enabling Monitor Paramaters in the option menu (the lined button in the top corner, or right-click the tab) and just hovering the mouse over the property name.

    Thanks Richard, I'll give that a try.

     

  • Leonides02Leonides02 Posts: 1,300
    barbult said:

    Can someone double-check for me...

    In the new Beta, I can no longer save a canvas (like for HDR) if I use the spot render. 

    That's a pretty big deal. 

    I can confirm that this happens for me, too. Spot Render to a New Window, followed by saving the rendered image, creates canvas files in DS 4.11.0.383, but not in DS 4.12.0.67.  @Leonides02, have you submitted a help request?

    Yes, help request submitted!

  • Daz 4.12.0.67 crashes with the first dforce hair I have tried to render; https://www.daz3d.com/dforce-lea-hair-for-genesis-3-and-8-femaless.  Renders fine with standard hair.

  • Malawolf said:

    Daz 4.12.0.67 crashes with the first dforce hair I have tried to render; https://www.daz3d.com/dforce-lea-hair-for-genesis-3-and-8-femaless.  Renders fine with standard hair.

    Tried my save file of dF Lea Hair that am keeping for benchmarking. For whatevs it is worth, that hair worked fine for me with this latest beta .67.  

     

     

  • I get these WARNINGS.. and render to movie is terrible slow, the render windows crash but still manage to make the movie but is ULTRA SLOW...

    2019-09-02 20:12:32.142 Iray [INFO] - IRAY:RENDER ::   1.1   IRAY   rend info : NVIDIA display driver version: 431.70

    2019-09-02 20:12:32.142 Iray [INFO] - IRAY:RENDER ::   1.1   IRAY   rend info : Your NVIDIA driver supports CUDA version up to 10.1; iray requires CUDA version 10.1; all is good.

    2019-09-02 20:12:32.149 Iray [INFO] - IRAY:RENDER ::   1.1   IRAY   rend info : Using iray plugin version 5.0-beta, build 317500.3714 n, 19 Jul 2019, nt-x86-64-vc14.

    2019-09-02 20:12:32.280 Iray [INFO] - IRAY:RENDER ::   1.1   IRAY   rend info : CUDA device 0 (GeForce RTX 2080 Ti): compute capability 7.5, 11 GiB total, 9.09105 GiB available, display attached

    2019-09-02 20:12:32.280 Iray [INFO] - IRAY:RENDER ::   1.1   IRAY   rend info : CUDA device 0 (GeForce RTX 2080 Ti): WDDM driver used, consider switching to TCC driver model if no display needed (via 'nvidia-smi -dm 1'), to increase rendering performance

    2019-09-02 20:12:32.284 Iray [INFO] - IRAY:RENDER ::   1.1   IRAY   rend info : iray photoreal CPU fallback is enabled.

    2019-09-02 20:12:32.285 Iray [INFO] - BLEND:RENDER ::   1.1   BLEND  rend info : Plugin "blend render" (build 317500.3714, 19 Jul 2019) initialized

    2019-09-02 20:12:32.285 Iray [INFO] - IRAY_CLOUD_CLIENT:NETWORK ::   1.1   IRAY_C net  info : Plugin "iray_cloud" (build 317500.3714, 19 Jul 2019) initialized

    2019-09-02 20:12:32.285 Iray [INFO] - IRAY_CLOUD_CLIENT:NETWORK ::   1.1   IRAY_C net  info : Plugin "irt_cloud" (build 317500.3714, 19 Jul 2019) initialized

    2019-09-02 20:12:32.289 Iray [INFO] - IRAY_CLOUD_CLIENT:NETWORK ::   1.1   IRAY_C net  info : Plugin "nitro_cloud" (build 317500.3714, 19 Jul 2019) initialized

    2019-09-02 20:12:32.289 Iray [INFO] - IRAY_CLOUD_CLIENT:NETWORK ::   1.1   IRAY_C net  info : Plugin "iq_irt_cloud" (build 317500.3714, 19 Jul 2019) initialized

    2019-09-02 20:12:32.289 Iray [INFO] - IRT:RENDER ::   1.1   IRT    rend info : Plugin "irt" (build 317500.3714, 19 Jul 2019) initialized

    2019-09-02 20:12:32.289 Iray [INFO] - EIAXF:IO ::   1.1   EIAXF  io   info : Plugin "axf importer" (build 317500.3714, 19 Jul 2019) initialized

    2019-09-02 20:12:32.293 Iray [INFO] - ICB:IO ::   1.1   ICB    io   info : Plugin "cb_importer" (build 317500.3714, 19 Jul 2019) initialized

    2019-09-02 20:12:32.294 Iray [INFO] - IRAY_CLOUD_CLIENT:NETWORK ::   1.1   IRAY_C net  info : Plugin "iray_bridge_snapshot" (build 317500.3714, 19 Jul 2019) initialized

    2019-09-02 20:12:32.294 Iray [INFO] - IRAY_CLOUD_SERVER:NETWORK ::   1.1   IRAY_C net  info : Plugin "iray_bridge_server" (build 317500.3714, 19 Jul 2019) initialized

    2019-09-02 20:12:32.294 Iray [INFO] - EEMI:IO ::   1.1   EEMI   io   info : Plugin ".mi exporter" (build 317500.3714, 19 Jul 2019) initialized

    2019-09-02 20:12:32.298 Iray [INFO] - EIMI:IO ::   1.1   EIMI   io   info : Plugin ".mi importer" (build 317500.3714, 19 Jul 2019) initialized

    2019-09-02 20:12:32.299 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : CUDA device 0 (GeForce RTX 2080 Ti): compute capability 7.5, 11 GiB total, 9.09105 GiB available, display attached

    2019-09-02 20:12:32.299 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : CUDA device 0 (GeForce RTX 2080 Ti): WDDM driver used, consider switching to TCC driver model if no display needed (via 'nvidia-smi -dm 1'), to increase rendering performance

    2019-09-02 20:12:32.304 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : iray photoreal CPU fallback is enabled.

    2019-09-02 20:12:32.304 Iray [INFO] - IRT:RENDER ::   1.0   IRT    rend info : Resource assignment for host 0 has changed.

    2019-09-02 20:12:32.304 NVidia Iray GPUs:

    2019-09-02 20:12:32.304 GPU: 1 - GeForce RTX 2080 Ti

    2019-09-02 20:12:32.304 Memory Size: 10.9 GB

    2019-09-02 20:12:32.304 Clock Rate: 1665000 KH

    2019-09-02 20:12:32.304 Multi Processor Count: 68

    2019-09-02 20:12:32.304 CUDA Compute Capability: 7.5

    2019-09-02 20:12:32.358 Iray [INFO] - SCENE:IO ::   1.0   SCENE  io   info : Loading module "::nvidia::lights_photometric" from "C:\Program Files\DAZ 3D\DAZStudio4 Public Build\shaders\iray\nvidia\lights_photometric.mdl".

    2019-09-02 20:12:32.358 Iray [INFO] - SCENE:IO ::   1.0   SCENE  io   info : Loading module "::daz_3d::property_annotations" from "C:\Program Files\DAZ 3D\DAZStudio4 Public Build\shaders\iray\daz_3d\property_annotations.mdl".

    2019-09-02 20:12:32.358 Iray [INFO] - SCENE:IO ::   1.0   SCENE  io   info : Loading module "::daz_3d::basic" from "C:\Program Files\DAZ 3D\DAZStudio4 Public Build\shaders\iray\daz_3d\basic.mdl".

    2019-09-02 20:12:32.405 Iray [INFO] - SCENE:IO ::   1.0   SCENE  io   info : Loading module "::daz_3d::irayubermaterial" from "C:\Program Files\DAZ 3D\DAZStudio4 Public Build\shaders\iray\daz_3d\irayubermaterial.mdl".

    2019-09-02 20:12:32.423 Iray [INFO] - SCENE:IO ::   1.0   SCENE  io   info : Loading module "::nvidia::axf_importer::axf_importer" from "C:\Program Files\DAZ 3D\DAZStudio4 Public Build\shaders\iray\nvidia\axf_importer\axf_importer.mdl".

    2019-09-02 20:12:32.447 Iray [INFO] - SCENE:IO ::   1.0   SCENE  io   info : Loading module "::nvidia::core_definitions" from "C:\Program Files\DAZ 3D\DAZStudio4 Public Build\shaders\iray\nvidia\core_definitions.mdl".

    2019-09-02 20:12:32.471 Total class factories: 2124

    2019-09-02 20:12:32.471 Iray [VERBOSE] - IRAY:RENDER ::   1.1   IRAY   rend stat : Environment cache size capacity: 5.

    2019-09-02 20:12:32.474 Creating Script Engine...

    2019-09-02 20:12:32.490 WARNING: 3DConnexion Plug-in Error: Could not create Device, CoCreateInstance failed

    2019-09-02 20:12:32.490 3D mouse support library could not be loaded.

    2019-09-02 20:12:32.491 Creating Main Window...

    2019-09-02 20:12:32.492 Creating Viewport Manager...

    2019-09-02 20:12:32.547 Successfully created OpenGL viewport for Viewport1.

    2019-09-02 20:12:32.673 Successfully created OpenGL viewport for Viewport2.

    2019-09-02 20:12:32.791 Successfully created OpenGL viewport for Viewport3.

    2019-09-02 20:12:32.873 Successfully created OpenGL viewport for Viewport4.

    2019-09-02 20:12:32.956 Creating Action Manager...

    2019-09-02 20:12:32.966 Creating Pane Manager...

    2019-09-02 20:12:33.116 Successfully created OpenGL viewport for AuxViewportView.

    2019-09-02 20:12:34.054 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): peer performed orderly shutdown errno=0

    2019-09-02 20:12:38.453 Updated metadata for 0 of 1 items.

    2019-09-02 20:12:38.579 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(660): sync completed successfully, 1 items succeeded, 0 items failed.

    2019-09-02 20:12:38.579 Metadata update succeeded.

    2019-09-02 20:12:38.579 Executing startup script...

    2019-09-02 20:12:38.611 Started in: C:/Program Files/DAZ 3D/DAZStudio4 Public Build

    2019-09-02 20:12:38.611 DAZ Studio Started

    2019-09-02 20:12:38.611 Creating Pixel Buffer

    2019-09-02 20:12:38.653 Pixel buffer - Width: 1024 Height: 1024

    2019-09-02 20:12:38.658 Compiling OpenGL Shader...

    2019-09-02 20:12:38.660 Fragment Shader:

    Fragment Shader compiled successfully.

    Linking Shader:

    Shader Program successfully linked.

     

    2019-09-02 20:13:15.377 WARNING: QFont::setPixelSize: Pixel size <= 0 (0)

    2019-09-02 20:13:21.298 *** Scene Cleared ***

    2019-09-02 20:13:31.275 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): recv failed errno=10054

    2019-09-02 20:13:32.632 JSON interpreter warning: Unexpected member object: pSadation

    2019-09-02 20:13:55.902 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(7848): Failed to add user alias property to node.

    2019-09-02 20:13:55.907 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(1451): Failed to create alias!

    2019-09-02 20:13:55.907 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(7848): Failed to add user alias property to node.

    2019-09-02 20:13:55.908 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(1451): Failed to create alias!

    2019-09-02 20:13:55.908 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(7848): Failed to add user alias property to node.

    2019-09-02 20:13:55.908 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(1451): Failed to create alias!

    2019-09-02 20:13:56.307 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5759): Could not find output property for formula: Genesis8Female:/data/DAZ%203D/Genesis%208/Female/Morphs/DAZ%203D/Head/Old/PHMEyesIrisSize.dsf#PHMEyesIrisSize?value in file : /data/DAZ%203D/Genesis%208/Female/Morphs/vyktohria/Meredith/VYK%20Meredith%20Head.dsf

  • Looks like there may be an issue with VYK Meredith, try uninstalling and reinstalling that.

  •  WARNING: 3DConnexion Plug-in Error: Could not create Device, CoCreateInstance failed ???

    2019-09-02 20:12:34.054 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): peer performed orderly shutdown errno=0

  • When I start up DAZ3D I get these errors:

    How do I fix them ??

    2019-09-02 22:48:50.923 Iray [INFO] - API:DATABASE ::   0.0   API    db   info : Loaded "C:\Program Files\DAZ 3D\DAZStudio4 Public Build\libs\iray\libneuray.dll"
    2019-09-02 22:48:50.928 Iray [INFO] - API:MISC ::   0.0   API    misc info : Iray RTX 2019.1.3, build 317500.3714, 19 Jul 2019, nt-x86-64
    2019-09-02 22:48:50.928 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(419): Could not add path: "C:/Users/fableman/AppData/Roaming/DAZ 3D/Studio4 Public Build/shaders/iray". Due to unknown error -2
    2019-09-02 22:48:50.928 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(419): Could not add path: "C:/Users/fableman/AppData/Roaming/DAZ 3D/Studio4 Public Build/temp/shaders/iray". Due to unknown error -2

  • When I load the basic genesin 8 female I get these errors:

    2019-09-02 23:47:21.362 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): peer performed orderly shutdown errno=0
    2019-09-02 23:47:26.885 *** Scene Cleared ***
    2019-09-02 23:47:37.575 JSON interpreter warning: Unexpected member object: pSadation
    2019-09-02 23:47:56.325 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(7848): Failed to add user alias property to node.
    2019-09-02 23:47:56.325 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(1451): Failed to create alias!
    2019-09-02 23:47:56.330 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(7848): Failed to add user alias property to node.
    2019-09-02 23:47:56.330 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(1451): Failed to create alias!
    2019-09-02 23:47:56.330 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(7848): Failed to add user alias property to node.
    2019-09-02 23:47:56.330 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(1451): Failed to create alias!
    2019-09-02 23:48:35.586 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): peer performed orderly shutdown errno=0
    2019-09-02 23:48:37.895 Begin Loading Character Addons...
    2019-09-02 23:48:38.184 File loaded in 0 min 0.2 sec.
    2019-09-02 23:48:38.202 Loaded file: genesis 8 female eyelashes.duf
    2019-09-02 23:48:38.209 Loaded Morph Deltas in 0 min 0.0 sec.
    2019-09-02 23:48:38.211 Loaded file: PHMEyelashesLengthUpper.dsf
    2019-09-02 23:48:38.211 Loaded Morph Deltas in 0 min 0.0 sec.
    2019-09-02 23:48:38.214 Loaded file: PHMEyelashesLengthLower.dsf
    2019-09-02 23:48:38.214 Loaded Morph Deltas in 0 min 0.0 sec.
    2019-09-02 23:48:38.216 Loaded file: PHMEyelashesCurl.dsf
    2019-09-02 23:48:38.265 Loaded Morph Deltas in 0 min 0.0 sec.
    2019-09-02 23:48:38.266 Loaded file: PHMEyelashesLengthUpper.dsf
    2019-09-02 23:48:38.267 Loaded Morph Deltas in 0 min 0.0 sec.
    2019-09-02 23:48:38.267 Loaded file: PHMEyelashesLengthLower.dsf
    2019-09-02 23:48:38.269 Loaded Morph Deltas in 0 min 0.0 sec.
    2019-09-02 23:48:38.269 Loaded file: PHMEyelashesCurl.dsf
    2019-09-02 23:48:38.271 Loaded Morph Deltas in 0 min 0.0 sec.
    2019-09-02 23:48:38.272 Loaded file: PHMEyelashesExpand.dsf
    2019-09-02 23:48:38.436 File loaded in 0 min 0.0 sec.
    2019-09-02 23:48:38.441 Loaded file: base mat eyelashes.duf
    2019-09-02 23:48:38.443 Finished Loading Character Addons
    2019-09-02 23:48:38.545 File loaded in 1 min 11.6 sec.
    2019-09-02 23:48:38.550 Loaded file: genesis 8 basic female.duf
    2019-09-02 23:48:41.506 Loaded image g8fbaselegsmapd_1003.jpg
    2019-09-02 23:48:41.559 Loaded image g8fbaseeyes01_1007.jpg
    2019-09-02 23:48:41.722 Loaded image g8fbasearmsmapd_1004.jpg
    2019-09-02 23:48:41.775 Loaded image g8fbasemouthmapd_1005.jpg
    2019-09-02 23:48:41.941 Loaded image g8fbasefacemapd_1001.jpg
    2019-09-02 23:48:42.127 Loaded image g8fbasetorsomapd_1002.jpg
    2019-09-02 23:48:42.180 Loaded image g8fbaseeyelashes_1006.jpg

  • fableman said:

     WARNING: 3DConnexion Plug-in Error: Could not create Device, CoCreateInstance failed ???

    2019-09-02 20:12:34.054 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): peer performed orderly shutdown errno=0

    Do you have a 3DConnexion device? If not, ignore it.

  • @Richard Haseltine:

    OptiX SDK 6.5 and 7.0 have been released recently and changes look like they will be very beneficial for DAZ Studio, and not only for RTX owners. Any news on integration of that?

    Release Highlights NVIDIA® OptiX™ 6.5.0 (Aug 2019)

    • OptiX AI denoiser no longer requires redistribution of cuDNN
    • New disk caching features offer flexibility for production environments
    • Improved PTX handling (extended instruction set)
    • Improved build times (3x to 4x faster on average)
    • Hit shaders can access triangle vertex data, motion blur data, and the transformation stack
    • Introduction of demand loaded buffers and textures
      • Decreases memory requirements of large texture sets by only loading required textures
      • Time to first pixel is greatly reduced
      • Two new samples included to demonstrate best practices
    • Nsight Compute 2019.4 & NsightVSE 2019.3 Debugger OptiX application profiling support
      • OptiX driver modules are identified
      • All public OptiX modules and Application/User kernels called by OptiX are visible
      • NsightVSE can set breakpoints, inspect GPU state, and debug with expected run control through application code

     

    Release Highlights NVIDIA® OptiX™ 7.0.0 (Aug 2019)

    • No host state is maintained. Scene graphs, materials, etc., are managed by the application rather than by OptiX
    • GPU memory is managed by the application using CUDA. (No OptiX buffers or variables)
    • GPU launches are explicit and asynchronous using CUDA streams
    • Shader compilation is explicit (Similar to DXR or Vulkan)
    • All host functions are thread-safe
    • Source code for demand loading library is included and designed for direct inclusion in production applications
    • Multi-GPU operation is managed by the application
    • OptiX AI denoiser no longer requires redistribution of cuDNN (included in the driver)
    • New disk caching features offer flexibility for production environments
    • Improved PTX handling (extended instruction set)
    • Improved build times (3x to 4x faster on average)
    • Hit shaders can access triangle vertex data, motion blur data, and the transformation stack
    • Nsight Compute 2019.4 & NsightVSE 2019.3 Debugger OptiX application profiling support [Coming Soon]
      • OptiX RTCore modules are identified
      • All public OptiX module and Application/User kernels called by OptiX are visible
      • NsightVSE can set breakpoints, inspect GPU state, and debug with expected run control through application code

     

    You'd need to keep an eye on the change log http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log#private_channel

  • I am, I guess those OptiX changes (if they every arrive) will come through the Iray SDK update though?

    Yes, I am pretty sure of that.

  • robotmonsterousrobotmonsterous Posts: 3
    edited September 2019

    Goz and Daz studio have been broken on mac for quite some time now, sometime in the v 4.10 to 4.11 transition it got broke! Works as it should on pc but not on mac. Initially the object is sent to zbrush fine, and you could work with it, but when then sending back to Daz studio with GoZ it would give an error message. After installing latest version of the beta it still gets to zbrush fine, but going back to daz it goes through the motions but never ends up back in daz but now  there is no error message, but it doesn't go to daz studio either. Any word on when this might be fixed or if it's even on the docket? Anyone else experience this, or is everyone on a pc for daz  these days?

     

     

    Post edited by robotmonsterous on
  • IvyIvy Posts: 6,828

    I am not sure if this is something someone can help with or not. But something thing ive been experimenting with in a MS-VB  sand box is a dopesheet script for the daz keyframe editor to accept MS excel data spread sheets by script to import excel data to the keyframes to the timeline keyframe editor,  Ive been using the daz 4.5 SDK and MS VB2018, are these still acceptable for script plugin development? I don't appear to be having much luck. is there something else i should be using instead?

    I was hoping to achieve what I can do with Maya LT by importing a spread sheet data into the keyframe editor, and have the keyframe editor follow the data in the spread sheet for repetitive motion cycles . I am working on a Piano player fingering to match on the keyframe editor using the keyframes data note by note in the MS excel spread sheet. this way when the piano players fingure press down on the key of the piano it will be following the spread sheet data,   but when I try to import into daz the keyframe data using MS VB 2018  the timeline crashes or better description would be it just goes blank while daz 12.67 is still remain running. though animate2 appears to still working as well.   It was not what i was expecting for a results, usually when I make bad VB script changes the whole ds studio crash  or goes white. so this was new.  I'm just wondering does the daz studio timeline editor work with daz SDK4.5 & MS VB,  I am trying to use a MS data spread sheet for repetitive motion cycles?  am I missing a step somewhere, or is it even possible to import spreadsheet data into the daz timeline editor? Maybe I am just wasting my time and its not achievable?  So any advice or help please would be welcomed. I believe it would be very useful to use excel data for keyframing long repetitive motion. But is it even possible with daz because I seem to be missing something to get it to work that is why i am asking if the daz 4.5 sdk and vb where still acceptable ways for script editing or is there a new SDK I should be using? I never had issues with the daz 4.5 SDK kit before using MS VB thats why i ask.

    Thank you for reading my comment

  • Leonides02Leonides02 Posts: 1,300

    Another weird bug I've sent to support...

     

    Adding Zev's Fit Control morphs to an object in 4.12 makes the software EXTREMELY slow.

    This does not occur in 4.11.

  • barbultbarbult Posts: 17,317
    edited September 2019

    Another weird bug I've sent to support...

     

    Adding Zev's Fit Control morphs to an object in 4.12 makes the software EXTREMELY slow.

    This does not occur in 4.11.

    I'm not having that problem with Genesis 8. I didn't try Genesis 3. Zev0 mentioned in his thread that there is a known problem when some hair products are in the scene, but he didn't specify what hairs cause the problem.

    Post edited by barbult on
  • In my experience it's fiber mesh hair.

  • Leonides02Leonides02 Posts: 1,300

    In my experience it's fiber mesh hair.

    Ah. I do have a Fibermesh hair in the scene.

    However, it works fine in 4.11.

     

  • L'AdairL'Adair Posts: 9,470

    I just read this in the Change Log, build 4.12.0.73:

    • Fixed an issue trial usage activation policy; now dependent on release cycle/channel

    Does this mean Daz is going to stop providing Daz Studio free of charge? (If the program is not paid, why would it need a "trial usage activation policy"?)

  • L'Adair said:

    I just read this in the Change Log, build 4.12.0.73:

    • Fixed an issue trial usage activation policy; now dependent on release cycle/channel

    Does this mean Daz is going to stop providing Daz Studio free of charge? (If the program is not paid, why would it need a "trial usage activation policy"?)

    At a guess it means the system used by AniMate 2/AniMate Lite - meaning you can have two trials, one in each channel.

  • IvyIvy Posts: 6,828
    edited September 2019

    Karate Girl in the 5th chamber of the Shaolin

    Something fun to watch as Suki the Karate Girl tries to defeat the 3rd master of the 5th chamber in this 3 minute animated short of Kung Fu mastery.   Created with Daz Studio 4.12 pro, rendered in NVIDIA iRAY

    Click picture to watch animation. have fun :)

    Post edited by Ivy on
  • Leonides02Leonides02 Posts: 1,300

    LOL - Great stuff, Ivy. How much was hand-animated and how much was MOCAP?

  • nonesuch00nonesuch00 Posts: 15,625
    L'Adair said:

    I just read this in the Change Log, build 4.12.0.73:

    • Fixed an issue trial usage activation policy; now dependent on release cycle/channel

    Does this mean Daz is going to stop providing Daz Studio free of charge? (If the program is not paid, why would it need a "trial usage activation policy"?)

    At a guess it means the system used by AniMate 2/AniMate Lite - meaning you can have two trials, one in each channel.

    I reported a bug regarding aniMate2 / aniMate Lite & have aniMate2 paid & licensed but maybe that was the cause of the bug. It would be nice to see it fixed.

  • nonesuch00nonesuch00 Posts: 15,625

    Could the designers & programmers investigate whether the Spectral Rendering feature is working correctly in 4.12+ and 4.11+? When it's on the lighting in my scenes is considerably dimmed but when it's off lighting functions at the brightness I expect (and most people expect from experience). Contrast and the white points seem to then work correctly too.

    I think the having spectral rendering turned on should not make for such radically different renders but it is. It seems when I first starting rendering in DAZ 4.9 spectral rendering didn't create such an obvious difference in renders of on vs off for spectral rendering.

  • IvyIvy Posts: 6,828

    LOL - Great stuff, Ivy. How much was hand-animated and how much was MOCAP?

    all the walk cycles were SK MOTIONS aniblocks, about 20% of the fight scene, i used bone-tec action melee aniblocks the other 80% was hand keyframed & assorted pose to pose sequencing

    Thank you for watching smiley

  • TaozTaoz Posts: 8,980
    edited September 2019

    I'm having a problem with the Library - can't fully see the last subfolders:



     

    ds_library_scroll.png
    415 x 478 - 23K
    Post edited by Taoz on
  • how much faster is 2080ti to 980ti on this build, I wonder?

  • How long did the rendering take

     

Sign In or Register to comment.