Arye Ramaty aryeramaty
  • Joined on 2018-06-10
Arye Ramaty pushed to fix-index-of-nearest at aryeramaty/blender 2024-10-15 18:13:52 +02:00
8cbae6ceef make format
Arye Ramaty commented on pull request blender/blender#129021 2024-10-15 08:22:46 +02:00
Fix: Wrong offset in the 'Has Neighbour' output of the 'Index of Nearest' node

Ah, stop. Idea was that for single element here is no neigboard, so you actually should count with starting from 0 rather than 1.

As I understand the current state is as For 1 element:…

Arye Ramaty commented on pull request blender/blender#129021 2024-10-14 23:41:01 +02:00
Fix: Wrong offset in the 'Has Neighbour' output of the 'Index of Nearest' node

Actually, the behavior is more complex without the former fix (#128998), I'll create a video in a moment

Arye Ramaty commented on pull request blender/blender#129021 2024-10-14 23:35:54 +02:00
Fix: Wrong offset in the 'Has Neighbour' output of the 'Index of Nearest' node

Yep, This is 4.4 from 8.10: image file:///home/arye/Desktop/tmp/BugReport2.blend

Arye Ramaty commented on pull request blender/blender#128998 2024-10-14 19:58:18 +02:00
FIX #128997: Wrong evaluation of outputs in the Index of Nearest node

I created another PR for the bias in the 'has neighbor', #129021

Arye Ramaty commented on pull request blender/blender#129021 2024-10-14 19:57:41 +02:00
Fix: Wrong offset in the 'Has Neighbour' output of the 'Index of Nearest' node

As a note, this has been split from #128998

Arye Ramaty created pull request blender/blender#129021 2024-10-14 19:56:20 +02:00
Fix wrong offset in the 'has neighbour' output of the 'index of nearest' node
Arye Ramaty created branch fix-has-neightbor-wrong-calculation in aryeramaty/blender 2024-10-14 19:53:41 +02:00
Arye Ramaty pushed to fix-has-neightbor-wrong-calculation at aryeramaty/blender 2024-10-14 19:53:41 +02:00
1ef9f5cd51 Fix wrong offset in the 'has neighbour' output of the 'index of nearest' node
Arye Ramaty pushed to fix-index-of-nearest at aryeramaty/blender 2024-10-14 19:49:00 +02:00
4b48695af9 I accidentally checked the submodule commit...
Arye Ramaty pushed to fix-index-of-nearest at aryeramaty/blender 2024-10-14 19:47:04 +02:00
71faf5fc44 Revert this change due to splitting this into it own PR
Arye Ramaty pushed to fix-index-of-nearest at aryeramaty/blender 2024-10-14 19:46:08 +02:00
9732e99dce Fix field evaluation and 'Has Neighbor' count
0319b7b50a Fix #127611: Linked material can be modified by Copy/Paste Material
b2e0193cc1 Fix #128929: Multires face set automasking doesnt work with no face set
a205e34158 Fix #128933: Dyntopo density brush prints constant console errors
10f2d683ba Cleanup: Use dedicated string reference type for drop tooltip drawing
Compare 17 commits »
Arye Ramaty commented on pull request blender/blender#128998 2024-10-14 19:42:31 +02:00
FIX #128997: Wrong evaluation of outputs in the Index of Nearest node

Thanks! I suspected that would be the case but thought a one-liner would be fine, anyway, I'll split them.

Arye Ramaty created pull request blender/blender#128998 2024-10-14 15:08:07 +02:00
Fix field evaluation and 'Has Neighbor' count
Arye Ramaty created branch fix-index-of-nearest in aryeramaty/blender 2024-10-14 15:05:32 +02:00
Arye Ramaty pushed to fix-index-of-nearest at aryeramaty/blender 2024-10-14 15:05:32 +02:00
84fa16d453 Fix field evaluation and 'Has Neighbor' count
62b7947769 Merge branch 'blender-v4.3-release'
1246baa81b Fix #128935: Preview range to selected keyframes wrong
99b876e2bc Fix #128946: GPv3: Can't select materials in Modifier
724b9dd02c Update tests/data submodule
Compare 10 commits »
Arye Ramaty commented on issue blender/blender#128997 2024-10-14 15:04:01 +02:00
Index of nearest node evaultes GroupID input incorrectly

This issure is similar to this one: #126595

Arye Ramaty opened issue blender/blender#128997 2024-10-14 15:03:06 +02:00
Index of nearest node evaulte GroupID input incorrectly
Arye Ramaty commented on issue blender/blender#126595 2024-08-21 12:38:08 +02:00
Regression: Group ID in Fill Curve Evaluate inconsistantly

BTW, The FIll Curve behavior is correct even when the Capture Attribute's Geometry output isn't connected to anything: image