You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If an object has a face with at least 2 vertices with the same coordinates, that face does not affect the object's center of mass and inertia vectors, but does affect polylines
The currenly used method of slicing the object into 12 slices checks for vertices within 0.15 units from the slice plane, so if the object is really big, none of its vertices will intersect with any of the slices, grid2dv3a fixes this
The miner is using the reversed mining method, first finding a combination of polylines and then constructing an object from them, to do this it's first generating a normal random object and scaling it up until none of its vertices intersect with any of the 12 slice planes, then adds the polyline points as same vertex faces since they don't affect the object's rotation, the scaled up random object does not affect the hash, it just makes the object look normal
A possible fix is to discard any such faces and start using grid2dv3a's slicing algorithm
The text was updated successfully, but these errors were encountered:
If an object has a face with at least 2 vertices with the same coordinates, that face does not affect the object's center of mass and inertia vectors, but does affect polylines
The currenly used method of slicing the object into 12 slices checks for vertices within 0.15 units from the slice plane, so if the object is really big, none of its vertices will intersect with any of the slices, grid2dv3a fixes this
The miner is using the reversed mining method, first finding a combination of polylines and then constructing an object from them, to do this it's first generating a normal random object and scaling it up until none of its vertices intersect with any of the 12 slice planes, then adds the polyline points as same vertex faces since they don't affect the object's rotation, the scaled up random object does not affect the hash, it just makes the object look normal
A possible fix is to discard any such faces and start using grid2dv3a's slicing algorithm
The text was updated successfully, but these errors were encountered: