Dreamer-Zero
commented
1 year ago i keep having this same exact issue
Open DrPinkieDie opened 1 year ago
Dreamer-Zero
commented
1 year ago i keep having this same exact issue
idrisz19
commented
1 year ago The fix is in the development branch. You can download the fixed version from this link.
Frankly, I'm disappointed in the current crop of developers. This issue keeps popping up, yet there hasn't been any updates to the master branch or any new stables. I'm not even a developer for this project, yet this is the third time I had to respond to a bug report on account of the actual developers seemingly not paying attention.
Given the inactivity of the repository owner, I find myself wondering if the current developers even possess the authority to update the master branch or release a new stable. If that's the case, I'm wondering why none of the active developers forked the project in order to develop it at a faster pace.
Failing to keep pace with Blender stable releases isn't acceptable. If the current developers don't clean up their act, they might find themselves competing with a fork.
feilen
commented
1 year ago Given the inactivity of the repository owner, I find myself wondering if the current developers even possess the authority to update the master branch or release a new stable.
:sweat_smile:
If that's the case, I'm wondering why none of the active developers forked the project in order to develop it at a faster pace.
Charmster-Wang
commented
1 year ago The fix is in the development branch. You can download the fixed version from this link.
Frankly, I'm disappointed in the current crop of developers. This issue keeps popping up, yet there hasn't been any updates to the master branch or any new stables. I'm not even a developer for this project, yet this is the third time I had to respond to a bug report on account of the actual developers seemingly not paying attention.
Given the inactivity of the repository owner, I find myself wondering if the current developers even possess the authority to update the master branch or release a new stable. If that's the case, I'm wondering why none of the active developers forked the project in order to develop it at a faster pace.
Failing to keep pace with Blender stable releases isn't acceptable. If the current developers don't clean up their act, they might find themselves competing with a fork.
Wow! Thanks! After modifying it according to your method, it works again!
Traceback (most recent call last): File "C:\Program Files\Blender Foundation\Blender 3.5\3.5\scripts\modules\addon_utils.py", line 369, in enable mod.register() File "C:\Users\kingc\AppData\Roaming\Blender Foundation\Blender\3.5\scripts\addons\cats-blender-plugin-master__init__.py", line 319, in register bpy.context.window_manager.addon_support = {'OFFICIAL', 'COMMUNITY', 'TESTING'} ValueError: bpy_struct: item.attr = val:: 'TESTING' not found in ('OFFICIAL', 'COMMUNITY')