-
-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error won't allow to add custom shader properties #171
Comments
Can you send me the Blender file? |
Here: https://drive.google.com/file/d/1OHlXGUYiNJF9fZiU18Mc_0noqCvShNBB |
By the way, deleting the shader property is the only way to advance and finish the configuration mode, otherwise it gets "locked" |
For the record, these are the steps that lead to this error: Created multiple value based properties in the shader editor (subsurface, wetness, nails color, makeup, etc). They all included the old name format: "MustardUI Float - Subsurface" Making the UI search for the properties on it's own in configuration mode lead to the error. What I did to try to solve it but didn't work: I deleted the properties from the UI menu, that made the remaining options including the ability to "end" configuration mode to come back.
|
Ok, I'll take a look asap! Sorry I'm a bit busy lately :( |
Ok I found the issue, it was a missing check on the length of the section container. Thanks for reporting this! |
Error:
The conditions for this error may be (not sure) because I added the old MustardUI Float/Bool names to the initial values for some skin shader properties, example:
Value node name: MustardUI Float - Subsurface
Value node label: Subsurface
While working in configuration mode every other option (including end configuration mode) will disappear after that error message, it'll come back after I manually delete the shader property, BUT it won't let me manually add the node values properties again without the error showing up again now, even after changing back the value nodes names without the mustardui part on it, not allowing me to continue configuring the model.
The text was updated successfully, but these errors were encountered: