Indigo Renderer 3.4.7

[Silmä]

To be honest the post-pro diffraction probably shouldn't be so strictly physically based. With diffraction you want to have nice stars on sharp light sources and gentle blooming on highlights, not overall blurring even if it was physically correct.

Some sort of filtering by brightness should do the trick, and shouldn't be too hard to implement (well, what do I know). A slider or maybe even a curve editor to control the point where diffraction kicks in would be absolutely brilliant. That way you might be able to add diffraction to where it really doesn't belong (i.e. shots with larger apertures) and it would be a true post pro option that's not completely determined before a single sample is calculated.

For people liking absolute simulation there's always the physical AD, and you could always use the physically correct settings for the post pro AD too.

[zeitmeister]

Excellent idea,
a strength slider for postpro-AD!

[fused]

AD is not saved to final PNG when Indigo gets closed.

Yeah as I said before: that one is much more complicated to fix.

[suvakas]

AD is not saved to final PNG when Indigo gets closed.

Yeah as I said before: that one is much more complicated to fix.

Oh, I missed it. Sry. =)

Can't you use the same procedure as when you are saving to png using Save Image?
What's so different in saving after closing?

[Headroom]

Trying to use an IES file. I've used this IES file successfully before (a number of Indigo versions back) but have never encountered this problem. Exports fine (Blendigo 3.4.7.1 running on OSX Lion 10.7.4). Indigo 3.7.4 reports:

A problem occurred with the scene:
Error while building scene: Error while loading ies prifiles: IESDataExcep: IESDatumExcep: FileUtilsExcep: Could not open '/Users/Peter/Documents/tmp/IES_Test_Indigo_3_4_7/Scene/00001/../IES data/Solux/174100.ies' for reading: File open failed. (model UID: 11)
Indigo version: Indigo Renderer v3.4.7, OS X 64-bit build.
Exporter: Blendigo 3.4.7.1
Platform: 10.7.4 x86_64 - Darwin Peter-Doerings-iMac-2.local 11.4.0 Darwin Kernel Version 11.4.0: Mon Apr 9 19:32:15 PDT 2012; root:xnu-1699.26.8~1/RELEASE_X86_64 x86_64 i386 - Python 3.2.1 (default, Aug 5 2011, 20:41:36) [GCC 4.2.1 (Apple Inc. build 5666) (dot 3)]
Author: Peter
Description:
Date created: 2012-09-25 22:47:48 GMT
Please contact support@indigorenderer.com if you have any questions.


I've tried to place the IES file in a more "direct" location, i've used different IES files. I've renamed the path in objects.ies. All to no avail.

Am I missing something and if so, what ?

The "model" is about as simple as it can get.

Edit:
Just prepared a parallel test installation with Blender 2.63 and Blendigo 3.2.14.1
Same error occurs with Indigo 3.2.14.

[Headroom]

I could of course select the path to the IES file in Indigo like I can with textures etc. Or so I thought. Just cant find where to do that in the Indigo interface.

Also noticed that some of the naming seems...well....odd. See the attached screenshot

Light_8e3fa64e22.....etc.

Not sure that is intended. Just noticing ;-)

[fused]

I could of course select the path to the IES file in Indigo like I can with textures etc. Or so I thought. Just cant find where to do that in the Indigo interface.

Also noticed that some of the naming seems...well....odd. See the attached screenshot

Light_8e3fa64e22.....etc.

Not sure that is intended. Just noticing

Hi Headroom,

IES and emission scale are both model options in Indigo. IES is currently not exposed in the Indigo UI yet, tho.

[FakeShamus]

Could not open '/Users/Peter/Documents/tmp/IES_Test_Indigo_3_4_7/Scene/00001/../IES data/Solux/174100.ies' for reading: File open failed

I've gotten similar errors in the past and the above clip of your post kind of explains the issue. Try turning off "relative paths" under your Blender file preferences. With that disabled, browse to your iES file and Blendigo should export the full, direct path name instead of one relative to your scene file, like it's trying to do here.

[Pibuz]

Hi guys.
Maybe I'm telling an old speech, but when I try to use sun/sky with any amitter material I always end up setting absurd values for emission scale. I know that a great work has been done (don't know if for Indigo in general or only for sketchup) about the new way lights are handled, but still seems to me quite unconceivable to have all cool world-scale values for everything and then have to set the power of a lamp to 10.000.000lm to see a tiny spot along with a sun system.
Does anybody experience this too or is it just me?

[Oscar J]

Trying to use an IES file. I've used this IES file successfully before (a number of Indigo versions back) but have never encountered this problem. Exports fine (Blendigo 3.4.7.1 running on OSX Lion 10.7.4). Indigo 3.7.4 reports:

A problem occurred with the scene:
Error while building scene: Error while loading ies prifiles: IESDataExcep: IESDatumExcep: FileUtilsExcep: Could not open '/Users/Peter/Documents/tmp/IES_Test_Indigo_3_4_7/Scene/00001/../IES data/Solux/174100.ies' for reading: File open failed. (model UID: 11)
Indigo version: Indigo Renderer v3.4.7, OS X 64-bit build.
Exporter: Blendigo 3.4.7.1
Platform: 10.7.4 x86_64 - Darwin Peter-Doerings-iMac-2.local 11.4.0 Darwin Kernel Version 11.4.0: Mon Apr 9 19:32:15 PDT 2012; root:xnu-1699.26.8~1/RELEASE_X86_64 x86_64 i386 - Python 3.2.1 (default, Aug 5 2011, 20:41:36) [GCC 4.2.1 (Apple Inc. build 5666) (dot 3)]
Author: Peter
Description:
Date created: 2012-09-25 22:47:48 GMT
Please contact support@indigorenderer.com if you have any questions.


I've tried to place the IES file in a more "direct" location, i've used different IES files. I've renamed the path in objects.ies. All to no avail.

Am I missing something and if so, what ?

The "model" is about as simple as it can get.

Edit:
Just prepared a parallel test installation with Blender 2.63 and Blendigo 3.2.14.1
Same error occurs with Indigo 3.2.14.

Do you remember my thread, where I reported the same problem?

http://www.indigorenderer.com/forum/vie ... =5&t=11580

I am still having this extremely irritating problem.
The only solution that works for me is to save the IGS so that you can find it in Finder. Then open it with Text Edit, and change the path to where the IES is actually located. You can use cmd-F (find) and type "ies" to find the incorrect paths and correct them. If you have more than one IES light, however, this can become a very long and tedious thing to do.

When you've fixed the paths, save the file from the menu or press cmd-S. That will make Text Edit save the file in the same file format, IGS. Then, open the IGS with Indigo and hit render.

Simple as that, haha. Of course, you could try checkin or unchecking relative path boxes, but it didn't work for me, so I'm stuck with this process every time I want to use an IES light (one shouldn't have to do this). I'm guessing that this is a problem that occurs with Macs only.

Hope it helps!

[FakeShamus]

you're right, I just tried this again, and regardless of the relative paths being turned off Blendigo exports the complicated, unreadable path to the IES file. Blendigo bug.

[OnoSendai]

I think I've fixed the IES path problem.

[Headroom]

That would be great Ono. Thanks for the effort.

I suggested switching between relative/absolute path when Oscar_J ran into the same problem and it did not work or him, neither did it work for me.

Also I've tried editing the path in the objects.igs file but lost interest after one unsuccessful try last night.

Thanks for the suggestions. Let's keep reporting these things so we can get them fixed.

[Oscar J]

Headroom, there's now a new version of Blendigo. It works fine for me.