From Rhino to the viewer: prepare your model for a client

To bring a Rhino project into DRB Studio, try the 3DM file or prepare a mesh export such as OBJ. The choice depends on what your file contains and how it is interpreted when opened. This guide sets out a repeatable review for an architectural presentation. It does not promise to preserve every Rhino feature or let you edit surfaces in the viewer.

The viewer interface is in Spanish. Spanish control names are followed by their English meaning in this guide.

Editorial review: October 20, 2026 · DRB Studio.

1. Keep the working model separate from the presentation copy

   Define the question you want to resolve with the client. A curved roof calls for views of its profile and supports; a renovation may need to explain furniture and circulation. Select the part of the project that answers that question and keep the master file intact.

   Rhino’s Export command saves selected objects to another file. The Rhino 8 documentation also describes options for saving textures and other properties. See McNeel’s Rhino 8 Export command (source review: October 20, 2026) to check which options apply to your chosen format. Exporting a selection is different from saving a complete copy of the document.

   Give the copy a recognizable revision name. Record its units and save an overall screenshot. Use that reference to spot rotated or missing objects and surfaces seen from the back. Avoid relying on color alone to identify building elements.

2. Try 3DM before changing your workflow

   The viewer supports the 3DM format, but that does not guarantee every file version, plug-in or object type will retain its appearance. Open a representative copy and check it first. If something fails, record the missing object and file version. A specific diagnosis is more useful than repeatedly converting the entire project.

   Check both a simple and a complex object: for a house, perhaps a flat wall and a curved stair. Confirm that both appear, retain their relative positions and leave the interior readable. Then compare materials and names. Do not assume plug-in data will be available in the presentation.

   If the import does not work for your case, prepare a mesh in Rhino. Keep the earlier test for comparison. The aim is a dependable visual copy, while surfaces and modeling decisions remain under your control in the original file.

3. Export an OBJ mesh with its materials

   Rhino 8 can export surfaces as polygon meshes in OBJ. Enable material definitions if needed; this creates an associated MTL file. Also check texture coordinates and the option that transforms the vertical axis. See McNeel’s Rhino 8 OBJ export documentation (source review: October 20, 2026).

   Keep the OBJ, MTL and images together in a test folder. Preserve their names and select supporting resources when opening the model in the viewer. If a finish is missing, first check that its file accompanied the model. This helps distinguish a missing resource from a rendering difference.

   Do not silently change the proposal during export. If a surface is open or a junction is unresolved, mark it as pending. A meeting copy should preserve that distinction even when it has less detail than the working model.

4. Choose mesh detail for the views you need

   A mesh represents surfaces with faces. Rhino’s Mesh command controls their generation; see McNeel’s Rhino 8 Mesh documentation (source review: October 20, 2026). Compare an initial export with a less detailed version from the same viewpoint. There is no need to choose the densest setting by habit.

   Inspect curved silhouettes against the background and zoom in on edges the client will see. If a roof loses its smooth profile or a railing becomes angular, simplification is affecting how the design reads. If the difference appears only in a detail outside the presentation, a lighter copy may be appropriate.

   Check repeated elements too. Detailed furniture can slow rendering without helping answer a client’s question. Keep furniture that explains scale and use, and try a simpler version where ornament makes navigation difficult. Document the choice so it is not mistaken for a design change.

5. Check units, the vertical axis and finishes

   Open the export and measure an element with a known dimension. A house can look proportionate while having the wrong scale. Check this before placing it on the map or assessing a walkthrough. If the measurement does not match, review document units and export settings in Rhino.

   Check the vertical axis next: the building should sit and face as expected. Compare the main facade with your reference. An attractive camera angle can hide an accidental rotation. Correct the exchange file and reopen it before saving your final views.

   Check material color and transparency separately. DRB interprets names and may use a texture’s average color; it does not necessarily reproduce Rhino’s render material. If the meeting involves choosing a particular stone or wood, bring its sample too. The model shows where the finish goes, but does not replace its specification.

6. Prepare a review you can repeat

   Save an overall view and views of the area you want to discuss. In the standard 3D view, left-drag orbits, right-drag pans, scrolling zooms toward the cursor as in SketchUp, and middle-mouse dragging looks around from your current position. Practice returning to a saved view so the conversation does not depend on difficult camera moves.

   Rehearse with the same file on the final device. Record its format, revision, units and your observations. When comparing 3DM and OBJ, use the same viewpoints and acceptance criteria. Choose the route that preserves the necessary parts and supports the explanation; neither format is always better.

   An account is optional and project cloud storage is currently disabled. “Mis proyectos” (My projects) stores files in the browser. To share the project, follow the .drb package guide and test the file the client will receive. Keep your Rhino backup. No new Rhino export was performed for this guide; your particular model still needs testing.