::New();
[...]
polyData->SetPoints(p);
vertexFilter->SetInputData(polyData);
vertexFilter->Update();
pdMapper->SetInputConnection(vertexFilter->GetOutputPort());
pdMapper->Update();
actor->SetMapper(pdMapper);
```
and then changing the points every time needed by doing :
```
SOAData->SetArray(0, PointCloud.GetPointerX(), SizeX, false, true);
SOAData->SetArray(1, PointCloud.GetPointerY(), SizeX, false, true);
SOAData->SetArray(2, PointCloud.GetPointerZ(), SizeX, false, true);
p->SetData(SOAData);
p->SetNumberOfPoints(SizeX);
p->Modified();
polyData->SetPoints(p);
```
Seems to defer some type of lengthy operation at render time. Which leads me
to believe something is done for everypoint (much like i’d be doing manually).
I feel like I just pushed the work I avoided by adding all the new verts to the render
phase. Render time is fourthfold longer when just modifying the points compared to
when adding them the first time.
---
### Author:  [@dgobbi](https://discourse.vtk.org/u/dgobbi)
#### Post date: [August 27, 2019, 5:25pm UTC](https://discourse.vtk.org/t/adding-all-vtkpoints-at-once/1652/6 "2019-08-27T17:25:52Z")
You have the x, y, z components stored separately? I’m pretty sure that VTK will have to pack these so that the GPU can use them as a vertex buffer. Can your PointCloud store the points in packed format instead?
---
### Author:  [@jjackso2](https://discourse.vtk.org/u/jjackso2)
#### Post date: [August 27, 2019, 6:24pm UTC](https://discourse.vtk.org/t/adding-all-vtkpoints-at-once/1652/7 "2019-08-27T18:24:39Z")
The components are stored separately, yes. But even when I interleave the values to have a packed buffer to pass its pointer to do:
```
vtkDataArray* d = p->GetData();
d->SetVoidArray(packedData, Size*3, 1);
p->Modified();
```
The render time is as long as when I passed a SOA array. After tracing through the code it seems like
vtkOpenGLVertexBufferObject loses alot of time in
```
array->GetRange(range, i);
```
Which mean I’ll have to trace enven deeper because I do not understand why the Range would have to be computed because I supplied it when I set the dataPointer using:
```
d->SetVoidArray(packedData, Size*3, 1);
```
---
### Author:  [@dgobbi](https://discourse.vtk.org/u/dgobbi)
#### Post date: [August 27, 2019, 7:10pm UTC](https://discourse.vtk.org/t/adding-all-vtkpoints-at-once/1652/8 "2019-08-27T19:10:50Z")
I’m not sure what you mean when you say you “supply the range”.
In any case, you should be able to work around this by instantiating your vtkPolyDataMapper as a vtkOpenGLPolyDataMapper and then calling
```
mapper->SetVBOShiftScaleMethod(vtkOpenGLVertexBufferObject::DISABLE_SHIFT_SCALE);
```
I was surprised to see that the mapper does this range computation by default. It’s very computationally expensive. Looks like it was a recent change to VTK (just a couple years old).
---
### Author:  [@jjackso2](https://discourse.vtk.org/u/jjackso2)
#### Post date: [August 27, 2019, 10:04pm UTC](https://discourse.vtk.org/t/adding-all-vtkpoints-at-once/1652/9 "2019-08-27T22:04:58Z")
Thanks for the responsiveness!
This helped alot in both debug and release. I will probably be back when I feel like optimizing this even more. I feel like there may be more things we sould do with this to go even faster. Myabe as deep as the shaders that are used.
I now reach more or less 45fps while pushing 720k points each frame. Acceptable for now.
Thanks again David, you’re a good man!
---
### Author:  [@dgobbi](https://discourse.vtk.org/u/dgobbi)
#### Post date: [August 27, 2019, 11:43pm UTC](https://discourse.vtk.org/t/adding-all-vtkpoints-at-once/1652/10 "2019-08-27T23:43:06Z")
Glad to hear that things worked out!
If you haven’t tried vtkGlyph3DMapper yet, it should (in theory) be able to give better performance than vtkVertexGlyphFilter + vtkPolyDataMapper but it might not have exactly the same options.
---
### Author:  [@jjackso2](https://discourse.vtk.org/u/jjackso2)
#### Post date: [August 28, 2019, 9:04pm UTC](https://discourse.vtk.org/t/adding-all-vtkpoints-at-once/1652/11 "2019-08-28T21:04:25Z")
Unfortunately it doesn’t. It lenghtens the call to renWin-\>Render() tenfold. Even when I set the actor property SetRepresentationToPoints().
I was setting up my polyData as data to the 3dGlyphMapper and then setting it to the actor via SetMapper() and then updating the vtkPoints when they changed.
---
### Author:  [@dgobbi](https://discourse.vtk.org/u/dgobbi)
#### Post date: [August 28, 2019, 9:59pm UTC](https://discourse.vtk.org/t/adding-all-vtkpoints-at-once/1652/12 "2019-08-28T21:59:15Z")
The vtkGlyph3DMapper most likely ignores SetRepresentationToPoints().
What ‘Source’ did you use with vtkGlyph3DMapper? To do the equivalent of what you are doing with vtkVertexGlyphFilter, the code would look something like this:
```
# generate a glyph polydata with 1 point and 1 vert cell
auto pointSource = vtkSmartPointer::New();
pointSource->SetNumberOfPoints(1);
pointSource->SetRadius(0.0);
pointSource->Update();
auto mapper = vtkSmartPointer::New();
mapper->SetInputData(polyData);
mapper->SetSourceData(pointSource->GetOutput());
```
---
### Author:  [@jjackso2](https://discourse.vtk.org/u/jjackso2)
#### Post date: [August 28, 2019, 10:12pm UTC](https://discourse.vtk.org/t/adding-all-vtkpoints-at-once/1652/13 "2019-08-28T22:12:36Z")
That gave me about the same result in render time as it did with the previous iteration.
```
auto pointSource = vtkSmartPointer::New();
pointSource->SetNumberOfPoints(1);
pointSource->SetRadius(0.0);
pointSource->Update();
vtkDataArray* d = p->GetData();
d->SetVoidArray(packedData, Size * 3, 1);
p->Modified();
polyData->SetPoints(p);
auto mapper = vtkSmartPointer::New();
mapper->SetInputData(polyData);
mapper->SetSourceData(pointSource->GetOutput());
actor->SetMapper(mapperstrong text);
```
and then “p” is updated whenever my data changes by setting void arrays to it.
```
vtkDataArray* d = p->GetData();
d->SetVoidArray(packedData, Size * 3, 1);
p->Modified();
```
I am not sure what is the difference internally between this method and the previous metho but maybe this one creates a lot of VBOs that cant be treated as chunks of data when given to the shader.
J