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

Image file formats

neuray has no built-in support for reading and writing image data in different file formats. This support is solely provided by image plugins that can be dynamically loaded.

The following image plugins are currently available:

freeimage: The FreeImage library offers support for various image formats, including DDS, EXR, GIF, HDR, JPG, PNG, and TIFF. Note that DDS and GIF (and possibly other formats not mentioned above) support only the import, but not the export of images. Note that the gamma value stored in PNG files is not taken into account.
dds: The DDS (DirectDraw Surface) image format was established by Microsoft. While the freeimage plugin provides support for 2D DDS textures, the use of this plugin is recommended to add support for 3D textures, cubemaps, and mipmaps. It also supports the export of images.
ct: The CT format is a lossless image format created by mental images.

Your neuray installation can be extended with image plugins that support other file formats.

Every image plugin needs to be loaded explicitly in neuray using the mi::neuraylib::IPlugin_configuration::load_plugin_library() or mi::neuraylib::IPlugin_configuration::load_plugins_from_directory() methods. The latter allows you to offer automatic plugin loading from a specified directory.