This is an old revision of the document!
Summary: The Rhino RDK is a collection of tools that extend the Rhino 4.0 application platform with visualization specific capabilities.
Current Version: 4.1d (released 18th October 2010)
Please note that all features of the Rhino 4.0 SDK are included in Rhino 5 by default. You do *not* need to download and install either the plug-in or the SDK for Rhino 5.
Note: The RDK feature set underpins the Brazil for Rhino product, and all of the above features are supported in that product. However, all of these features are available to third party developers to integrate their products into Rhino.
RDK plug-in installer Last update: October 18th, 2010
|The current RDK plug-in installer is complete with online help - accessed directly from the new tools. Look for the new toolbar and additions to the Render menu.|
RDK scripting support Last update: 5th March 2009
RDK SDK Guide Last update: January 26th, 2009
Note: A complete version of this text is part of the SDK download below.
RDK SDK installer Last update: January 26th, 2009
|The RDK is a C++ SDK that integrates with the Rhino 4.0 SDK to add additional renderer specific functionality.|
Note: When developing your RDK-aware render plug-in, you will need the SDK installed on your workstation. The RDK installs into the same folder as the Rhino 4.0 SDK and requires the Rhino SDK to be installed first.
Note: When distributing your plug-in, you will need to include the RDK installer as part of your own plug-in installer. To do this, simply install the RDK plug-in installer into the temp folder, and run it using the /silent command line option.
Note: The SDK installer includes a demonstration project called Marmalade which you will find in the C:\Program Files\Rhino 4.0 SDK\Marmalade folder. This plug-in shows how to set up your paths for header and lib files, and demonstrates many common RDK tasks such as creating custom materials and using the frame buffer.
The material editor, environment editor, and texture palettes interact with the enhanced render content system. All are based on a similar interface with only small functional differences between them.
Access the editors through the Rhino Render menu, the Rendering2 toolbar, or the editor commands.
Lists of materials, environments, and textures are stored in the Rhino document. Each editor displays the relevant render content type as preview thumbnails.
A large button to the left of the editor controls the visibility of the editor side panel which displays a list of common tasks along with the structure of the currently selected material, environment, or texture.
The size of the preview thumbnails area can be adjusted by dragging the handle just below its lowest edge.
Contents display an interface below the preview thumbnails in an area reserved for collapsible UI panels. An addition to the basic UI panels, several additional collapsible panels are provided by Rhino within the same area as the content UI. These include the Texture Summary panel, the Notes panel, the Local Mapping panel, Graph panel and the Adjustment panel. These are described later in the content UI section.
The editor window can be minimized to the caption bar and restored by double clicking on the caption bar.
Each material, environment or texture can have child nodes. The children can be of any content type, but specific child slots will only support specific types. The most common child type is a texture. For example, the Texture child for a Basic Material will only support textures, as will the Background image slot on a Basic Environment.
The standard render window provides a number of features to renderers, including built in support for scripting, cloning, saving to High-Dynamic-Range formats, post effects, zooming and channel display.
Many renderers call the render window the frame buffer. The terms are nearly interchangeable.
An HDR image which provides automatic conversion to a bitmap for non-HDR capable renderers. This allows the Rhino renderer and viewport display to show HDR environments while providing HDR tools to third-party renderer engines.
The HDR texture also provides projection conversion features. Most HDRi files come as Light Probe projection. The Basic Environment requires Spherical (Equirectangular) projection for spherical environments, so the HDR texture defaults to this conversion. However, several other types are supported.
The LDR exposure determines the brightness of the image when converted to a bitmap image. This will not affect the rendering when used by a HDR capable renderer.
HDR multiplier is a simple linear multiplier on all values in the image. This can be used to brighten or dim the image in an HDR capable renderer.
The Save As button can be used to convert the image to a bitmap file. The LDR exposure value is used convert the image during this process.
Azimuth and Altitude values modify the way the image is rotated in space during the projection conversion.
Sun tools, including a docking panel to control the document sun, a sunlight preview within the Rendered viewport, a Sunlight command and a number of other scripting and developer tools make sun angle calculations easier.
Decals are non-repeating textures that are applied to the surface of an object with a given projection. They are an easy-to-use way of attaching single images or similar textures to objects without going through the complexity of the texture mapping process.
Decals are textures that are placed directly on a specified area of one or more objects. Use decals to modify a limited part of an object's color.
Decals consist of a single instance of a texture, rather than being tiled as they are when used in a material.