Description

Methods to import and to export scene data and MDL modules. All import and export methods use a common naming convention to identify files based on URIs as defined in [RFC3986]. Currently only the URI scheme file is supported. An empty URI scheme defaults to the file scheme. URI authorities are not supported, except for the empty URI authority, which is needed in some cases to resolve ambiguities (see below).

Within the file scheme relative and absolute URI paths are supported (see Section 4 in [RFC3986]). URI paths are mapped to filenames as follows:

• On Linux and Mac OS, URI paths are treated as filenames paths without any translation.

• On Windows, slashes in relative URI paths are replaced by backslashes to obtain the filename.

• On Windows, absolute URI paths are mapped to filenames according to the following table.

In addition, the following variable can be used in URI paths, which are expanded by .

• "${shader}"

  The URI path may start with the string "${shader}" followed by a slash and a relative path, in which case the relative path is resolved relative to the search path for MDL modules. If several directories for MDL modules have been configured, they are searched in turn. This variable is only supported for import methods, not for export methods.

See also:

The API components mi::neuraylib::IImport_api and mi::neuraylib::IExport_api offer methods to convert between filenames and URIs. The Iray Programmer's Manual describes [:ipmlink scene_file_formats scene file formats] that Iray can import.