Hello everyone!
I’ve written a simple web viewer and I want to be able to analyze the type of face (plane, cylinder, cone, etc.) when a face is selected, I’ve got the properties of the face in the code, but I don’t know what to do next, if I’m going in the right direction.
Thank you beau!
The examples you provided are very helpful to me. In addition to identifying the types of individual surfaces, I would also like to be able to recognize the shapes of combinations of surfaces, such as square holes, countersunk holes, keyway holes, conical holes, straight slots, T-slots, etc. This would allow me to apply it to my CNC machining automatic quoting feature.
The following is an example diagram in sequence:
Unfortunately, the level of feature recognition you are describing is not provided with the HOOPS Communicator SDK.
Regarding getting the surface area of a face with Communicator, it looks like @tino was able to to provide some guidance in this post. I would just add that you may also be able to calculate it if you are using HOOPS Exchange (which is part of HOOPS Web Platform). In this case, you’d be working with an additional API and need to link your Communicator and Exchange data.
According to the the 2024.4.0 release notes, the Communicator.SubentityProperties is now deprecated (and hidden).
The API to compensate for this deprecation is not documented yet (as far as I know) and It seams this API is far from compensate the deprecation (only Utils.isFace, Utils.isPlaneElement, Utils.isLineElement and a few more).
We’ve migrated to the version 2024.4.0 and as far as we tried the subentity properties object (origin, radius, normal, …) is always null (it looks props are not available anymore) and we can get the type of the face.
@beau.trifiro
Could you please explain how to do the simple demo you’ve made now the SubentityProperties are deprecated?
(And how to extract the subentity properties)
Hi @aloys, I’ve created a feature request to undeprecate and unhide Communicator.SubentityProperties. I’ve reached out to the engineering team to see if there is anything missing from our documentation that would enable the capability in this demo and will follow up here if so. I apologize for the inconvenience this change has caused. If you are an existing partner with a support account, please create a feature request as well: https://support.techsoft3d.com/ (or you can let me know your organization so I can create one for you).