OruvaDownload ↗

Getting started with Oruva 1.3.1

One asset. Your first native scene.

Set up a small library, send a .max asset to your application, then inspect the material graph and save the result.

Have these ready.

  • A representative asset you may useA .max scene or its original archive, companion textures and a preview image if available.
  • Your destination applicationChoose a version and renderer covered by the compatibility guide.
  • Oruva and its connectorUse a matching app/connector combination and sign in to your Oruva account.
  • A fresh destination sceneSave existing work first, then use an empty scene to make the result easy to inspect.

Use an asset you own or are licensed to use. The example recordings show real imports; their source .max files are not included as a downloadable sample pack.

Step 01

Create your first library.

In Oruva’s Library menu, choose Create Library… and select a location with enough free space. Give it a name you recognise. You can start empty, or bring in a collection straight away.

Start with a small folder of representative assets. Once that folder looks right, add the larger collection.

A library is where Oruva keeps its catalog, your pictures’ thumbnails, and the connection between each picture and its 3D model.

Oruva's Add to your library window asking where the pictures should live: copy into the library, or keep in their folders
The first question when you add a folder: copy the pictures into the library, or keep them where they are.

Step 02

Add your folder. Oruva connects the models.

Keep everything together

Copy into the library

Makes a separate copy of each picture inside your library. Choose this when you want the library to be self-contained. Keep enough disk space for both the originals and the copies.

Use your existing folders

Keep in their folders

Uses the pictures where they already live and saves disk space. Choose this for an existing organised collection. Keep its drive and paths available; moving, renaming or deleting the originals breaks their connection to Oruva.

Choose Add folder (or Add files) and point Oruva at your collection: pictures, 3D models, or a mix of both, in one folder or several. Short steps show what was found and ask only what needs a decision. For the best result, give a model and its pictures the same name — riolo.zip, riolo.jpg, and extra views riolo-1.jpg, riolo-2.jpg, riolo-3.jpg. Oruva connects those instantly and saves the connection in your library. Where names differ, it also uses files that were downloaded together. Oruva never renames, moves or changes your files. Model files can be ZIP, RAR, 7Z or MAX.

Anything Oruva could not connect is listed under Missing Models. Open Tools → Model Matcher to see the closest model for each picture, choose Connect all found, and settle the rest one at a time. You can also right-click any picture and choose Connect to a 3D model….

The Found step of Add to your library: 10 pictures, 6 models, and a row of thumbnails already connected
What Oruva found in the folder, and how many pictures it already connected to their models.
Model Matcher with riolo.jpg, riolo-1.jpg and riolo-2.jpg connected to riolo.zip
Model Matcher lists what is left, with the closest model already selected. Same names are found instantly.
Oruva library in the dark theme after adding a folder: thumbnails with their model badge, and Missing Models and Model Matcher in the sidebar
Your library after adding the folder. A small badge marks pictures that are connected to their model; Missing Models in the sidebar counts the ones that are not.

Step 03

Connect your application.

  1. Install your destination application and renderer. Confirm they start normally.
  2. Save your work and close every instance of the destination.
  3. In Oruva’s first-run setup or Preferences, open 3D Connectors and install the connector for the detected application.
  4. Reopen the destination, wait for it to finish loading and begin with a fresh scene.

If you have just updated Oruva, check for a matching connector update too. Detailed connector help.

Step 04

Send one scene.

  1. Choose the asset.

    Pick a picture that is connected to its 3D model. Right-click it and choose Send to, then your application and renderer. If the picture has no model yet, Oruva asks you to pick it once and remembers the connection.

  2. Select the intended source.

    If the archive contains multiple scenes or renderer variants, choose the one you want. Start with a V-Ray or Corona source represented in the compatibility guide.

  3. Resolve the textures.

    Review found and missing references. Add the correct texture folder when prompted and recheck before delivery. Missing-texture help.

  4. Let delivery finish.

    Keep Oruva and the destination open. Watch the status and wait until importing finishes before starting another send.

Working from a preview and archive?

The 3D Generator brings those model sources together for reuse. For this first check, use one asset with its original package so it is easy to recognise the scene and materials.

Step 05

Look inside the material.

Open the imported material in your destination’s material or node editor. Check its texture connections, layers and bump or normal inputs, then run a small native render.

Real imported V-Ray graph with linked colour-correction, combine-colour, V-Ray material and blend nodes
Detail from a real imported V-Ray graph. The recordings show the material after import, including its native nodes. Select the image to inspect it at full size.
  • Scene structureCheck scale, placement and the parts you expect to remain editable.
  • Textures and materialsCheck the main surfaces and confirm bitmap paths resolve.
  • Import reportRead approximations or unsupported-feature notices before relying on the result.
  • A small renderReview lighting, exposure and colour management alongside the materials.

Step 06

Save. Reopen. Make it yours.

Save the native scene under a new name in your destination. Use its asset-collection or texture-management tools if the project needs to move to another machine.

Reopen the saved scene and check the important materials once more. Then start editing, arranging and lighting the asset in your own project.

Something did not match the guide?

Choose Save support report in Preferences → Diagnostics, or on the startup screen. Email support@oruva.app with the record ID and a short description of the step that failed. You can attach the saved report; it is encrypted so only Oruva support can read it. Nothing is uploaded automatically.