Loading...
> >

A bunch of OOT (outoftouch) hair crashes Daz Studio in latest version

frits.vancampenfrits.vancampen Posts: 18
edited January 10 in Technical Help (nuts n bolts)

The application crashes when I try to load https://www.daz3d.com/dallas-pigtails-hair-for-genesis-3-and-8-females, https://www.daz3d.com/madeline-tails-hair-for-genesis-3-and-8-female-s, or https://www.daz3d.com/marigold-hair-for-genesis-3-and-genesis-8-female-s

Some other OOT hair does seem to be working, such as https://www.daz3d.com/2021-01-hair-for-genesis-8-females

I recently upgraded to Daz Studio 4.22.15. Previously I was on 4.21.05 and things where working fine then.

I'm posting this here because I can't report a bug anywhere. All links I can find are dead or point to pages that don't do what they should. The built-in report function also seems to be disabled.

zip
zip
DAZStudio_error_report_240110-214901.zip
153K
Post edited by frits.vancampen on

Comments

  • SofaCitizenSofaCitizen Posts: 1,894
    edited January 10

    The link at the footer of the page works: https://bugs.daz3d.com/hc/en-us

    Have you updated all those three hairs to the version released on 2023-01-24?

    EDIT: Just to double-check (since I usually just use the Beta now) I just loaded and part-rendered all three hairs on 4.22.0.15.

     

    OOT Hairs.png
    800 x 640 - 843K
    Post edited by SofaCitizen on
  • Richard HaseltineRichard Haseltine Posts: 100,969

    This has been discussed in the beta and release threads

    https://www.daz3d.com/forums/discussion/656716/daz-studio-4-22-0-x-pro-general-release#latest
    https://www.daz3d.com/forums/discussion/665996/daz-studio-pro-beta-version-4-22-1-54-updated#latest

    Mostaffected products have been updated, but since the issue is a shared file the installation order and method matter (as does having an older version of the file in another content directory). You can fix it yourself - select the hair in the Scene, select the hair in the editor tab of the Surfaces pane, type transm in the filter box at the top of the pane, and remove any map from the Transmitted Colour property by clicking the button to the left of the colour picker.

  • frits.vancampenfrits.vancampen Posts: 18

    Ok, I got it to work. Richard's workaround works but remember to set your Viewport to Texture Shaded. In IRAY mode it will crash right away.

    In general, what's Daz's process for dealing with breaking changes? Can we expect this bug to get fixed soon or at all?

    I'm not a fan of requiring an asset creator to 'fix' their assets for minor version release. Typically, breaking changes are saved for major versions. It makes things more predictable, but that's not a word I would use for anything related to Daz indecision

  • Richard HaseltineRichard Haseltine Posts: 100,969
    edited January 11

    nVidia would have to modify Iray not to crash, but having a map assigned to Transmitted Colour was incorrect so removing the maps is the basic solution.

    In order to keep plug-in/SDK compatibility Daz has integrated major feature updates in new minor versions, though we do know that an SDK-breaking DS 5 is coming.

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