CUAManager

Plugins CUAManager

Hi was woundering if anyone could help me out here. Plugin works fantastick and autoloads working as it should, but the thing is if i (create a scene > save it > Restart > reopen the scene) autoload loads the plugins/settings onto other people atoms who dont have the morph that should activate the trigger.
Dont know if this Error code is of any help but added it anyway
 

Attachments

  • 4113a63a199cdfce2b97b9687b2bb3f9.png
    4113a63a199cdfce2b97b9687b2bb3f9.png
    40.1 KB · Views: 0
Hi was woundering if anyone could help me out here. Plugin works fantastick and autoloads working as it should, but the thing is if i (create a scene > save it > Restart > reopen the scene) autoload loads the plugins/settings onto other people atoms who dont have the morph that should activate the trigger.
Dont know if this Error code is of any help but added it anyway

Try disabling CUAManager and load the scene and see if you encounter the same problems. If not, keep going and try to merge-load the plugin preset manually (that normally CUAManager triggers). Does the problem still happen?
 
Try disabling CUAManager and load the scene and see if you encounter the same problems. If not, keep going and try to merge-load the plugin preset manually (that normally CUAManager triggers). Does the problem still happen?
No if i disable auto load or disable the plugin(CUAM) it dosent happen
 
No if i disable auto load or disable the plugin(CUAM) it dosent happen
But was hoping to finde a resolution to the issue, wethere its my settings or so on, was looking for something like "dont load autotriggers on scene load" but cant seem to find anything, and looked all of my triggers and the plugins that it loads dont even fit the morph that should trigger it, but belongs to another person atom in the scene that it loads on the wrong person.
 
But was hoping to finde a resolution to the issue, wethere its my settings or so on, was looking for something like "dont load autotriggers on scene load" but cant seem to find anything, and looked all of my triggers and the plugins that it loads dont even fit the morph that should trigger it, but belongs to another person atom in the scene that it loads on the wrong person.
It could be that AlterantiveFuta plugin just isn't supported with CUAManager plugin triggers. All I can see from the stack trace is an exception thrown by the AlternativeFuta plugin. Sadly I don't have the time to further dive into this for some time to come, if at all. Consider it an unsupported plugin in CUAManager in your specific use-case for now.
 
Thanks, all of this because some "brilliant" creators decided it was a better idea to reinvent the wheel and make hair as an atom instead of, you know, HAIR!
 
I've been messing around with some models that require CUAmanager and ran into an issue. I initially saved the hair with CUAM so I can transfer it to another scene. However, when I try to load the hair in a new scene it doesn't load the hair color. I only get a pure white version of the hair. Any idea what I'm doing wrong?
 
I've been messing around with some models that require CUAmanager and ran into an issue. I initially saved the hair with CUAM so I can transfer it to another scene. However, when I try to load the hair in a new scene it doesn't load the hair color. I only get a pure white version of the hair. Any idea what I'm doing wrong?
I don't know how the original scene colored the CustomUnityAsset atom (the hair). CUAManager requires any plugin that modifies colors to be stored on the CustomUnityAsset atom itself.

If that is the case then my guess would be that the plugin on the CustomUnityAsset atom (the hair) doesn't work well with CUAManager and how it restore color parameters due to internal workings in VAM. Try another plugin that colors CustomUnityAssets.
 
Back
Top Bottom