Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
The current size limitations of the mesh tool restricts the tool to be used for small structures or objects. This tool could make life much easier in BIM 360 Glue, Navisworks and Revit if it the quantity of scans allowed was increased and the crop box size limitations were relaxed.
I'd love to know more about how this would help your workflow in Glue/Navis/Revit. In my experience, those products work more smoothly w/ Point Clouds than they do with the type of super-detailed textured mesh you get from the Object Mesh service. Usually we get this type of request from folks that need to take the data somewhere that can't handle point clouds.
Is there a specific reason you need a mesh vs. a point cloud?
There are a few use cases for meshes that we've experimented with. The major one being that the file size of a mesh is significantly smaller than that of a point cloud (depending on the settings). This would reduce or eliminate the need to model from a point cloud for existing conditions in a lot of cases. (It's still worth while trying to create tools that will help create accurate models from pointclouds.) For coordination purposes on a renovation job site, the GC and subcontractors often have to tie into existing utilities. It's often hard to visually see the pointcloud in Revit and it's almost impossible to share a point cloud in glue, so someone has to model those elements which takes time and costs money. With a mesh, you can drop it into Navis and save it as an NWD and import into Revit (2018) or Glue and have a better visual understanding of where things are at and you wouldn't have to worry about anyone having to model or adjust a model. The same goes for if you scan the structure of a facility. Meshes seem to be easier to use to adjust a revit model vs. a using a point cloud. The other useful workflow for a mesh would be for creating more realistic fly throughs for presentations, proposals and site logistics planning using infraworks. Meshes seem to have the potential to provide a better VR experience if they can be used in some of your VR engines. Those are a few examples, but I wonder what others are thinking... outside of the 3D printing world?
I noticed some listed Mesh enhancements in ReCap Pro V.4.2.2.15, but was wondering if you could expand on what those enhancements were. It sounds like you can now import an unstructured pointcloud, perhaps from another product as an .rcp file and then create a mesh from it? Have you all been able to increase the allowable area for mesh creation? Lastly, have you been able to improve the performance of the pointcloud when points are placed in scan regions or deleted? I'd really like to be able to clean up and remove all unnecessary points prior to creating a unified .rcp or mesh.... Thanks, Jon
