Blendigo (for Blender 2.58) 3.0.14.0

[dougal2]

3.0.14.0

DOWNLOADS

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

NOTE: This exporter REQUIRES Blender version 2.58a

Changes in this release:

* Removed old ray_origin_nudge_distance
* Re-write default "/tmp\" output location on windows to point to real temp directory
* Improved error reporting; should now show up in info header rather than console only
* Allow setting custom scene export name in Output Panel:
-- "/path/to/export" will be treated as directory, "<BlendFile>.<SceneName>.<FrameNumber>.igs" will be created there
-- "/path/to/file.igs" will use exact filename
-- "/path/to/file-####.igs" will replace # marks with formatted frame number
* Change default splat filter to fastbox
* Skip exporting meshes with no faces or verts
* Fix support for external PIGM and IGM materials:
-- Only first .igm file in PIGM will be used
-- Only last material definition in .igm will be used
-- Selected material found in file will be displayed in material editor panel
* Changed release .zip layout so that it can be used with blender's "Install Addon" button in User Preferences

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.

[FakeShamus]

works great so far. it's still not finding the camera response curves (presets) under tonemapping, but I do like the option of selecting the camera file directly. maybe the response curve thing is Mac OSX specific? they show up if I add the full path to the response curves folder in the "tonemapping.py" file (replacing the os.path.join... part)

[dougal2]

works great so far. it's still not finding the camera response curves (presets) under tonemapping, but I do like the option of selecting the camera file directly. maybe the response curve thing is Mac OSX specific? they show up if I add the full path to the response curves folder in the "tonemapping.py" file (replacing the os.path.join... part)

nice work-around
the reason it's not automatic at the minute is because on OSX, Indigo is not guaranteed to be in any particular location. probably in the future I can use the location set in the render settings though.

[solarray]

Thanks!

Sorry if still known: When AD-Type is set to image or circular (aperture diffraction) you will get an error in indigo. The error will also change about something to 'path' when path was set to absolue.

[dougal2]

Thanks!

Sorry if still known: When AD-Type is set to image or circular (aperture diffraction) you will get an error in indigo. The error will also change about something to 'path' when path was set to absolue.

OK, thanks, I'll look into it.

[dag]

Doesn't look like relative paths get exported correctly.
Output is set to C:\Users\Dag\AppData\Local\Temp
As IGM I use C:\Users\Dag\Documents\3D\Tests\glass.igm
That exports as ../../Documents/3D/Tests/glass.igm which is one folder too low.
If I browse for IGM in blender with relative paths enabled, //..\..\3D\Tests\glass.igm is entered.
If I manually enter //..\..\..\3D\Tests\glass.igm, which is correct, it says invalid file path in the name field.

It's the same with textures. They export correctly in 3.0.10.1.

[Alain]

Yes same texturepath error here.

I guess dougal2 will fix it ASAP.

How do you test new releases ?


Kind regards
Alain

[dougal2]

What's this?!!

untitled.Scene.00001.png (50.84 KiB) Viewed 23046 times

(update coming soon)

[CTZn]

Pacman 2011 ?

[dougal2]

[StompinTom]

What's this?!!

untitled.Scene.00001.png

(update coming soon)

Oooooh shit! Moving things are back!

[Borgleader]

While trying to export my scene I'm getting this:

Error: 'bpy_pro_collection[key]: "" not found'

Blender 2.58a (x64), Win7 x64, Blendigo 3.0.14

[kilbee]

While trying to export my scene I'm getting this:

Error: 'bpy_pro_collection[key]: "" not found'

Blender 2.58a (x64), Win7 x64, Blendigo 3.0.14

i'm experiencing the very same issue. it occures when i apply diffuse/texture material to my model and try to render scene.

Code: Select all

[Indigo 2011-Aug-08 10:59:54] Mesh Export: Cube.006
Info: Export render settings
Info: Export camera
Info: Export tonemapping
Info: Export environment
Info: Building meshes
Error: 'bpy_prop_collection[key]: key "" not found'

[Headroom]

On the "bpy_collection" issue. Some "object" is missing it's name and I'd suspect a texture.

All other things (Objects, Meshes, Materials) have a name assigned by default.
However, assume you have created a material and texture (type : image) channel for that material. In the Indigo specific material panel you need to specify the texture to be used for a Indigo material slot, e,g, Material Color or Bump etc.

Then you decide to rename the texture. You have to reassign the texture to the Indigo material slot.

If you went directly from renaming the texture to the render panel you'll get exactly that error.

Then you decide to reassign the texture and try to render the thing again and you'll get the same error because you choose an Image texture but forgot to actually load an image

[dougal2]

Headroom is correct. Whilst the exporter can't prevent you from setting up textures incorrectly, the next release will give you a more meaningful error message instead.