Iray Programmer's Manual

Preface
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
- Own canvas class
- Asynchronous rendering
- Multiple render contexts
Iray Photoreal
- Introduction
- System requirements
- Limitations
- Matte objects and matte lights
- Refractive objects and IOR handling
- Progressive rendering
- Caustic sampler
- Architectural sampler
- Light portals
- Rendering options
- Mixed mode rendering and load balancing
- Timeout prevention
- Integrated noise reduction
- Integrated bloom
Iray Interactive
- Introduction
- System requirements
- Limitations
- Progressive rendering
- Lighting
- Rendering options
- Path space filtering
- Output format
- Global performance settings
- Comparison with Iray Photoreal
Iray Realtime
- 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
- Depth of field
- 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
- Result canvas names
- Light path expression grammar
Bibliography

Restrictions

Iray Bridge has the following known restrictions:

Scopes: Currently, there is no support for scopes. This means that the client needs to select a single scope and make sure all transactions passed to Iray Bridge, directly through the API or indirectly by rendering with one of the cloud renderers, are created in that scope. All the incremental changes sent to the server will be replicated in a single scope on the server. The server will use different scopes for different users, so the server can handle multiple users without them interfering with each other. See mi::neuraylib::IScope for more information about scopes.
Cache: The server side disk cache currently does not support removal of data. This means that the disk cache will grow indefinitely when new data is added to it. It can however be completely removed when not being used by simply removing the files cache.db and cache.dat that are created in the configured disk cache folder.
Canvases: The cloud render contexts do not support multi-layered canvases. Only layer 0 is rendered.
RGBA: When using the H.264 video format, canvases must use pixel type RGBA only.
H.264: There is no H.264 software decoder fallback. An NVIDIA GPU that supports H.264 hardware decoding is required.