Iray Programmer's Manual

Preface
getting-started | Getting started
- Release overview
- Example programs
- How to compile a program
- How to run a program
- Starting and shutting down the Iray API
- A first image
Library design
- API modules
- Shared library
- Naming conventions
- Include files
- Include file compile-time configuration
- Main API access point
- Version numbers and compatibility
- Interfaces
- Reference counting
- Handle class
- Resources
- Strings
- Error handling
- Database, transactions and scopes
  - Transactions
  - Database scopes
- Runtime configuration
Rendering
- Rendering overview
- Rendering and canvases
- Render mode selection
- Progressive rendering of a scene
- Instancing
- Own canvas class
- Asynchronous rendering
- Multiple render contexts
Iray Photoreal
- photoreal-introduction | Introduction
- System requirements
- Limitations
- Matte objects and matte lights
- Refractive objects and IOR handling
- Progressive rendering
- Caustic sampler
- Architectural sampler
- Light portals
- photoreal-options | Rendering options
- Mixed mode rendering and load balancing
- Timeout prevention
- Integrated noise reduction
Iray Interactive
- interactive-introduction | Introduction
- System requirements
- Limitations
- Progressive rendering
- Lighting
- Rendering options
- Path space filtering
- Output format
- Global performance settings
- Comparison with Iray Photoreal
Iray Realtime
- realtime-introduction | Introduction
- System requirements
- Limitations
- Rendering options
Iray Blend
- Introduction
- Rendering options
Scene database
- Overview of the scene database elements
- Creating a scene programmatically
Geometry
- Creating triangle meshes
- Creating polygon meshes
- Creating on-demand meshes
- Creating subdivision surfaces
- Creating freeform surfaces
Materials
- Material Definition Language
- Measured materials
- Editing and creating materials
Decals
Sources of light
- Emission distribution functions
- Light distribution from scene elements
Environment dome and implicit groundplane
- Environment function
- Environment dome
- Implicit groundplane
Camera
- Tonemapping
  - Photographic tonemapper
  - Custom tonemapper
- Bloom filter
- Lens
- Virtual backplate
- Motion blur
Physically plausible scene setup
- Recommendations for geometry preparation
- Recommendations for lights
  - Using photometric lights
  - Using environment and sunlight
- Recommendations for materials
- Recommendations for cameras
Networking
- Networking overview
- Networking modes
- Iray Bridge
Delivering an image from server-based rendering
- Running an HTTP server
- RTMP server
- RTMP client
- Running an RTMP and HTTP server with mouse interaction
Customization
- Extending the database with user-defined classes
- Extending neuray with plugins
- Extending supported file formats with plugins
Appendix
- Supported file formats and URI schemes
- Canvas names in render targets
- Light path expressions
Bibliography

The mi_exporter plugin

General

Use the mi_exporter plugin to enable the export of a scene to the NVIDIA Iray .mi file format. To enable the plugin it must be loaded in neuray using either the mi::neuraylib::IPlugin_configuration::load_plugin_library() or the mi::neuraylib::IPlugin_configuration::load_plugins_from_directory() method.

Configuration

In addition to the standard options described for mi::neuraylib::IExporter::export_elements() and mi::neuraylib::IExporter::export_scene() the mi_exporter plugin has additional configuration options:

mi_write_binary_vectors_limit of type mi::IUint32. Geometric objects with vectors larger than this size are exported in a binary format. It saves space and speeds up both export and import, while making the data humanly unreadable.
mi_mdl_root of type mi::IString. When exporting memory-based MDL modules, the given value defines the location of the root directory to which the MDL data is exported.