Indigo Renderer Forum

Windows 7.0 64bits
Blender 2.49 64bits
Blendigo 2.4 Stable Update #2
Indigo 2.4.13 64bits
____________________

Not sure if it is systematic but I've noticed that the Gain value under the Environnement tab in Blendigo gets reset to 1.0 very often after reopening a saved file. Could there be a problem with the way the variable is saved?

Got the exact same result again. Here is a little bit more info on my setup :

I have 4 machines.

MACHINE 1 : Workstation where I create stuff in Blender (also Indigo slave)
- V drive is a shared drive from Machine 2

MACHINE 2 : Indigo Master
- Local Drive shared with all other machines

MACHINE 3 : Indigo Slave
- V drive is a shared drive from Machine 2

MACHINE 4 : Indigo Slave
- V drive is a shared drive from Machine 2

Steps I took
1. Machine 2 has Blender open with file 3d.blend
2. Machine 1 has Blender open with file 3d.blend
3. I perform changes in Blender in Machine 1
4. I confirm that Env. Gain is set to 4.0 in Blender on machine 1
4. I save changes in Blender on Machine 1
5. I re-open 3d.blend on machine 2
6. I look at Env. Gain on Machine 2 and it is set to 1.0
7. I can confirm that all my other changes are actually there on machine 2 so the save/load actually worked.

Thanks in advance,

Again, what is strange is that I don't have that problem systematically. It seems intermittent?

Hello,

I just ran into another problem regarding gain value. This time on the material themselves. I have created a "Neon" material within a "Neon" light layer and I have specified this layer to be set with a Gain value of 0.008. When I launch my render with Indigo, it is set to 1.000. I have to manually change it back to 0.008.

This is not a problem with static images but with animation, it's quite a different story!!!

Any idea if this problem is generic or only related to my setup?

Hello Dougal, any idea what could be the problem?

Hi,

Sorry I was meant to look into this, but development of the new exporter has been taking quite a lot of my Indigo-time. I'll probably have some spare time tomorrow and I'll try to catch up with a few 2.49 issues.

Indeed, the value was not specified in the list of settings to be saved to file. It'll be fixed in the next release.

Cool thanks,