-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CMD line: add option to "use sensors" when using COMPUTE_NORMALS and OCTREE_NORMALS #1339
Comments
he is right, |
the original issue is from october, but its still it would be the last brick in my project, that thx for your answer, |
Hi. Since the COMPUTE_NORMALS is used to compute normals of structured scans (PTX, FARO, DP) and it's already using the sensor (origin), I assumed you were referring to the OCTREE_NORMALS method (the way to go with E57 files). I added a '-ORIENT SENSOR_ORIGIN' option to allow using the associated sensor origin as orientation point. |
I'll update the 2.12.alpha version (for Windows) later today. |
Ok, the latest 2.12.alpha version is now up to date. |
Sorry for the long wait: I finally fixed the bug! I fixed it: a517fed An updated version of CC 2.12.alpha will soon be online. |
This is actually 2 requests, but either solution would be welcome:
This would be helpful when computing normals of e57 files using the command line.
The GUI has the option to "use sensors when possible", but currently is is not possible compute e57 normals correctly, based on the sensor position, at the command line.
PTX and FARO files work correctly. The issue is PTX (exported from FARO Scene) are enormous files and take forever to export.
The text was updated successfully, but these errors were encountered: