Ok, I'll try this. From this initial post it wasnt'n clear enough. So, this is what "(System)" note is all about. Thanks a lot!

Sorry for posting on topic, and disturbing the flame that just started! :lol: @SmartDen. I just upgraded to 1.1.18 (from 1.1.14) using the win32 installer. All works fine, but every time I start blendigo it complains that indigo path is not set. After setting it up is OK until next Blender start. Cu...

I'm not a linux guru (not even experienced user) but when clicking the indigo icon nothing happens. When typing "sh indigo" in console I get: indigo: 1: Syntax error: word unexpected (expecting ")") same thing when trying to start indigo_console indigo_v1.1.18 running on an Ubuntu based box (8.04 ha...

@PureSpider Taking the smallest pixel value of several images will reduce fireflies, but it's biased. We all see what OnoSendai said. But the discussion has evolved and we are not talking anymore about taking the smallest pixel value but a way of excluding the "wrong" pixel aka noise and get a "most...

Wow, guys I had do read twice to understand (or so I think - what's sigma?), I'm not a programer/math guy but I think v_mulligan might be right. Anyway there must be a balance. I think there must be a point where is better to wait the rendering of one image than sum up a set of images and recombine ...

@ Ono My combined image was not optimal because of the way Photoshop combines images, taking the lowest value as you said. But the algorithm should be: if a certain pixel has values like a in the first render, a in the second and b , then the final result should be a , completely ignoring the "stati...

The principle: the noise is distributed on the surface of the render in a random way. So on a second render of the same scene we will have different noise, but most of the correct pixels will correspond on the two images. If we take three images we can get an even better combination. And so on. The ...

My scene (see first post) does not contanin any fluids or particles. Still getting the Vec3 error. It is a complex scene, though. Maybe the exporter chokes.
I'm using Blendigo 117. If no one experienced the same error with other app/exporter then must Blendigo's fault.

anybody knows what's this all about?

Fatal Error: IndigoDriverExcep: SceneLoaderExcep: syntax error while parsing Vec3
Stopped.

What's Vec3 ?

Borgleader wrote:actually the error might be on your side rather than his (unless this works with a previous version of the exporter)

Was my mistake: I set up no lights recognized by indigo.

OnoSendai wrote:I'll release 1.1.8 tomorrow barring any unforeseen issues.

Come on, man! I can't keep up the peace! New features, richer GUI... I can't test/learn them with you always sticking out a new version!

Ok, kidding!
Thanks for you efforts! Thanks for you efforts! (twice, not mispelled)

Fatal Error: IndigoDriverExcep: SceneLoaderExcep: ModelLoadingStreamHandlerExcep: UV set with index 0 was exposed, but the UV set data was not provided. (In element 'mesh', around line 123, column 5) Stopped. And was a simple plane with a cube on it...for testing purposes. thought You guys wanna kno...

I've noticed that windows installer of blendigo does not deploy the same content in IndigoDir/previews as the .zip version. As a result, the preview function implemented into the script GUI does not work when using the installer. The console message complains about not finding some .xml-s. In fact t...