Olukayode Talabi

@tamte, thank you for your suggestions. The float values are already set at 64-bit in the Lidar node and using an Attribute Cast change nothing. It seems translating the point cloud from the obj level removes this issue. However, I have a particular pipeline that is contained in the geo context that requires the translation to happen before a couple other actions, most of which has been automated in an HDA. Point is, it would be preferred to have the translation happen within the geometry context, and not the object context.

Is there a reason why moving on obj works where geo does not? Is there a software preference or something I am missing?

Has anyone else ran into an issue where when you import a point cloud (as an .e57 or .las file) and transform the points at a certain distance, the points start to clamp and display in a grid like projection? Is there a way to fix this other than centering the point cloud? The work I do requires the pc position to be at a certain location to match other incoming data form other collaborators.

Hey all. I have been r&ding the new rbd car workflows in Houdini and have been stuck trying to figure out why my vehicle collapses even though there are constraints connecting everything.
As a quick breakdown. I have a mustang model that I cleaned up with new and organized naming conventions and groups. I used a rbdcarrig sop to pack the geo and set up the body and wheels while also giving it a speed value. I used the new rbdcarfracture sop to set up the constraints for the different components of the vehicle. When attaching a rbdbulletsolver sop, even with default settings, it falls apart during simulation.
Any advice to help me troubleshoot? I assume many other artists struggle with this setup as well. Please let me know if you have any questions concerning info I may have left out or need any clarification.