Blendigo (for Blender 2.63) 3.4.8.1

[OnoSendai]

Blendigo (for Blender 2.63) 3.4.8.1


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

WINDOWS INSTALLER: http://www.indigorenderer.com/dist/expo ... taller.exe

Changes in this release:

3.4.8.1
-------
* If there is no light in the scene, a white environment light is exported.
* Fixed only first material assigned to object getting its IES profile and emission scale exported.
* Fixed bug with IES paths being incorrect.
* Hopefully fixed bug with motion blur keyframes having wrong rotation.


NOTE: This exporter REQUIRES Blender version 2.63
It also requires Indigo 3.4.7 or newer to be installed.

[Oscar J]

Great, thanks!

[StompinTom]

So far, so good!

Could you add support for ortho camera export and clipping planes?

Clipping planes could perhaps just take position and orientation of an Empty object?

[FakeShamus]

IES paths do seem to be exported correctly now, thanks!

[fbrunell]

Ahhhhh, YES, indeed, motion blur works perfect, many many thanks...

Regarding "Animation" crashing systematically, in case it could help I looked at my event viewer and I get the following error!!!

Faulting application name: blender.exe, version: 2.6.3.0, time stamp: 0x4fab91f1
Faulting module name: nvoglv64.DLL, version: 8.17.13.142, time stamp: 0x4fb2042c
Exception code: 0xc0000005
Fault offset: 0x000000000063473a
Faulting process id: 0x1304
Faulting application start time: 0x01cd9c4cc434bf36
Faulting application path: D:\blender-2.63a-release-windows64\blender.exe
Faulting module path: C:\Windows\system32\nvoglv64.DLL
Report Id: 4c786e1f-0840-11e2-b6a3-f04da23a1b43

[Headroom]

IES path also seems to work on the Mac OSX platform. That was a very quick turn around.
Thanks!

[fbrunell]

Ahhhhh, YES, indeed, motion blur works perfect, many many thanks...

Regarding "Animation" crashing systematically, in case it could help I looked at my event viewer and I get the following error!!!

...

Ok, I tried something Bold today!!!

I formatted my hard drive and reinstalled everything to rule-out any local problems on my system. Here is the sequence I used :

1. Installed Windows 7 (Formating the hard drive prior to make sur I leave nothing out)
2. Installed Windows 7 updates
3. Installed GeForce 670 latest drivers (from ASUS Website)
4. Installed Norton Internet Security
5. Installed Python 3.2 Windows 64bit MSI
6. Installed Visual C Redist 2010 (Which includes 2005, 2008 and 2010 32 & 64 bits packages)
7. Insatlled Blender 2.63a from Blender website
8. Insatlled Indigo 3.4.8 along with Blendigo 3.4.8.1 included package

I was ready to go and full of hopes..

1. Started blender
2. Loaded a scene
3. Tried a single Image render and it worked fine.
4. Tried to render "Animation" from frame 1 to 100 and Blender crashed at frame 48
5. Started blender again tried rendering a single frame and it worked fine
6. Tried to render "Animation" and it gave me the following error message in the console :

[Indigo 2012-Oct-01 21:52:16] 'Mesh' object has no attribute 'faces'

This is strange since I did not save the file I was working on... Why is the reaction not the same?

1. Started blender again
2. Loaded back the same scene
3. Tried a single Image render and it worked fine.

4. Tried to render "Animation" from frame 1 to 50 and it game me the same error message.


Tried with another scene.

1. Started blender
2. Loaded a another scene (PaintPatch1.blend which I send earlier last week)
3. Tried a single Image render and it worked fine.
4. Tried to render "Animation" from frame 1 to 50 and Blender crashed at the first frame.

When Blender crashed the Blender window became pale with the windows crash message in the middle of the screen. This time, I was able to see in the blender console window the following message :

File "C:blender-2.63a-release-windows32\2.63\scripts\addons\indigo\core\__init__.py", line 159, in render
Traceback (most recent call last):

I than tried to create a scene from scratch within Blender 2.63. Created a box and 4 UV sphere.

Simple renders and animation works fine. I than started to add different object, textures, Object with lights, etc. and it continued to work fine.

As soon as I import an object within my scene that comes from my library I get my problems back! Please don't tell me that my entire library is corrupted?

P.S. I did find, up to now, one object that I was able to import without getting the problem!!!

[fbrunell]

Found another bug.

When an object is a child of another object, the parent get motion blurred but not the child!

Edit: it is the same thing for recurcive childs...

[FakeShamus]

a couple tiny things that I've been hoping to see fixed (I've asked about them in the past):

RGB albedo values are exported using a default gamma of 1.0, but that results in washed-out color in the render. with every new Blendigo version I go into 'spectra.py' with my text editor and switch the default RGB gamma to 2.2 which gives me the expected color in relation to the Blender interface. might be helpful to have an option to choose RGB gamma in the Blendigo UI?

the other thing is the missing support for indigo sphere primitives. we used to be able to name an object ".sphere" and it would generate a perfect sphere primitive instead of a mesh. but this doesn't work currently. I have a number of scenes where I would use this if we had it back.

thanks for all the hard work!

[dag]

Simply changing gamma to 2.2 is wrong, as 1.0 gamma matches textures pretty well except in darker colors.
Try looking at the hex color in blender and comparing that with a texture with the same hex number.

Ideally blendigo should convert blender colors and export as 2.2 gamma to match textures 100%.

[CTZn]

Oh bummer. I think that MtI is exporting colors at the declared screen gamma (usually 2.2).

Thank you for pointing out dag, and everyone please remember that I loath texels

[dag]

Well, Maya and Blender may have different color systems.
Blendigo just reads the color currently set in blender and exports as gamma 1.0.

[FakeShamus]

I see what you mean, but here's what I'm talking about (attached images) - this might be due to Blender's color pipeline, but adjusting Blendigo's default gamma setting to 2.2 (within the spectra.py file) get's me much closer to what I'm seeing in the viewport before export. I'm not expecting a perfect match, of course, but the colors in the gamma 1.0 version are just not very close...

[dag]

What kind of tone mapping are you using?
That's not what it looks like to me.

[FakeShamus]

just linear tonemapping.
the background is a marble using an image texture with gamma 2.2 - and that color looks as expected to me.