Repository navigation
[3D Annotation] Variable point size for point clouds #11398
|
I've been trying out the 3D functionality for an upcoming expansion of our workflow but from my first experiences, I found that the displayed point sizes of the 3D model was very high and there was no option to change it a preference box or similar. My assumption from browsing through code was that the size was hardcoded in canvas3dView.ts. Is my assumption correct? Could a functionality to change the displayed point sizes of a model by a user be added? |
Replies: 4 comments 2 replies
|
Yes, your assumption is correct. The point size is hardcoded in canvas3dView.ts and isn't exposed in any settings: Perspective view: points.material.size = 0.05 (L1799). The perspective cloud is a clone of points taken at L1816, so it keeps this material. Making it configurable looks straightforward. The canvas already reads controlPointsSize from this.model.data.configuration (L1736). A pointSize value could be passed the same way, from a setting in the 3D player settings, and applied to the three point materials. |
|
I noticed that a similar feature was previously requested in #9461. Would it make sense to continue tracking this functionality there, or should this discussion be handled separately? I'm interested in exploring a possible implementation. |
|
It seems there has been something developed already in #9464 but hasn't been merged into the release branch. |
|
Following up: I opened #11413, which adds a "Point size" slider for point clouds (Appearance panel, 3D jobs only), based on the approach in #9464. It's waiting for maintainer review. If my earlier answer covered your question, could you mark it as the answer? It helps others who find this thread. |
Thanks for finding that. #9464 was closed on 2026-07-29 without being merged. It was never reviewed and now conflicts with develop, so it won't reach a release as it is. #9461 is still open.
The approach in #9464 (a point size slider in the appearance settings, passed to the 3D canvas) looks right to me. I'd be happy to rebase it onto current develop, credit @arianizadi as co-author, and apply the import fix suggested in the PR comments. Are you planning to pick it up, or shall I? And could a maintainer confirm whether a PR like this would be reviewed?