dForce String Lights: Error loading prop?

dForce String Lights: Error loading prop?

Attempted to load some blue string lights into my existing environment and "an error occurred while loading".
This is in the LogFile... anybody knows what the issue seems to be? Thank you :)

2020-08-13 22:13:22.073 Invalid hierarchy for selected node(s) and "preset_hierarchical_material" type; no root(s) found.
2020-08-13 22:13:22.073 Error reading file, see log for more details.

Comments

  • barbultbarbult Posts: 24,240

    It looks like you are loading a materials preset instead of a prop.

  • DMaxDMax Posts: 637
    barbult said:

    It looks like you are loading a materials preset instead of a prop.

    Hmm.. I just tried again and have made very sure that I was loading the "prop" from Props>Furnishings>Decor (it even had the green "Prop" icon) as opposed to a file from the >Materials section. Meanwhile, I found another string light to use in my current environment... it always feels like Christmas came early when I find a forgotten purchase hahaha!

  • barbultbarbult Posts: 24,240

    I'll check it when my current render finishes. Maybe you found a bug. 

  • barbultbarbult Posts: 24,240

    The product is completely broken as far as I can see. The fact that the thumbnails have the word Prop on them and that they appear in the Props category is just bad metadata. The actual duf files identify them as "type" : "preset_hierarchical_material". 

  • DMaxDMax Posts: 637
    barbult said:

    The product is completely broken as far as I can see. The fact that the thumbnails have the word Prop on them and that they appear in the Props category is just bad metadata. The actual duf files identify them as "type" : "preset_hierarchical_material". 

    Urgh... probably a bad product... it was a freebie from a month ago perhaps that's why.

  • barbultbarbult Posts: 24,240

    Edit: Not completely broken. There are some props in there that are actually props. I would guess that if you ferret them out you could apply those mislabeled and miscategorized hierarchical materials presets to them. The freebies that we've been getting from PC+ have been having a lot of errors.

  • barbultbarbult Posts: 24,240
    edited August 2020

    DHL Light Line Straight is a real Prop. You can load it into your scene. Then you can select it and apply DHL Line Straight - Blue to turn the bulbs blue.

    There are also large and small loop props and corresponding hierarchical material presets for them. They are just mislabeled and miscategorized as "Prop". Similarly, there is a single bulb prop and a Tinsel prop and materials for them.

    I'll submit a help request, but none of my help requests are resulting in fixes these days. They all just go into the bug tracker black hole.  sad

    Hey, this one is NOT complicated! wink

    Post edited by barbult on
  • SevrinSevrin Posts: 6,306
    edited August 2020

    So yeah.  You have to load a vanilla prop - without colour, and then apply the colours, that are just pretending to also be props.  Once you get past that weirdness, they're pretty nice.

    String Lights.png
    800 x 1040 - 1M
    Post edited by Sevrin on
  • barbultbarbult Posts: 24,240

    Bug report submitted:

    Request #341692

    Almost all of the "Props" in dForce String Lights don't work

    dForce String Lights has 44 assets labeled as "Prop" and categorized as "Props". Most of those are actually hierarchical materials presets, not props. When you try to load one, like DHL Small Loop - Clear or DHL Large Loop - Blue, Daz Studio displays an error message. The log file says:

    2020-08-14 00:34:07.408 Invalid hierarchy for selected node(s) and "preset_hierarchical_material" type; no root(s) found.
    2020-08-14 00:34:07.409 Error reading file, see log for more details.

    The metadata for this product needs to be fixed.

  • NorthOf45NorthOf45 Posts: 5,482

    Yikes! Does it realy need 25 MB (Line Straight) or 35 MB (Loop Large) to change the colour of the lights? Every shader parameter for each light is included, but 99% of the parameters don't change from one preset to another. Only those that actually change need to be included if the prop's initial load has a basic shader preset. A very inefficient way to do it, coming in at 934 MB installed.

  • DMaxDMax Posts: 637

    @Barbult ... thanks for all the help! Strangely I didn't receive any notifications for this thread and luckily I chanced upon this within my bookmarks tonight!
    This one truly isn't complicated hahahahaha wink wink...

  • barbultbarbult Posts: 24,240

    The product has been updated. I saw it in DIM. I haven't checked to see if it is fixed.

  • DMaxDMax Posts: 637
    barbult said:

    The product has been updated. I saw it in DIM. I haven't checked to see if it is fixed.

    Thanks for the headsup, downloaded the update... haven't gone back into it though. Been busy all night trying to repair some horrifying character skins!

Sign In or Register to comment.