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

Fix custom nodes #481

Merged
merged 29 commits into from
Apr 7, 2024
Merged

Fix custom nodes #481

merged 29 commits into from
Apr 7, 2024

Conversation

BradyAJohnston
Copy link
Owner

@BradyAJohnston BradyAJohnston commented Apr 5, 2024

Fixes the creation of custom nodes in 4.1, as well as bumping bpy and python verisons to 4.1 and 3.11 repsectively.

There seem to be a number of problems with bpy 4.1 though. It is unable to be installed on macos. The tests pass on other platforms but the GHA are reporting failure. If I run the test suite through Blender though it passes.

Copy link

codecov bot commented Apr 5, 2024

Codecov Report

Attention: Patch coverage is 76.47059% with 24 lines in your changes are missing coverage. Please review.

Project coverage is 75.28%. Comparing base (b8fe90f) to head (303bcfd).

Files Patch % Lines
molecularnodes/blender/node.py 50.00% 12 Missing ⚠️
molecularnodes/blender/nodes.py 88.46% 6 Missing ⚠️
molecularnodes/io/parse/mrc.py 77.77% 4 Missing ⚠️
molecularnodes/ui/ops.py 0.00% 2 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##              4.1     #481      +/-   ##
==========================================
- Coverage   76.02%   75.28%   -0.74%     
==========================================
  Files          40       41       +1     
  Lines        3716     3731      +15     
==========================================
- Hits         2825     2809      -16     
- Misses        891      922      +31     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

it seems that there is now a blender 4.1 issue where even if the underlying `.vdb` changes, if you reimport the file it still uses the preview for the 'old' version.

Because of this, the created .vdb file path now contains whether or not it was centred and inverted, which makes different files and fixes the issues.
@BradyAJohnston BradyAJohnston merged commit 2802a47 into 4.1 Apr 7, 2024
2 of 8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Blender 4.1 custom nodes broken Blender 4.1 import density broken
1 participant