Closed
Description
http://processing.org/reference/PShape.html
Shape
- PShape
- createShape()
- loadShape()
Loading & Displaying
- shape()
- shapeMode()
Later version!
Metadata
Metadata
Assignees
Type
Projects
Relationships
Development
No branches or pull requests
Activity
lmccart commentedon Dec 10, 2014
addressed with https://github.com/lmccart/p5.js/issues/458
asfarley commentedon Sep 21, 2018
May I ask what happened here? That link gives a 404. I'm interested in the PShape functionality for rendering large point-clouds.
Spongman commentedon Sep 21, 2018
i believe that issue was moved here: #458
asfarley commentedon Sep 21, 2018
From my reading, that discussion is more about re-implementing p5.js to render SVG, rather than replacing PShape.
Really, what I want to do is optimize the display of a point-cloud with many thousands of points. Somewhere I read that PShape is the way to do this in Processing, hence my question.
Is there any recommended facility for making something like a vertex buffer to contain an object that I'm rendering repeatedly at different locations? Is p5.js looking for something like this as a contribution?
Spongman commentedon Sep 21, 2018
do you mean something like this: https://p5js.org/reference/#/p5/vertex ?
b2renger commentedon Sep 22, 2018
I think what @asfarley is referring to is creating a PShape object in which you could store points an geometric forms ready to be rendered in one call and I guess on the gpu
probably something like that : https://processing.org/tutorials/pshape/
Dan talks about it and refers to this as "retained" mode to draw VBO
asfarley commentedon Sep 22, 2018
@b2renger yes, that's exactly what I meant.
rsodre commentedon Jan 19, 2022
I don't understand why this has been closed.
This is a fair request, to implement a great Processing feature, and was not addressed by #458 as mentioned.
Please reopen it, even if it's not on the roadmap, it should be.
darthgrayter commentedon Mar 5, 2022
I agree, I feel like this should be a default feature.
designbyadrian commentedon Jul 25, 2022
I really hate to +1 an issue, but this is an unsolved issue from 2013 that still remains unresolved with no opinion from the devs why it shouldn't be included. I'm experiencing huge slowdowns while drawing many vertices in each draw() call. Being able to cache the shape somehow would be a solution.
davepagurek commentedon Jul 25, 2022
Is this something that would be solved by drawing to a p5.Graphics and reusing that? Or for 3D, creating a p5.Geometry and then drawing it with
model()
?