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

145791030

Comments

  • Daz3d 4.21.1.29 figure and geograft FBX file crashed on 3dcoat. 
    Blender with "better FBX importer" load the figure without the mesh.

  • Saxa -- SDSaxa -- SD Posts: 871
    edited January 2023

    Hand Pose - likley alias - how to clear keyframe - delete keyframe not possible cos alias

    in further reply to question on previous page

    see images below

    1 show clear animation.JPG
    1286 x 928 - 149K
    2 show alias.JPG
    1394 x 995 - 176K
    Post edited by Saxa -- SD on
  • marblemarble Posts: 7,453
    edited January 2023

    Saxa -- SD said:

    Hand Pose - likley alias - how to clear keyframe - delete keyframe not possible cos alias

    in further reply to question on previous page

    see images below

    Actually, I wasn't using a pose from my library, I was posing using the hand pose controls. Here's what I mean (see screenshot):

    Hand Pose.jpg
    1152 x 1022 - 166K
    Post edited by marble on
  • marblemarble Posts: 7,453

    I don't know why but when I just tried with the scene in the screenshot (just a G8F development figure) I used the pose controls to grasp the hand and hit the Add Keyframe button on the timeleine. This time I could delete the selected keys. So I have no idea as to what conditions are needed for this to work or not.

    Another question I have is how to clear the movement or posing in frames between keyframes? There are some things which don't create a keyframe when posed or moved. This was the case for the hand grasp just described - I had to manually add the keyframe using the +key button.

  • marblemarble Posts: 7,453
    edited January 2023

    Another observation (see attached screenshots).

    Again using the pose controls to grasp the hand at frame 5 on the timeline, I checked with the old GraphMate add-on that I have. Here there is clearly a keyframe marker at frame 5 which can be moved using GraphMate.

    I checked using the DAZ timeline Graph Editor and I see nothing at all.

    GraphMate.jpg
    521 x 822 - 53K
    Timeline Graph.jpg
    865 x 847 - 87K
    Post edited by marble on
  • marble said:

    johndoe_36eb90b0 said:

    You should not render icons to 800x800 -- for asset.duf you should render asset.png at the icon size (91x91), and asset.tip.png at the size you want (say 800x800). That way icon doesn't have to be resized to be displayed in the user interface, and when you mouse over the icon you get shown larger image as a tooltip.

     

    I don't understand the point of the 91x91 image. Why not just render out the larger image instead of creating an extra .tip.png? I always save my icons at larger resolutions precisely because I want something my old eyes can see when I hover over them with the mouse.

    When you hover over the asset.duf that's when 800x800px asset.tip.png is loaded and shown in its original size. Until you hover, only the 91x91px asset.png is shown.

    Basically by using 800x800px image as an icon you are wasting CPU and RAM resources because Daz Studio has first to resize each 800x800px to 91x91px in order to show the icons.

    If you are OK with that, just ignore what I said -- I was just trying to explain why there is a separate .tip.png image and why it should be used especially if you are selling assets.

  • marblemarble Posts: 7,453

    [MODERATOR REQUEST]

    Mods, please could you consider moving the above timeline-related posts to a new thread I have just started so as not to derail this Beta thread. I feel this is a subject that needs a separate focus. Thanks.

  • marble said:

    [MODERATOR REQUEST]

    Mods, please could you consider moving the above timeline-related posts to a new thread I have just started so as not to derail this Beta thread. I feel this is a subject that needs a separate focus. Thanks.

    It may have a quick reply - which properties are set to show in the Timeline pane?

  • marblemarble Posts: 7,453
    edited January 2023

    Richard Haseltine said:

    marble said:

    [MODERATOR REQUEST]

    Mods, please could you consider moving the above timeline-related posts to a new thread I have just started so as not to derail this Beta thread. I feel this is a subject that needs a separate focus. Thanks.

    It may have a quick reply - which properties are set to show in the Timeline pane?

    I am not sure what propertieds you mean but I think that might be TRSHA (without the O). By the way, there are already several posts in the new thread. It might be worth adding that other thread asking about deleting keyframes to that too?

    Post edited by marble on
  • With the latest Daz studio and latest nv studio drivers, I can't render OOT hairs.

    If I switch to Iray Preview, it never finishes switching to Iray. I had to restart the studio in order to stabilize it and the following is logged (always) :

     

    2023-01-23 14:56:56.791 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.4   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): Kernel [4] (ShadowEvalFS      ) failed after 0.022s
    2023-01-23 14:56:56.792 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.4   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while launching CUDA renderer in <internal>:908)
    2023-01-23 14:56:56.792 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.4   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): Failed to launch renderer
    2023-01-23 14:56:56.792 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): Device failed while rendering
    2023-01-23 14:56:56.792 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [WARNING] - IRAY:RENDER ::   1.5   IRAY   rend warn : CUDA device 0 (NVIDIA GeForce RTX 3090) is no longer available for rendering.
    2023-01-23 14:56:56.793 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): [Guidance sync] Failed master device (remaining 1, done 0).
    2023-01-23 14:56:56.793 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)

    2023-01-23 14:56:57.568 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [WARNING] - IRAY:RENDER ::   1.2   IRAY   rend warn : All available GPUs failed.
    2023-01-23 14:56:57.568 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: Fallback to CPU not allowed.

    2023-01-23 14:56:57.569 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [WARNING] - IRAY:RENDER ::   1.2   IRAY   rend warn : Re-rendering iteration because of device failure

    2023-01-23 14:56:57.572 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: All workers failed: aborting render

    2023-01-23 14:56:57.572 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
    2023-01-23 14:56:57.573 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
    2023-01-23 14:56:57.573 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
    2023-01-23 14:56:57.573 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
    2023-01-23 14:56:57.573 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
    2023-01-23 14:56:57.574 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
    2023-01-23 14:56:57.574 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
    2023-01-23 14:56:57.575 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
    2023-01-23 14:56:57.575 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)

    2023-01-23 14:57:26.815 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - OPTX:RENDER ::   1.14  OPTX   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
    2023-01-23 14:57:26.815 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - OPTX:RENDER ::   1.14  OPTX   rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
    2023-01-23 14:57:26.829 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.14  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error
    2023-01-23 14:57:26.830 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - OPTX:RENDER ::   1.14  OPTX   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
    2023-01-23 14:57:26.830 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - OPTX:RENDER ::   1.14  OPTX   rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)

    ... (last optx render is repeated lots of times)

    2023-01-23 14:57:26.921 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Device statistics:
    2023-01-23 14:57:26.921 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : CUDA device 0 (NVIDIA GeForce RTX 3090): 0 iterations, 4.885s init, 0.919s render

    2023-01-23 14:57:26.921 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)

    (last repeated lots of times)

    Then log finishes.

  • Dolce Saito said:

    With the latest Daz studio and latest nv studio drivers, I can't render OOT hairs.

    If I switch to Iray Preview, it never finishes switching to Iray. I had to restart the studio in order to stabilize it and the following is logged (always) :

     

    2023-01-23 14:56:56.791 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.4   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): Kernel [4] (ShadowEvalFS      ) failed after 0.022s
    2023-01-23 14:56:56.792 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.4   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while launching CUDA renderer in <internal>:908)
    2023-01-23 14:56:56.792 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.4   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): Failed to launch renderer
    2023-01-23 14:56:56.792 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): Device failed while rendering
    2023-01-23 14:56:56.792 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [WARNING] - IRAY:RENDER ::   1.5   IRAY   rend warn : CUDA device 0 (NVIDIA GeForce RTX 3090) is no longer available for rendering.
    2023-01-23 14:56:56.793 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): [Guidance sync] Failed master device (remaining 1, done 0).
    2023-01-23 14:56:56.793 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)

    2023-01-23 14:56:57.568 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [WARNING] - IRAY:RENDER ::   1.2   IRAY   rend warn : All available GPUs failed.
    2023-01-23 14:56:57.568 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: Fallback to CPU not allowed.

    2023-01-23 14:56:57.569 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [WARNING] - IRAY:RENDER ::   1.2   IRAY   rend warn : Re-rendering iteration because of device failure

    2023-01-23 14:56:57.572 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: All workers failed: aborting render

    2023-01-23 14:56:57.572 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
    2023-01-23 14:56:57.573 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
    2023-01-23 14:56:57.573 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
    2023-01-23 14:56:57.573 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
    2023-01-23 14:56:57.573 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
    2023-01-23 14:56:57.574 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
    2023-01-23 14:56:57.574 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
    2023-01-23 14:56:57.575 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)
    2023-01-23 14:56:57.575 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.5   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)

    2023-01-23 14:57:26.815 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - OPTX:RENDER ::   1.14  OPTX   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
    2023-01-23 14:57:26.815 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - OPTX:RENDER ::   1.14  OPTX   rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
    2023-01-23 14:57:26.829 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.14  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error
    2023-01-23 14:57:26.830 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - OPTX:RENDER ::   1.14  OPTX   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
    2023-01-23 14:57:26.830 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - OPTX:RENDER ::   1.14  OPTX   rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)

    ... (last optx render is repeated lots of times)

    2023-01-23 14:57:26.921 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Device statistics:
    2023-01-23 14:57:26.921 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : CUDA device 0 (NVIDIA GeForce RTX 3090): 0 iterations, 4.885s init, 0.919s render

    2023-01-23 14:57:26.921 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 3090): an illegal memory access was encountered (while de-allocating memory)

    (last repeated lots of times)

    Then log finishes.

    There is an issue with some OOT hairs. Select the hair, switch to the surfaces tab, make sure all the surfaces are selected. Scroll down to the Transmitted Color channel, and remove the map(s) for that channel.

    It doesn't seem to affect the hairs for Genesis 9, or the ones named in the year format.

  • DoctorJellybean said:

    ...

    There is an issue with some OOT hairs. Select the hair, switch to the surfaces tab, make sure all the surfaces are selected. Scroll down to the Transmitted Color channel, and remove the map(s) for that channel.

    It doesn't seem to affect the hairs for Genesis 9, or the ones named in the year format.

    Thank you very much!

  • cleric_e28bdb695f said:

    Daz3d 4.21.1.29 figure and geograft FBX file crashed on 3dcoat. 
    Blender with "better FBX importer" load the figure without the mesh.

     same here. crashes CC4 and loads with no mesh in blender, even if i used the offical DAZ2Blender exporter.

    the FBX exporter is completely broken in this latest beta build

  • Looks like deforce is still broken. Tried adding the deforce modifier on a surface and it did not work.

  • Hitesh_Sethi said:

    Looks like deforce is still broken. Tried adding the deforce modifier on a surface and it did not work.

    nVidia driver version? dForce is working with adequate drivers, including the nearly latest crop.

  • Blood-PawWerewolf said:

    cleric_e28bdb695f said:

    Daz3d 4.21.1.29 figure and geograft FBX file crashed on 3dcoat. 
    Blender with "better FBX importer" load the figure without the mesh.

     same here. crashes CC4 and loads with no mesh in blender, even if i used the offical DAZ2Blender exporter.

    the FBX exporter is completely broken in this latest beta build

    Can the file be imported back into DS? If it won't make a round trip that may well be a bug, and should be reported (ideally using the simplest possible steps to reproduce). The FBX exporter writes files that Maya can open, so if another application can't it merely shows theer is an incompatibility but doesn't prove that there is a fault in DS - unfortuantely FBX seems to be a problematic format all round, and trying to figure out incompatibilities can be a pain.

  • crosswindcrosswind Posts: 5,254
    edited January 2023

    DoctorJellybean said:

    ...

    There is an issue with some OOT hairs. Select the hair, switch to the surfaces tab, make sure all the surfaces are selected. Scroll down to the Transmitted Color channel, and remove the map(s) for that channel.

    It doesn't seem to affect the hairs for Genesis 9, or the ones named in the year format.

    Does not work for me... For instance, I installed the update of Classic Bob Hair that OOT just released for latest iray version. There's no problem in 4.21.0.5 but still cannot preview or render in 4.21.1.29. I could only convert OOT Hairblending shader to Iray Uber, it finally worked but I had to tweak a lot of parameters... However for Mega Updo 2, with the same Hairblending shader, it works fine in both DAZ versions...  It's really weird~ 

     

    Post edited by crosswind on
  • barbultbarbult Posts: 23,431

    crosswind said:

    DoctorJellybean said:

    ...

    There is an issue with some OOT hairs. Select the hair, switch to the surfaces tab, make sure all the surfaces are selected. Scroll down to the Transmitted Color channel, and remove the map(s) for that channel.

    It doesn't seem to affect the hairs for Genesis 9, or the ones named in the year format.

    Does not work for me... For instance, I installed the update of Classic Bob Hair that OOT just released for latest iray version. There's no problem in 4.21.0.5 but still cannot preview or render in 4.21.1.29. I could only convert OOT Hairblending shader to Iray Uber, it finally worked but I had to tweak a lot of parameters... However for Mega Updo 2, with the same Hairblending shader, it works fine in both DAZ versions...  It's really weird~

    Classic Bob Hair was updated January 24, 2023, and the readme says the shader was fixed to work with the latest Iray, but it is NOT fixed. There is still an image loaded in the Transmitted Color channel.

     

    Screenshot 2023-01-26 142436.jpg
    637 x 337 - 51K
  • barbultbarbult Posts: 23,431
    edited January 2023

    I just tried a few other OOT hairs that were updated. Martha's Everyday Bob, Rose Hair, and Charlene Hair also still crash DS 4.21.1.29. Their readme files claim the shader was updated to work with updated Iray. But they still load an image in the Transmitted Color channel and crash DS, so they are not really fixed. I have other OOT hairs that were updated, but I am tired testing, since the results have been so poor. However, 3-in-1 Ponytail Hair looks like it was really fixed (or maybe never broken, I don't know).

    I guess I'll submit a ticket, but since the tech support ticket I submitted on December 29 hasn't even had a human response, I am not hopeful.

    Edit: Ticket submitted:
    Request #429861 Recent updates to OOT hair have not fixed the Daz Studio crash problem

    Screenshot 2023-01-26 143724.jpg
    636 x 326 - 50K
    Screenshot 2023-01-26 143808.jpg
    637 x 328 - 50K
    Screenshot 2023-01-26 145343.jpg
    632 x 379 - 52K
    Post edited by barbult on
  • barbult said:

    I just tried a few other OOT hairs that were updated. Martha's Everyday Bob, Rose Hair, and Charlene Hair also still crash DS 4.21.1.29. Their readme files claim the shader was updated to work with updated Iray. But they still load an image in the Transmitted Color channel and crash DS, so they are not really fixed. I have other OOT hairs that were updated, but I am tired testing, since the results have been so poor. However, 3-in-1 Ponytail Hair looks like it was really fixed (or maybe never broken, I don't know).

    I guess I'll submit a ticket, but since the tech support ticket I submitted on December 29 hasn't even had a human response, I am not hopeful.

    Edit: Ticket submitted:
    Request #429861 Recent updates to OOT hair have not fixed the Daz Studio crash problem

    Interesting.

    I've just updated various OOT hairs, e.g. Marthas Everyday Bob, Classic Bob, no maps in the Transmitted Color channel and they all rendered.

     

    OOT Martha.png
    471 x 360 - 27K
  • barbultbarbult Posts: 23,431

    DoctorJellybean said:

    barbult said:

    I just tried a few other OOT hairs that were updated. Martha's Everyday Bob, Rose Hair, and Charlene Hair also still crash DS 4.21.1.29. Their readme files claim the shader was updated to work with updated Iray. But they still load an image in the Transmitted Color channel and crash DS, so they are not really fixed. I have other OOT hairs that were updated, but I am tired testing, since the results have been so poor. However, 3-in-1 Ponytail Hair looks like it was really fixed (or maybe never broken, I don't know).

    I guess I'll submit a ticket, but since the tech support ticket I submitted on December 29 hasn't even had a human response, I am not hopeful.

    Edit: Ticket submitted:
    Request #429861 Recent updates to OOT hair have not fixed the Daz Studio crash problem

    Interesting.

    I've just updated various OOT hairs, e.g. Marthas Everyday Bob, Classic Bob, no maps in the Transmitted Color channel and they all rendered.

     

    Your attached image shows the Cap. The Cap never had a transmitted color image. What about all the other surfaces?

  • barbult said:

    Your attached image shows the Cap. The Cap never had a transmitted color image. What about all the other surfaces?

    Oops.

    The other surfaces don't have a Transmitted Color channel.

    OOT Martha 2.png
    471 x 369 - 26K
  • barbultbarbult Posts: 23,431

    DoctorJellybean said:

    barbult said:

    Your attached image shows the Cap. The Cap never had a transmitted color image. What about all the other surfaces?

    Oops.

    The other surfaces don't have a Transmitted Color channel.

    They do for me, as shown above. This is what happens when I try to render.

    Screenshot 2023-01-26 163124.jpg
    1279 x 810 - 218K
  • How are you installing? I just tried a couple installed through Connect and have yet to see a transmitted colour mapped.

  • OK, I do haev Rose hair and I do see maps on its Transmiited Colour, both versions of the hair. Tried a couple of materials presets without changing that.

  • barbultbarbult Posts: 23,431

    Richard Haseltine said:

    How are you installing? I just tried a couple installed through Connect and have yet to see a transmitted colour mapped.

    I use DIM.

  • cain-xcain-x Posts: 167

    Is the play/pause timeline shortcut (default to spacebar) fixed in BETA?

  • barbultbarbult Posts: 23,431

    NorthOf45 gave me the clue I needed to solve my OOT hair problem. Daz Connect was the source of my problem. Although I don't use it anymore, there is still some old junk there. There was one old OOT hair product still installed there (not one of the ones I tested today). Once I uninstalled and deleted that product and reinstalled it with DIM, everything was fine. Oh, I also cleared the DSON cache for good measure.

  • crosswindcrosswind Posts: 5,254
    edited January 2023

    barbult said:

    NorthOf45 gave me the clue I needed to solve my OOT hair problem. Daz Connect was the source of my problem. Although I don't use it anymore, there is still some old junk there. There was one old OOT hair product still installed there (not one of the ones I tested today). Once I uninstalled and deleted that product and reinstalled it with DIM, everything was fine. Oh, I also cleared the DSON cache for good measure.

    That's it!  I disabled DAZ Connect years ago, and clearing cache did not work. The reason on my side is that I have 2 DAZ libraries, those 2 hairblending .dsf files in 'data\outoftouch\OOT Hairblending 2' have not been updated in the old library, I replaced them with the latest versions, all problems have gone. Thanks for the instruction!

    Post edited by crosswind on
  • Richard HaseltineRichard Haseltine Posts: 97,943
    edited January 2023

    If you use Connect, have legacy Connect files with a DIM workflow, or have multiple content directories so that you get an unupdated copy of the hair blending file, find a good copy of the file* and copy it, then execute this script in DS and it should open a file browser to the copy that DS will actually use - paste the updated version over it and the issue should be resolved 9obviously my testing was just on my own system).

    // Find the active copy of the Hair Blending file

     

     

    // get the content manager

    var oCntMgr = App.getContentMgr();

     

    // get the locations for the file in question

    var aLocations = oCntMgr.getAbsolutePaths( "/data/outoftouch/OOT Hairblending 2/OOT Hairblending 2 Hair/OOT Hairblending Hair.dsf" , false );

     

    // assuming we have a hit

    if (aLocations.length > 0 ) {

    // Get a file info object for the first entry

    var oPrefFile = new DzFileInfo ( aLocations[ 0 ] );

     

    // now tell the OS to open a folder to show that location,

    // so we ignore the filename and just take the path from the file info

    App.showURL( "file:/" + oPrefFile.path() );

    }

    * You can get the updated files from the /data/outoftouch/OOT Hairblending 2/OOT Hairblending 2 Hair/ in your main directory if you mainly use DIM, from an updated zip, or you can right-click on one of the updated OOT hair products in Smart Content>Browse to Product Folder and then find the file in there if using Connect.

    Post edited by Richard Haseltine on
Sign In or Register to comment.