Import 3d texturized model into revit (not just point cloud)

[Anonymous]

Hi everyone,
I've carried out a Image-based metric survey and I manage it with Agisoft Photoscan.
Firstly, I've obtained a  very dense point cloud ( > 1 500 000 000 points)  and I've already imported it on Revit with success, so far so good.
In Photoscan I've obtained a 3d texturized model (the textures are not materials but a high quality photo collage) as shown in the attached picture (it's just a piece of the whole survey) .
My question is: there is a way to import this 3d texturized model in Revit? 

Photoscan permits to export model in :
• Wavefront OBJ • 3DS file format • VRML • COLLADA • Stanford PLY • Autodesk DXF • U3D • Adobe PDF


Thanks you in advance for the help in the resolution of this matter.

Best regards,

Andrea

[cbcarch]

You can Link or Import ( recommend Link, not Import) a .dxf file.

Not sure if textures will come through into Revit.

Give it a try and report back.

[Anonymous]

Thank you Mr. Collins.
I've tried right now. Photoscan produces a dxf file of 377 mb and when I tent to link it, Revit not responding. 

[cbcarch]

How much RAM does you PC have?

Sounds perhaps like a memory limit.

The dxf is probably really heavy with all those textures.

Your GPU will also need lots of memory--what are your GPU specs?

[Anonymous]

Here below the specification of my notebook:

• The GPU is a Geforce GTX 960M (4GB);
• RAM 16 GB
• Processor:  i7 -6700 HQ (4 cores)

[cbcarch]

I'd suspect the 16GB or RAM is the problem.

You could try opening the dxf in AutoCad and Purging it to get file size down--but the heavy texturing will still be an issue.

[Anonymous]

That's sounds bad

[cbcarch]

Good news is that RAM is inexpensive! 16 GB is not really going to keep up with large complex Revit jobs,

Not to mention throwing in large Point Clouds and heavily textured files such as yours.

[dgorsman]

I suspect it's not the texturing at all; the DXF file is likely only the mesh.  You can attempt to walk it through other formats first, such as 3DS, but you're going to get the same results.

Revit, as a design tool, is set up to work with ideal solids.  When converted the scans into a mesh, you got *all* the details - warps, bumps, twists, and all.  Even without the textures Revit is likely going to choke on something that big especially all in one go.  And if you need a monster computer to work with it (what you stated isn't even close), chances are whoever gets the model after you won't be able to do anything with it.

If you are hoping to use that mesh as a substitute to creating Revit objects you're probably not going to get that.  Ideally, you would chop the mesh up into small, logically workable design areas.  Bring those into Revit individually, one at a time, and use Revit to create objects that are best-fit.  Then remove the mesh, and move on to the next one.