Blendigo 2.0.6.1

[benn]

Installer for Blendigo 2.0.6.1 on Windows:

http://www.indigorenderer.com/dist/plug ... taller.exe

Mac version with installer:

http://www.indigorenderer.com/dist/beta ... seimage.gz

You will require Indigo 2.0.6 to use this plugin.

Changes:

* Automatically detects the location of Indigo from the registry
* Material preview and export is fixed for Indigo 2.0.6
* Lamps are converted to a sun object (so you can hit render with the default scene)

Changes to 2.0.6.1:

* Better error reporting if you don't have indigo installed.

Comments?

[Doug Armand]

Installation went fine - nice

Script installed correctly and Indigo runs without having to set location - nice

The light grey text on the white background makes it almost impossible to read on my system - not nice.

Material previews works great - Woohoo! nice

Thats all I've tested so far.

Win 7 x64/ Blender 2.49 RC3 x64

[ROUBAL]

Thank you very much !

I have just downloaded it.

It is 02:49 in the night.I will test it as soon as possible. I have to sleep some hours before !

[ROUBAL]

Well, bad news...

None of the previous problems have been solved, and it is worse than ever, with new things not working :

Previous problems still not fixed :
- Some materials are still not exportable for an unknown reason.
- UVTex/uv name not solved despite what I have read on the forum.
- Frequent message not helpful : Memory Allocation failure while allocation master buffer.

The button Render in Indigo doesn't open the file browser, and no igs file seems to be saved. To save an igs file, you have to set your start and stop frames to the same number and Export Animation (not practical).

And a thing that could be due to Indigo itself : it seems that the rendered image is saved only with the save button. No more automatic saving : if your computer crashes after many hours,you have nothing saved ! Right ?

[WytRaven]

Renders are autosaved, just not in indigo program directory anymore as that is bad practice (a practice which vista + prohibits).

[ROUBAL]

Please could you tell me where they are saved by default ?

I'm working under Windows XP Pro SP2.

I have searched every where on the machine without finding the renders, except for manually saved images.

[suvakas]

In my system the renders folder is located here:

Code: Select all

C:\Documents and Settings\Username\Application Data\Indigo Renderer\renders

[ROUBAL]

Thanks suvakas,

After a new tests, I have found the folder at the same location than on your system, but my rendered images are not inside.

In my computer, I have also found something at this location :

Code: Select all

C:\Documents and Settings\Username\Local Settings\Temp\

In this folder, there are only two files that belongs to blendigo and indigo :

the blendigo-export.igs
and indigo-wrapper.cmd

[suvakas]

I belive the ..Local Settings\Temp\ folder is where Blendigo saves the igs files it exports. The actual renderings should appear under the folder I gave you. Maybe Blendigo directs Indigo to save to a different path than Indigo's default folder?

[ROUBAL]

I have uninstalled everything : Indigo,Blendigo, cleaned the register, removed the Py file from my script directory.

After reinstalling, it is exactly the same. No autosave of my images.png (I mean that I haven't found them).

I have changed the output directory in blendigo, without more success...

If it is not possible to define the render directory, it is a bad thing. I have always separated the software and the data. It helps to keep the application disk clean.

I also prefer to put my data on separate partitions and better on external disks, for confidentiality reasons (for customers privacy), it allows me to put my data disks in a safe when I'm not at home.

New test : After I have typed manually the path of the renders directory, Blendigo crashes and now shows a python error pop up each time I launch it. After uninstalling and reinstalling blendigo, it is the same. So, now, I can't export at all... Well, I can't believe it. With indigo 1.0.9 everything worked in one click...

Well, more experiments : After testing with blendigo 1.1.18.py, the error as disappeared, and I can launch blendigo 2.0.6 again. Though, it disappears from the script window after each export ! And still no autosaved image in the render directory...

New tests, and One more time, I have to come back to indigo 1.0.9_3 and blendigo 1.0.9 ! I have done some test with them, and they work fine. The path are defined by hand when you launch blendigo.exe, and you can run indigo on whatever disk you want, and it saves automatically your rendered images as well. It even run and save on a USB key!

I can understand that 2.0.6 being commercial it can't run on a USB key because of the software key, but I should be at least able to use it. Since I have 2.0.6, I have not been able to render more than the default cube and a previously created scene from which I have had to remove many objects that were not accepted (crash) or not exported.

[Doug Armand]

Blendigo window disappears from script window after using the 'Render in Indigo' button.

[SmartDen]

Blendigo window disappears from script window after using the 'Render in Indigo' button.

[Jambert]

Hi all,

What about linux installer? Do linux users will have to require every time an update??? Sorry but it's now a commercial software and linux users seems to be forgotten...

sorry for my poor english

thanks

[pitat450]

Hey guys, i wonder what went wrong here, but when i try t o export it produces lot of errors starting with File String...blah blah
Is it ok that I am using version 2.5.2 of python?
I was using blendigo 1.0.9 and it was working fine except for external material so i tried to update and this happened, thanx for reply...

[ROUBAL]

Some more days (and bad nights) later, I still can't get Blendigo 2.0.6 an Indigo 2.0.6 work togather.

Still not found the directory where images are supposed to be saved automatically.

I'm so tired to install and uninstall... The Output Paths field in blendigo has no effect at all. You can write in whatever you want, blendigo doesn't take it in account !

Please, in the next blendigo release, come back to the manual path system asking to fill in fields when installing !