Announcements

Starting in December, we will archive content from the community that is 10 years and older. This FAQ provides more information.

[BUG] Rebel Pack resample_strands Broken

Anonymous

[BUG] Rebel Pack resample_strands Broken

Anonymous
Not applicable

Hi,

It seems that the resample_strands compound is broken in Rebel Pack 0.2.0. Other rebel compounds are working fine for me but this one spits out the following error:

Warning: while compiling top level compound 'bifrostGraph2', around the node 'Geometry::Strands::resample_strands::update_strands_length1':
Node 'update_strands_length1' does not have a node definition

The update_strands_length1 graph compound causes the issue. I'm currently using Windows but I don't remember facing this on Linux though or maybe I never used it so far.

 

Maya 2019.2.0 (CutID: 201907021615-48e59968a3)

Windows 10

Bifrost 2.0.2.0

 

Can someone please confirm if this is indeed an issue?

resample_strands_issue.png

 

Thanks,

Sachin

0 Likes
Reply
Accepted solutions (1)
972 Views
5 Replies
Replies (5)

yeungy
Autodesk
Autodesk

Hello Sachin,

 

A couple of us tried, but unfortunately, we were not able to reproduce.

 

Would you happen to have an older version of the rebel pack installed, causing a conflict between the files?

If you are loading the rebel compounds by pointing the BIFROST_LIB_CONFIG_FILES environment variable to the config file, would you please paste your log here? You should see messages in the Script Editor upon startup of Maya and the loading of Bifrost along the lines of:

// Bifrost: Loading library: Rebel-PO-Alliance, version: 0.2.0, from: Autodesk.
// Bifrost: Loading library: Amino, from: Autodesk.
// Bifrost: Loading library: AminoMayaTranslation, from: Autodesk.

 

Thanks!

Yvonne

0 Likes

Anonymous
Not applicable

Hi Yvonne,

 

Sorry for the delayed response. I just got back to this issue today and noticed the following in the script editor:

// Warning: Warning: Resolver (File Path Relative): Found duplicate file for: 'C:/Users\noizf\Autodesk\Bifrost\Compounds\rebel_pack\compounds\update_strands_length.json'.  Duplicate in: C:/Users\noizf\Autodesk\Bifrost\Compounds\MJCG_compounds\compounds\geometry\strands\update_strands_length.json // 
// Warning: Warning: Resolver (File Path Absolute): Found duplicate file for: 'C:/Users\noizf\Autodesk\Bifrost\Compounds\rebel_pack\compounds\update_strands_length.json'.  Duplicate in: C:/Users\noizf\Autodesk\Bifrost\Compounds\MJCG_compounds\compounds\geometry\strands\update_strands_length.json // 

So, both the rebel_pack and MJCG_compounds have the same update_strands_length compound and the resolver  seems to be reporting a clash at startup. I set the BIFROST_LIB_CONFIG_FILES right now and set the rebel_pack config file path first and now the problem goes away and the resample_strands loads correctly. But I still see the above errors at startup since MJCG compounds are still trying to load its own update_strands_length compound (which has now gotten removed from the MJCG user menu).

 

I think I didn't notice this problem on Linux before probably because the path was resolved for rebel_pack first so its compounds worked. But shouldn't Maya be namespacing these compounds as its loading them for each json config file so that both rebel_pack and MJCG's versions of the update_strands_length compound can co-exist?

 

Thanks,

Sachin

 

mjcg91
Collaborator
Collaborator

I noticed the same issue recently.

 

It seems like if you have compounds sharing the same name, in the same library, they will not conflict. Bifrost will just show they are at 2 different places in the tab menu (as they have different namespaces).

 

However, when Bifrost loads, if it finds compounds sharing the same name, in different libraries, it will choose one over the other.

I've always used my own namespace to avoid such issues, so I find it a bit frustrating that Bifrost is not able to load both of them with their respective namespaces. 

In any case I recommend deleting the one from my library and use the one from the rebel pack instead 🙂

Maxime Jeanmougin - Technical Artist
https://maximejeanmougin.com

Join the Bifrost Addicts community on Discord:
https://discord.gg/bifrost-addicts

jonah.friedman
Community Manager
Community Manager
Accepted solution

Hi Maxime and Sachin,

 

You did everything right with namespacing your nodes - I think this is because of collisions on the JSON file name. Currently the compounds all specify what json files they need for dependencies, and if there's a collision on the names it only loads one. We're already working to changing this to not have any dependencies on the names of json files, and only on the name and namespace as you expected.  (For tracking this is Bifrost-868). 

 

For now, one of us needs to change the name of that json file. However we also need to change the name of the include in any file that's using it, so I think I'll do that in the rebel pack. 

 

Jonah Friedman
Bifrost Product Manager

Anonymous
Not applicable

Thank you for the detailed updates Jonah.

 

Cheers,

Sachin

0 Likes