Blendigo 2.0.6.1

[Doug Armand]

Watch out Doug! You'll make ne0 cry with comments like that

You might say that but I couldn't possibly comment

[suvakas]

As for whoever made the "igi's are too big" comment. If 2 igis of any realistic size are too big for your system to handle then you should be seriously considering your hard drive situation.

That was me. Yes, I constantly keep running out of hdd space and that's my personal drama. I would be happy about the option that allows me to turn off igi saving. Like it has always been actually. I see no point in arguing over it.

Suvakas if you have issue with only a single autosave.igi being used..

Well..nope, I thought it was an excellent idea . Indigo has always saved different igi's per render and I automatically assumed, that turning on autosave for igi's would behave the same. I never thought about having only one igi. Maybe my wording was a bit bad and sounded sarcastic? I really think 1 igi is a good idea.
For multiple Indigo instances you could always save different igi's for each using some thread number or whatever. But yeah..this is more like Ono's territory.

[ROUBAL]

The one thing I don't like about the latest blendigo is that the igs being exported is no longer under user control. In other words you used to be able to turn off auto start and it would prompt for a save location (allowing subsequent xml editing with ease) whereas now the igs is getting saved to a temp folder somewhere and I find that anoying. I would definitely like to have manual .igs saving restored as an option.

@WytRaven I agree with you that I found the old way more practicle, but I have also discovered that it can be done with the Export Animation button by exporting only one frame (needs to use Start and End number identical in the Blend file). This way you can access to a path field to choose your igs file name and location.

For the igi autosave, I agree with you too: the png file is useless as you can get it from the igi file. I had made a confusion between igi and igs, so I thought that I would have to render again!

This said, if igi files are really too heavy to be saved each x seconds on some computers, autosaving only png files could be an option too.

[WytRaven]

but I have also discovered that it can be done with the Export Animation button by exporting only one frame (needs to use Start and End number identical in the Blend file). This way you can access to a path field to choose your igs file name and location.

Thanks for that ROUBAL. It's a work around to use in the meantime at least. Don't know why I didn't think to try that

[BleedForMe]

I have a problem, every time I try to run the export script, I get an error message saying: "Error%nBroken installation of Blendigo, please reïnstall". The console reads:

----------------------------
Blendigo 2.0.6
----------------------------
Traceback(most recent call back last):
File"<string>", line 1, in <module>
File "C:\Documents and Settings\Administrator\Application Data\Blender Foundation\Blender\.blender\scripts\Blendigo.py", line 2630, in <module>
NameError: name 'indigo' is not defined

Could it be that it's not installed in my main blender directory?

Don't know what it is, but I can't figure it out myself.

Daniel

[ROUBAL]

Could it be that it's not installed in my main blender directory?

It's a possibility.

Try to re-install Blendigo. It it doesn't work, reinstall Indigo and again Blendigo.

If it still doesn't work, maybe also that you haven't set the indigo path in Blendigo GUI (or a wrong path).

As I have already said several times, path troubles wouldn't happen with fields for typing the paths by hand when installing Blendigo, like in previous versions of Blendigo... Please, when something works well, don't break it !

[Josh]

There has to be a folder called blendigopkg with some python scripts in the same folder as the main Blendigo.py script. Re-installing should fix this.

I doubt that there is a problem with the paths, since the main script found its way to the correct folder.

[benn]

@roubal sorry you've had no luck with blendigo 2.0.6.1 - we've fixed a bunch of issues in 2.0.7. The path setting in the old blendigo did work once it was set up - but this was is easier for new users - they can get up and going faster.

[ROUBAL]

Well, I hope that 2.0.7 will be the end of my nightmares,because I have few remaining hair to pull