I've been messing around with the new renderer and I love the results. I've run into some issues and had some questions along the way. Maybe we can centralize our findings here. I'll keep the first couple posts updated with what we've discovered.

Post any issues you run into and also any solutions you discover.

Differences from iClone renderer
Indigo renderer will render either a single image or a sequence of images. It will not output a video file. You have to open the image sequence in a video editor, add sound and output the video from that.

The Indigo renderer produces much better results than the iClone renderer due to the way it simulates light when capturing the scene. It also takes a lot longer.

Indigo Watermark
The first time I started Indigo renderer, and put in my serial number, I still had the watermarks on the screen. The second time I started it, the watermarks were gone.

Changing Render Settings
If you've started your render and want to change a setting, you must stop the render, use the pull-down menu on the right-hand side under "Render Settings" to choose the category, then make the change and start your render from scratch.

Which Tracing Method?
“GPU Acceleration” is going to give you the fastest results, but it may have difficulty with some lighting aspects. “Bidirectional Path Tracing” is the best all-around choice. If you have glass or water in your scene, then you may want to choose an option with MLT. Every render mode should eventually get your scene to an acceptable point, but it’s just a matter of choosing the one that will get there fastest. Always try a single image from your scene to see how it renders and determine what render mode you should use for your multi-frame output.

Spotlights
Spotlights will render the light fixture on-screen with Indigo, even though the light fixture is invisible in iClone. Point lights do not render because there is no casing around them. To make an on-camera light, you have to use point lights. Trying to figure out if flashlights are possible without an iClone spotlight.

Save IGI
According to the Indigo manual, this save information that allows you to stop and resume renders. The files are very large, however, and iClone will create one for every frame in your render.
"The Indigo Image stores all the information about a render in progress, so if the same scene is loaded again later (even after the rendering has been stopped and Indigo closed), the current rendering state can be fully restored using the IGI file."

White dots
The "White Dots" will disappear when the "Supersampling factor" (new setting in iClone 6.01) is set to a value higher than the default 2. Anything higher than 5 gives good results, but can increase the rendering time depending on the image content. - wires & animagic

If there are still white dots, they do go away as the rendering continues. You can get quicker results, though, by using “Bidirectional Path Tracing with MLT”. Also, “Aperture Diffraction” will accentuate these white spots if you have it enabled.

Fog (iClone Feature)
iClone Fog settings have no results in Indigo. It’s possible other items in the Visual panel also have no effect.

Light
Light in Indigo works a lot differently than in iClone. If your iClone scene is bright, then it’ll be even brighter in Indigo. If your scene is dark, it will be even darker. You have to do some renders to test your lighting.

Black render
Sometimes it takes a few image updates before you see anything other than a black image on your render. Give it a little time. Also, make sure you camera is not clipping a wall. You can view your scene normally in iClone, but the camera in the renderer is just a little different. If its lens is inside a wall, you won’t be seeing the same shot.

Camera in iClone vs Indigo
Camera Focal Length will be a little different when rendered in Indigo. For instance, my 50mm focal length was the equivalent of 52mm (in iClone) when rendered. Be sure to compensate if the edges of your frame are important.

Scene complexity
More complex scenes (lot of 3D models) will take a while to build in Indigo before the rendering starts. It’s normal.

White Point (Indigo setting)
I think the white point defaults to B. However, if you want to use a different white point, here is a list of common ones: http://en.wikipedia.org/wiki/Standard_illuminant#White_points_of_standard_illuminants

Image Completion (iClone setting)
When outputting a range of frames you can select how long Indigo spends on each image. Some are fine with 200 sample per pixel, some take 1000 or more. You need to render a test image to find the proper value for your scene. Just export a single frame and let it run. Note how long or how many samples per pixel until the image looks good (that data is at the bottom of Indigo when rendering).

Editing .ig_ files
The .igq and .igs files are in XML format. You can edit them with any text editor. This allows you to change the render settings in the configuration files rather than the renderer.

.igq
IGQ files are the queue of .igs files that you are rendering. This is a quick way to change the render time on all the image frames in the queue.

halt_spp = the amount of "samples per pixel" of the frame. This is if you want the render to finish at a certain quality.
halt_time = the amount of time to spend on each frame. This is if you want the render to finish in a certain amount of time.

.igs
There is a .igs file for each frame of your render. Changing settings for all of them isn't practical without some sort of automation. Someone (justaviking, maybe?) suggested "ecobyte replace text". It can be downloaded here: http://www.ecobyte.com/replacetext/

- Keith