Oruva 1.3.1 support
From your first asset to your next scene.
Practical guides for your library, conversion, connectors and the moments when something needs attention.
Make a home for your assets
Create a library, import copies or index folders where they already live.
Set up your library → 02 / CONVERSIONTry your first .max scene
Choose a destination, resolve textures and inspect the imported materials.
Follow the walkthrough → 03 / YOUR SETUPCheck your app and renderer
Find the versions and renderer combinations for your workflow.
Check compatibility →Connect your destination
Install the connector from Oruva.
- Check your combination.
Use the compatibility guide to check your OS, application version and renderer. Install the destination application and renderer first.
- Save your scene, then close the destination.
Close every running instance of that application before installing or updating its connector.
- Open Oruva’s 3D Connectors settings.
Find the application in first-run setup or Preferences, select its detected installation and use its install or update action. Let the operation finish.
- Reopen the destination and check its status.
Wait for the application and renderer to finish loading. Start a fresh scene, then send a single asset from Oruva.
Texture recovery
Resolve missing files before you send.
- Keep the asset package together.
Keep the .max scene, its maps or textures folders and companion files together. A preview image alone does not contain the model or its textures.
- Read the texture check.
Before delivery, review found and missing references. Add the folder containing missing textures to the search locations and check again.
- Check the actual missing filenames.
Confirm that the files exist and the drive or network location is available. If the package never included them, obtain them from the asset creator.
- Review the scene after delivery.
Inspect a material and its bitmap paths in your destination. After correcting source locations, send into a fresh scene again, or use the destination’s relink tools for an existing import.
Found textures and supported materials are separate checks. A procedural or shader feature may still need an approximation even when every bitmap has been found.
Troubleshooting
Get back to your work.
Oruva will not start
Note the exact startup message. Use Try Again if recovery offers it. If it still fails, email your Oruva version, OS, the message and a screenshot to hello@oruva.app. If Preferences opens, save a diagnostics bundle. You can contact support even if the app cannot open.
The destination or renderer is unavailable
Check the version guide, then confirm that the renderer is installed and available inside the destination application. Recheck the connector, reopen the destination after any update and wait for it to finish loading. A listed renderer still needs a matching, working installation.
A send is stuck or asks me to retry
Check whether the destination is still importing or showing a dialog. Follow Oruva’s status and retry action; avoid starting another send while the first one is still importing. If the same error returns, record it and save diagnostics.
Previews disappeared after I moved files
An indexed library depends on original file locations. Reconnect the drive or restore its path, then rescan. If you intentionally reorganised the originals, use the library’s verify or repair tools and keep a backup before changing library data.
An asset has no preview
Check whether the original is reachable. Some formats and archives do not contain an extractable preview. Open the asset to confirm it is the expected file, or assign a custom thumbnail; a placeholder by itself does not mean the asset is damaged.
The graph imported, but the render looks different
Read the import report for approximations or unsupported nodes. Confirm bitmap paths, then compare lighting, exposure and colour management. Different renderers may express the same shader differently. Send support your source and destination renderer versions, warnings and comparison images; here is what to inspect.
Search & local AI
Start with the library. Add AI when you need it.
AI is optional. Start with a small folder and confirm its previews appear before enabling captioning, semantic search or visual search.
Open the relevant AI settings and follow Oruva’s hardware and disk-space guidance. Runtimes and models can be large; let downloads and setup finish before starting a library-wide job.
If setup fails, note the model, exact error and available disk space. CPU and GPU performance differ, so begin with the suggested model for your machine.
Local processing keeps your library on your computer. Account, licensing and download services use a connection; external search can send an image to a provider when you choose that action. See the privacy policy.
Extend Oruva
Manage plugins in one place.
Open the Plugin Center to discover, install and manage plugins. Review requested access when installing or when an update changes permissions. Use the Update action to install an available update.
Accounts & purchase
Clear terms before you commit.
An eligible new account receives a 14-day trial with five protected scene conversions. No payment card is required.
A personal license is for one named user’s workstation and laptop, with twelve months of eligible updates. It remains perpetual for eligible versions; protected conversion still relies on valid authorization.
See the pricing page for launch prices, checkout availability and optional update renewal terms.
Paid licenses provide offline conversion passes for up to 30 days for individuals and 90 days for studio seats, with an online renewal.
A useful support report
Give us the details that help reproduce it.
- Open Preferences → Diagnostics.
Choose Run diagnostics, then Save diagnostics bundle…. Report and log export actions are also available.
- Describe the smallest repeatable case.
Include Oruva, OS, application and renderer versions, the action you took, what you expected and the exact error. Add the failed send’s time and a screenshot when useful.
- Email support with your report.
Save the bundle locally, then attach it yourself. Exporting does not send it automatically. Share asset files only when you have permission to share them.
Talk to us
Help is one email away.
hello@oruva.appFor installation, compatibility, licensing or a scene that needs a closer look. Start with your app version and a short description of the problem.