Indigo Renderer Forum

3.2.0.0

DOWNLOADS

ALL PLATFORMS: http://www.indigorenderer.com/dist/expo ... .2.0.0.zip

NOTE: This exporter REQUIRES Blender version 2.60

Changes in this release:

* add support for original/simulated/extra-atmospheric sunsky modes
* implemented external igmesh proxying
* add exit portal + subdivision options to curve objects
* try utf-8/latin-1/ascii decoding of external igm files in that order of preference
* support export of CURVE objects by mesh tesselation
* correctly skip export of disabled light layers
* fix light layer indexing
* add precedence value to medium elements
* prevent stdout deadlock when using wait_for_process
* Add indigo version check; prevents launching Indigo if version doesn't match Blendigo version, however scene will still be exported OK.
* fix (relative) path check for exr in check_lights
* Add networking options
* Fix UV export for trianglemeshses using igmesh_stream
* Switch mesh export back to igmesh_stream

MANUAL INSTALLATION

Unzip the archive. Move the extracted indigo folder into your Blender addons folder.
You should end up with <blender scripts>/addons/indigo/

Run Blender 2.5, go into User Preferences/Addons, and find the Render section. Locate the Blendigo entry
and enable the addon by clicking the little checkbox on the right.

INSTALLATION VIA BLENDER

Run Blender 2.5, go into User Preferences/Addons. Click the "Install Addon" button and choose the blendigo-2.5-3.2.0.0.zip file. The addon will be installed and shown to you, ready for activation.

This method _should_ automatically replace any previous version. You can easily check the installed version in the Addons panel. After upgrading/replacing I would strongly recommend restarting blender.

HINTS

Save your User Settings now to make Blendigo activate every time you start Blender 2.5.

Non-windows users will have to also fill in the "Path to Indigo" setting in the "Indigo Render Engine Settings"
panel. (Windows does this automatically from the information provided by the installer). Note that you should
specify the actual Indigo binary file for this setting.

YOUR FEEDBACK IS ALWAYS APPRECIATED

As with the current efforts to get Indigo 3.0 as complete and user-friendly as possible,
please please keep reporting any issues you find with Blendigo - it is your feedback as
users and artists alone that push Blendigo forward into being the software that works for you.

Hi Doug,
did you add support for the new sky model?
example code:

OnoSendai wrote:Hi Doug,
did you add support for the new sky model?
example code:

Code: Select all

<skylight>
		<sundir>1 1 0.1</sundir>
		<turbidity>2</turbidity>

		<sun_layer>0</sun_layer>
		<sky_layer>1</sky_layer>

    <model>captured-simulation</model>
	</skylight>

Sure can, but should this be user-selectable? On or off by default?

Yes, I think it should be user-selectable.
Maybe a combo box, with 'original' and 'captured simulation' as options?

Not sure what the default should be.

Also take notice that the turbidity value must be present with the captured simulation even though it does not affect the render.

Not sure either what the default should be, my first test using a topdown view was quite confusing due to the black bottom half giving the sensation of an environment contributing, but not showing off. The dumb test scene was in cause certainly.

Hi and thanks for blendigo update !

Just installed and got the same problem as with 3.0.14.1 - smooth shading bug as I've been advised in other thread.

That doesn't happen with blendigo 3.0.14.0

screenshot to illustrate (blender 2.60, indigo 3.2.0.0, blendigo 3.2.0.0)

No light sources available when only using envmap.
Mesh export is now 4 seconds slower.
Skylight object has no attribute 'scene' when using sun & sky with light layers.
obstacle_map is missing image and path tags in igs.

When there's no mesh deformation, would be nice to export only one time mesh for animation rendering. Maybe it can be an option at export? (Actualy I've a folder of 5.7 Go for 200 frame! A bit heavy to backup .igs)

haluperido wrote:Hi and thanks for blendigo update !

Just installed and got the same problem as with 3.0.14.1 - smooth shading bug as I've been advised in other thread.

That doesn't happen with blendigo 3.0.14.0

screenshot to illustrate (blender 2.60, indigo 3.2.0.0, blendigo 3.2.0.0)

same here

Use the mesh proxy option.

Select the object.
File > export > igmesh.
Go to properties panel > object data > check proxy box > browse to exported igmesh.
Animate!

dag wrote:Use the mesh proxy option.

Select the object.
File > export > igmesh.
Go to properties panel > object data > check proxy box > browse to exported igmesh.
Animate!

Sorry, don't know how to browse to exported igmesh? what do you mean by "proxy box"? do you have screenshot?

thx

Click checkbox on the bottom and enter path to igmesh.

Great, thx

Doug, this is great!

Awesome to have .igmesh linking. There are a couple of bugs with material linking with it, though. I've exported a high-poly model as an .igmesh, then I'm using a low-poly version as a stand-in. Both objects have multiple materials, however there seems to be some trouble with material definitions. Going to test it a bit more, but it doesn't seem to export the materials from the stand-in/proxy, so that when it looks for them when linking the .igmesh, it whines that it can't find them.

I think when the kinks are worked out, this will be an incredible time-saver!

Also, the exporting process still seems suspiciously slow, as if it's still exporting a bunch of geometry...

26.415 seconds with a proxy attached to a low-poly object.
2.590 seconds with only the low-poly object.
35.941 seconds with only the high-poly object (no linking).

Seems a little strange, as I would expect the exporting of the proxy object to be just as fast, or even faster, than exporting the low-poly stand-in since it's just linking an external file...

Also, the old problem of Indigo giving 'Error while building scene: ModelLoadingStremHandlerExcep: Triangle material_index is out of bounds. (material index=4).' is still there when you have an unused material attached to an object.

StompinTom wrote:Also, the exporting process still seems suspiciously slow, as if it's still exporting a bunch of geometry...

26.415 seconds with a proxy attached to a low-poly object.
2.590 seconds with only the low-poly object.
35.941 seconds with only the high-poly object (no linking).

Seems a little strange, as I would expect the exporting of the proxy object to be just as fast, or even faster, than exporting the low-poly stand-in since it's just linking an external file...

Also, the old problem of Indigo giving 'Error while building scene: ModelLoadingStremHandlerExcep: Triangle material_index is out of bounds. (material index=4).' is still there when you have an unused material attached to an object.

The apparent slow down when using a proxy is that Blendigo is actually loading the high-res igmesh in order to try and discover its material assignments. As you've also found, this method seems to not work properly yet anyway - so I'll have another look at it for the next release.