Visualizer doesn't display attr as expected or Remesh broken
1296 2 0- geordiemartinez
- Member
- 45 posts
- Joined: April 2016
- Offline
I have a simple example file attached.
there is an int attribute called patch
and it has a value of either 1, 2, 3, 4, 5 in columns along the patch.
The remesh will transfer the values as expected on the borders of the mesh, but the interior will entirely be zero.
both in the geometry spreadsheet and the visualizer. This is not expected
I have noticed similar results with float values. interpolating completely wrong values far away from their original point in space values.
Here is a float attr called remesh_bug before remesh
and after:
BUT here is the truly odd thing, the correct expected value is in the geometry spreadsheet for the float value remesh_bug but not the integer value casted by the int function.
I am either missing something fundamental or some function I don't know to cast this float to a proper integer.
Please help
there is an int attribute called patch
and it has a value of either 1, 2, 3, 4, 5 in columns along the patch.
The remesh will transfer the values as expected on the borders of the mesh, but the interior will entirely be zero.
both in the geometry spreadsheet and the visualizer. This is not expected
I have noticed similar results with float values. interpolating completely wrong values far away from their original point in space values.
Here is a float attr called remesh_bug before remesh
and after:
BUT here is the truly odd thing, the correct expected value is in the geometry spreadsheet for the float value remesh_bug but not the integer value casted by the int function.
I am either missing something fundamental or some function I don't know to cast this float to a proper integer.
Please help
Edited by geordiemartinez - Oct. 4, 2020 02:57:53
- geordiemartinez
- Member
- 45 posts
- Joined: April 2016
- Offline
I just found there is a rint function that returns the proper integer value.
I guess the geom spreadsheet is rounding some 1.9#### values to 2 for space. and when int() is used it just chops off the tail float and keeps the first digit where rint() rounds first then returns the int.
This still doesn't explain remesh node is transferring interior integers as zeros.
I guess the geom spreadsheet is rounding some 1.9#### values to 2 for space. and when int() is used it just chops off the tail float and keeps the first digit where rint() rounds first then returns the int.
This still doesn't explain remesh node is transferring interior integers as zeros.
- geordiemartinez
- Member
- 45 posts
- Joined: April 2016
- Offline
-
- Quick Links