Indigo Renderer Forum

3.0.14.1

DOWNLOADS

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

NOTE: This exporter REQUIRES Blender version 2.58a

Changes in this release:

* Fixed path handling fubar
* CRF presets should now be found on Linux/OSX if you have set the "Path to indigo" setting
* Add support for basic motion blur; Currently only works on objects which are directly keyframed, not moving due to parent transforms
* Fixed circular aperture
* Allow relative path to indigo exe
* Hide emission power and gain if using emission_scale
* Provide better error messages if a texture/image lookup fails (incorrect or edited assignment)
* Simplified render options using dropdowns with presets and "custom" option for people who like checkboxes
* Fix ISL export from Text block (prevent certain characters being XML encoded)
* Fix visibility rules for dupli/particle system objects
* Allow turning off particles via switch in modifier stack
* Fixed pre-export lights check in material emission settings
* Added support for using a 2nd scene as a "Background Set"
* Added support for textured emission
* Reverted to previous UV-set chooser UI for texture setup
* Fixed exporting meshes with mutliple UV sets

WARNING
I had to make a few changes to how data is stored in this release, some old scenes may need emitters and textures setting up again in places. I apologise if this causes any inconvenience, but it was necessary in order to make progress with some of the features.

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.0.14.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.

I am trying to render a scene that has rendered fine with a previous Blendigo/insdigo 3.xx version.

I am getting this error:
bpy_prop_array[index]: index 3 out of range

It does show up in the status line in Blender as well as in the System Console.

I have reassigned a simple Clay material (default diffuse) to everything and still get this message. I went into all meshes that had more than one material assigned, removed them and reassigned the clay material to the entire mesh.

No luck!

The scene was lit with an .exr and Blendigo complained about the lack of a light source. I changed to environment and since then have persistently gotten the bpy_prop... message.

Also every 2-3 times I started the export process Blender crashed violently.

Headroom wrote:I am trying to render a scene that has rendered fine with a previous Blendigo/insdigo 3.xx version.

I am getting this error:
bpy_prop_array[index]: index 3 out of range

It does show up in the status line in Blender as well as in the System Console.

I have reassigned a simple Clay material (default diffuse) to everything and still get this message. I went into all meshes that had more than one material assigned, removed them and reassigned the clay material to the entire mesh.

No luck!

The scene was lit with an .exr and Blendigo complained about the lack of a light source. I changed to environment and since then have persistently gotten the bpy_prop... message.

Also every 2-3 times I started the export process Blender crashed violently.

That's quite surprising - I've constructed a set of tests to run before release and none of them crashed like that.

EDIT: just fixed the issue, re-packaged, re-uploaded and added myself another test case. Please re-download and re-install. Sorry for the balls-up

Great! I'll check it out tomorrow when I get back in the office.

Thanks!

Nope!

It still complains "no light source present" despite the fact that I have an .exr assigned, so I changed to the default white background for lighting. I cannot recreate the error with a fresh scene though.

I started deleting objects and finally must have deleted the one that created the elusive bpy-error. Then I went to the initial scene and deleted only that one then received the bpy-error again.

Still frequently crashes Blender (that may be machine oriented though).

I'll continue the tests!

Edit:

I spoke too soon! I tried to render the default cube with the same .exr in environment lighting and it also complained "no light source present"

Edit 2: Went back to 3.0.10.1 and seems to work fine.

Did you heed my warning in the top post about setting up emitters and textures/UVs again for this release?

If problems persist, sending me the actual .blend file would be massively helpful.

Envmap needs absolute path now? Doesn't work with relative.
Crashes on a scene that was saved with previous version because of subsurf modifier on some objects. Try removing them.

I hope I did

Am I correct that only objects get exported that are in the active layers ?

The thing is an animation where I look at an outdoor situation (a manhole) and show how the manhole cover and a security device are removed. Then I move underground into the manhole and show what happens when the security device is triggered.

During the animation I move all parts that can't be seen and don't contribute otherwise to a different layer.

The first thing I did to see if UV's and textures would be a problem was to assign a simple diffuse clay materials to everything. I assumed that should take care of all UV and texture related issues. Still got the bpy-error.
Then for the outdoor part I actually deleted all mesh objects and still got the bpy-error.

Also the outdoor part does not have any mesh emitters but is only lit by the .exr.

Could you tell me exactly what the bpy-error is ?

No unfortunately not. In order to recreate it reinstalled this newest Blendigo and now it always crashed through mesh export.

1. I had an imported STL mesh that was very messy after I had removed doubles (too high threshold). I tried to clean it up but ended up reimporting the STL. and just applied a Egdesplit modifier. That seems to have fixed that issue.

However, it still crashed!

2. As Dag suggested I removed the Subdiv modifier from the only mesh that has one applied and voila it started rendering, alas not environment lit but just white background.

I moved to an earlier part in the animation that has a two other subdivided meshes and sure enough it crashed again. These have first a simple subdivision applied and then a catmull clark after that. I removed only the catmull clark from these two meshes That did the trick! the meshes in question are UV mapped and have image textures applied.

I'll test some more.

Still sometimes crashers when exporting meshes. Just repeatedly loading the file and clicking render image. Sometimes it works and it exports and sometimes it does not.

grr that sounds really frustrating, and it's equally frustrating for me to try and guess what the error is

I'll do some tests with catmull subdiv, but if you can provide me with an STL mesh even, that would give me at least something to start looking at.

Without further detailed info, or example data, I really can't even begin to debug this issue.

Are you using very high levels of subdiv? I can get blender to segfault when using level 5 or 6 on a standard cube

I found one issue: this release uses the 'debugging' mesh exporter - it should be using the faster version which I have found doesn't crash blender.

3.0.14.2 will be released shortly, but I would still like some example data from you guys to test with before I release (if possible).

I'll see what I can do!

So far all my tests have been on my WinXP 64 work computer. Tonight I'll test some of it at home on my iMac and see how that behaves!