Skip to content
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

"ID user decrement error" #141

Closed
mokujinh opened this issue Dec 11, 2023 · 4 comments · Fixed by #152
Closed

"ID user decrement error" #141

mokujinh opened this issue Dec 11, 2023 · 4 comments · Fixed by #152
Assignees
Labels
bug Something isn't working
Milestone

Comments

@mokujinh
Copy link

I seem to have come through some errors with the Add-on version after checking the console after blender crashed on me a couple of times.

Here are some screen of the errors and what it causes.
2351432513425

4124124

Apparently it causes many fake users and also it crashes blender when I try to open or make a new project as well.

I tried uninstalling the latest UI Version 3 and blender won't crash anymore and the errors won't show up on the console anymore.

This happen to a model I updated from 3.6 to 4.0, (I appended the model to a clean project first).

I tested the older models version in blender 3.6 with the script version of MustardUI and they work fine and the errors won't show on the console either.

@mokujinh
Copy link
Author

mokujinh commented Dec 11, 2023

Update: Figured out the source of the error may be changing the bone layer name before it being assigned to a specific mesh in the UI configuration mode.

Edit update: the error specifically happens when assigning a bone collection to an outfit part. Changing the name of the bone collection but not assigning it to an outfit part does not produce this error.

@Mustard2 Mustard2 added the bug Something isn't working label Dec 11, 2023
@Mustard2 Mustard2 self-assigned this Dec 11, 2023
@Mustard2
Copy link
Owner

Wow this seems like a major issue.

I did see those errors in the console, but I thought it was just a small warning from Blender. Apparently, it isn't.

Let me check. :)

@Mustard2
Copy link
Owner

It seems like it's a Blender bug. I reported it:
https://projects.blender.org/blender/blender/issues/116061

@Mustard2
Copy link
Owner

It seems it will be fixed in Blender 4.1 :)

@Mustard2 Mustard2 added this to the Version 0.32 milestone Jan 20, 2024
@Mustard2 Mustard2 linked a pull request Mar 10, 2024 that will close this issue
Mustard2 added a commit that referenced this issue Mar 10, 2024
@Mustard2 Mustard2 unpinned this issue Mar 15, 2024
Mustard2 added a commit that referenced this issue Mar 19, 2024
- Feature: The updater function checks the minimum Blender version required by the remote MustardUI version and show additional messages to prompt the user to update Blender if necessary
- Bug: Children armature collections were not showing.
- Bug Auto Smooth Normal not working in Blender 4.1 #151 : Compatibility with Blender 4.1 (normals auto smooth switched to modifier)
- Bug "ID user decrement error" #141: Mask support for Armature bones has been reintroduced (due to the Blender 4.1 fix of the ID decrement error)
- Bug: Removed a cause of failure for the addon to be disabled/removed/re-installed/updated.

Note: this version is still also compatible with Blender 4.0, but I bumped the minimum version just in case. That is, it should be safe to use MustardUI 0.31.1 also with Blender 4.0.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants