Displayed texture resolution on OBJ import of textured mesh in 3D window

Displayed texture resolution on OBJ import of textured mesh in 3D window

timrahn
Observer Observer
262 Views
3 Replies
Message 1 of 4

Displayed texture resolution on OBJ import of textured mesh in 3D window

timrahn
Observer
Observer

One of the most valuable developments for me in my work recently has been the increasing availability of high quality photogrammetry services that generate accurate and detailed textured meshes from photos (eg Polycam etc). As best I can tell OBJ is the only/best way to bring these into Revit currently and it has recently become a workable method, even for multiple acre "scans" on the order of hundreds of MB files.

 

One issue I (and best efforts of o1) have not been able to solve and which is hindering the last leg of a pretty fun workflow is getting the full resolution texture to show in 2D views and 3D views for actual published output (drawings of a detailed mesh). If I render (actual render command) the view in a 3D window the full resolution is available, so we can rule out a number of issues. But in any 2D or 3D view, the texture is displayed with much less resolution, and this is consistent from small meshes to large.

 

Rhino and Blender are able to show the full resolution in 3D extremely well, which seems to tell me that the issue isn't my hardware, drivers, OS, etc, but Revit itself. 

 

So the question is: Can anyone describe how Revit is set to degrade texture resolutions, perhaps only with OBJ links/imports, in 2D and 3D views versus with rendering, and how it can be changed?

 

Can publish screenshots if helpful.

0 Likes
263 Views
3 Replies
Replies (3)
Message 2 of 4

RDAOU
Mentor
Mentor

@timrahn 

 

Revit handles solids better than meshes. If you wish to have better quality, I would suggest that you use .SAT or .AXM 

 

 

YOUTUBE | BIM | COMPUTATIONAL DESIGN | PARAMETRIC DESIGN | GENERATIVE DESIGN | VISUAL PROGRAMMING
If you find this reply helpful kindly hit the LIKE BUTTON and if applicable please ACCEPT AS SOLUTION


0 Likes
Message 3 of 4

timrahn
Observer
Observer

Thanks for the information RDAOU. Neither of these solutions seem viable for my work, since I'd have to convert meshes to a solid before exporting SAT (seems possible in Rhino to export this but I need to convert meshes first), and I don't plan on including FormIt or any other Autodesk software beyond Revit, so .AXM is a non-starter.

 

But I will remember that solid models may work better in Revit if a solution arises.

Thanks again

0 Likes
Message 4 of 4

RDAOU
Mentor
Mentor

@timrahn wrote:

Thanks for the information RDAOU. Neither of these solutions seem viable for my work, since I'd have to convert meshes to a solid before exporting SAT (seems possible in Rhino to export this but I need to convert meshes first), and I don't plan on including FormIt or any other Autodesk software beyond Revit, so .AXM is a non-starter.

 

But I will remember that solid models may work better in Revit if a solution arises.

Thanks again


@timrahn 

 

If so and you have grasshopper, then try to export as Directshape or Freeform Element via Speckle. It might give you better results in Revit 

 

 

YOUTUBE | BIM | COMPUTATIONAL DESIGN | PARAMETRIC DESIGN | GENERATIVE DESIGN | VISUAL PROGRAMMING
If you find this reply helpful kindly hit the LIKE BUTTON and if applicable please ACCEPT AS SOLUTION


0 Likes