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
FYI, was exploring buildGeometry() for a faster point cloud when drawing the obj.computeFaces().vertices as discussed here and wonder if it's intentional or a bug that point() doesn't work?
The text was updated successfully, but these errors were encountered:
This one is intentional for now -- buildGeometry generates a thing that you can draw in one go, but fundamentally points are drawn with a different shader than regular meshes, so for now that means p5.Geometry is for meshes only. (Similarly, switching shaders inside buildGeometry won't save either for the same reason.)
I think if we want to support this, we might need to try merging points and strokes so that points can be stored alongside the other strokes on a p5.Geometry. We currently use a separate shader for points, and there are some aspects of strokes that currently would break if used for points (I think we assume that all strokes have >= 2 points when we convert strokes to meshes) so we'll need to update a few spots there too. If any contributors are interested in looking into how that might be done, let me know!
Most appropriate sub-area of p5.js?
p5.js version
1.11.7
Web browser and version
Chrome 136.0.7103.93
Operating system
MacOS
Steps to reproduce this
Steps:
buildGeometry()
shape using pointsclear()
orbackground()
then go poofline()
orsphere()
Snippet:
See example here.
FYI, was exploring
buildGeometry()
for a faster point cloud when drawing theobj.computeFaces().vertices
as discussed here and wonder if it's intentional or a bug thatpoint()
doesn't work?The text was updated successfully, but these errors were encountered: