Mats Lemmens

Hi,

I have the same problem but when using the rbdbulletsolver sop. Not any of the force-guides show up when toggled on or off.

I am able to show them when doing the following:

When going into your vellumsolver/rbdbulletsolver, up top where the "breadcrumbs" or "adress" shows you where you are, you can see that you actually jumped an extra layer deeper. A dopnet is suddenly extra there. That's normal because how those nodes are build up, but if you enter that dopnet (click on it in the breadcrumb-thing), you enter a "locked off" dopnet and suddenly the guides are visible in the viewport, at least if you toggled them on on your force. If you now pin your viewport to that view, you can go back to the forces and adjust them.

The so called breadcrumb (I'm sorry, I don't have a better word)



So it seems that the toggle or view of the forces gets lost in the whole dop-setup that simplifies the rbdbulletsolver and vellumsolver.

edit: I am on version 21.0.440 on Linux.

I know it is an older post, but as johnmater is saying they want to improve the tools in there i have some remarks and maybe it get's some attention:

I'm working in the simulation industry and we often have to generate meshes from pointclouds that are several square kilometers. The pointclouds are not always perfect square and are, in my case, mostly following a river so i have very long but (relativly) narrow points clowds.

For these large pointclouds you often struggle with the sheer size. The pointcloud surface node has to have a very high subdivision to keep some detail. Wich results in a very high memory usage and is mostly unworkable. It also generates a border mesh around the pointcloud wich is going to big.

Another big problem is that the pointclouds we get are mostly already processed clouds: they have been converted into a very even grid point cloud. It looks like: 3D pointcloud to 2D pointcloud and added the height information again. It gives you a kind of JPEG compression: you have jagged edges.
If you mesh a pointcloud like this one, you'll get very jagged edges if a corner or difference in height is not exactly on the grid-lines. It would be nice if we could apply some kind of guid-geometry (curves, lines, ...) so that the surface-node takes them into account when connecting certain points. I'm thinking of something like you can add flow-lines from wich you can set the influence (and influence distance) it has on the pointcloud-surfacing so that it prioritizes the flowlines first when looking for the best points to connect.

or am i looking for a solution that already exists?

Thanks for reading!