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

Shared library

The Iray API is a C++ API. Its implementation is provided to you in the neuray library, which is a dynamic library (a.k.a. shared library or DLL), named libneuray, with the usual platform specific file extension.

The main benefits of the dynamic library for you are:

You can link the neuray library to your application or dynamically load it on demand at runtime without requiring to statically link an interface library to the application. This can improve application startup time.
The Iray API follows conventional modern C++ library design principles for component software to achieve binary compatibility and future extensibility across shared library boundaries. The neuray library relies therefore only on the stable C ABI of a platform and you can use a different compiler for the application then the compiler used for the neuray library.
Iray API and ABI versioning allows the safe upgrade of the neuray shared library. For details about when a recompilation is necessary and when not. see Version numbers and compatibility.

Note: The neuray system itself depends on other shared libraries. Several of those are also only loaded on demand as plugins when needed. See mi::neuraylib::IPlugin_configuration for details and A first image for an example.