Indigo 2.0 Stable

[pixie]

Hi Phoenix,

Do you get the same behaviour with every scene? The indigo thread behaviour only applies to the rendering process, not when building the scene. If you can zip up the scene and email it to us we can take a look at the usage.

Ben

This is due to the way 64 bits scheduling works, it happens all the time, namely when more then one indigo is run

[Phoenix]

Hi Nick,

I have a problem.

Indigo always freezes nearly my entire system so that it mostly costs me minutes just to stop a rendering.
Cause while in the Indigo GUI the thread priority is said to be "Below Normal", in fact it is still "Normal". That is what I get, if I check it in the Windows Task-Manager.

Just for your information:
My OS is Windows XP Pro x64 and my CPU is a Q6600.

Kind regards,
Tom

hi Tom,
I'll work on this for the next version, so that the Indigo GUI is more responsive.

Hi Nick,

thank you!

But is there also a chance, that you can fix the problem, that the thread priority will be set correct under XP x64?

[Jambert]

Is it possible to run an "autosave" image or it's no longer available?

Sorry: output path doesn't work with animation rendering with blendigo...

[OnoSendai]

Hi Nick,

I have a problem.

Indigo always freezes nearly my entire system so that it mostly costs me minutes just to stop a rendering.
Cause while in the Indigo GUI the thread priority is said to be "Below Normal", in fact it is still "Normal". That is what I get, if I check it in the Windows Task-Manager.

Just for your information:
My OS is Windows XP Pro x64 and my CPU is a Q6600.

Kind regards,
Tom

hi Tom,
I'll work on this for the next version, so that the Indigo GUI is more responsive.

Hi Nick,

thank you!

But is there also a chance, that you can fix the problem, that the thread priority will be set correct under XP x64?

Well, it's set correctly for the render threads already.

[OnoSendai]

Is it possible to run an "autosave" image or it's no longer available?

Sorry: output path doesn't work with animation rendering with blendigo...

Autosave should still work in general.

[SmartDen]

Is it possible to run an "autosave" image or it's no longer available?

Sorry: output path doesn't work with animation rendering with blendigo...

Autosave should still work in general.

Autosave is working

[ROUBAL]

Autosave is working

Yes, but while png files are autosaved in a user defined location, through a path field in Blendigo, the igi files are still autosaved at the former location in the C:/Documents and settings/User Name/Application data/indigo Renderer/ folder.

Having both png and igi files autosaved in the same user defined folder would be really fine in a next Blendigo release ! Pleeeease !

[CTZn]

I agree with you ROUBAL, but it's definitly an exporter issue since Indigo can do that already, as per its manual page 13:

-igio pathname
Writes the Indigo Image (IGI) output to pathname instead of the usual generated pathname.
Only used if IGI output is enabled.

[ROUBAL]

@ CTZn : Which manual are your talking about ?

In the 1.0 serie manual, there is only something about igi in the XML file (True/False choice) on page 11.

And in the 2.0 manual, on page 13 there is something about the license.

[CTZn]

I was quoting the 1.x series manual, and page 13 is were the command line reference begins, as I can see it. The -igio parameter is the fifth parameter described on that page. I don't believe it was disabled for Indigo 2.x, so exporters should be able to use it.

[fused]

yes, it works. very well

[Jambert]

Ono, could you allow higher value for linear tonemapping, it's just 10^6 and it's not enough to correct F-stop.

Here an exemple with lower value http://www.indigorenderer.com/forum/vie ... f=5&t=6557

thanks

[Zom-B]

simply raise the opening time for the aperture...

[Jambert]

simply raise the opening time for the aperture...

Ok lol

thanks

[Russdigo]

Can you have a 64bit Indigo version on the master working with 32bit Indigo versions on the slaves?


Cheers Russell