Export Model still unhides everything in Blender #268

New issue

Closed

opened 2025-01-08 03:41:43 +00:00 by Ghost · 2 comments

Ghost commented

2025-01-08 03:41:43 +00:00

(Migrated from git.disroot.org)

Blender Version:
4.2.2 LTS

Cats Version:
4.2.2.3

Operating System:
Windows 11

Steps to Reproduce:
Hide model sub meshes
Click Export Model and then click Export Model again
Observe

Screenshots or Error Messages:

Additional Context:
N.A.

Description of Issue: Recently updated CATS and the changelog claims to have made it so that the Export Model button doesn't unhide everything, but this still occurs. Just to make sure, I uninstalled CATS and did a clean install from the GitHub release. Blender Version: 4.2.2 LTS Cats Version: 4.2.2.3 Operating System: Windows 11 Steps to Reproduce: Hide model sub meshes Click Export Model and then click Export Model again Observe Screenshots or Error Messages: ![ss1](https://github.com/user-attachments/assets/b3e692f7-68cb-4002-8ca7-707eb734f6a2) ![ss2](https://github.com/user-attachments/assets/a4b5b177-0cf2-416f-8627-251aa7cc0380) Additional Context: N.A.

Ghost commented

2025-01-08 12:38:00 +00:00

(Migrated from git.disroot.org)

Hi, this happened due to GitHub not merging my PR's correctly, This has been fixed in the DEV version for Blender 4.2 and 4.3 and will be released to stable in the next week or so.

My local git merge everything correctly, GitHub git system is sub par and doesn't do merging that well.

Hi, this happened due to GitHub not merging my PR's correctly, This has been fixed in the DEV version for Blender 4.2 and 4.3 and will be released to stable in the next week or so. My local git merge everything correctly, GitHub git system is sub par and doesn't do merging that well.

Ghost commented

2025-01-08 13:15:04 +00:00

(Migrated from git.disroot.org)

Fully tested and is now in Dev version, closed as is now fixed, I plan to release the next stable update on Monday.

If this issue keeps happening in the dev version (Or in the next stable) please re-open this issue.

Fully tested and is now in Dev version, closed as is now fixed, I plan to release the next stable update on Monday. If this issue keeps happening in the dev version (Or in the next stable) please re-open this issue.