Improve visuals in MetaballsMode - #794
Conversation
…tribution calculations
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📜 Recent review details⏰ Context from checks skipped due to timeout. (86)
🔇 Additional comments (3)
Summary by CodeRabbit
WalkthroughChangesMetaballs falloff calculation
Merge Risk: ⚪ Minimal · up to The change refines MetaballsMode brightness calculations to use the full contributions range and removes initialization magic numbers, improving edge brightness behavior. No actionable merge-blocking risk remains after normal checks and review. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches✨ Simplify code
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
JanPetterMG
left a comment
There was a problem hiding this comment.
Looks good to me. I've reviewed the code and tested it on the actual hardware, and everything looks good. Approved!
|
Thanks for the contribution @Solmath! I really appreciate you taking the time to improve this. It's now included in the upcoming v2.5.2 release. |
Creating a separate PR for the refinement of the contribution calculation from #788
Currently the brightness calculation does not use the entire contributions array, due to the hard coded
1<<6:This factor should be related to the size of the contributions array.
Also the initialization of the contributions array is not very intuitive, so I tried to make it clearer.
Key changes
falloffResolutionduring init of contributions and in calculation of brightnessImpact