Hello, must be a problem related to my setup but I am confused :

Versions :
- Windows 7 - 64bits
- Indigo 2.0.12 - 64bits
- Blendigo 2.2.11 -c (even though is shows as -b)

When I start rendering with Indigo from Blendigo GUI, I get the following messages (see attached pics)


but Indigo is in my path. When I launch Indigo from any directory from DOS, it works fine. Why is Blendigo not able to launch Indigo?

P.S. I also tried to use the "start indigo..." command directly from dos and it works fine.

To resolve the problem I copied all indigo files directly in the blender folder and it resolved my issue but I don't find it very practice (mainly for reinstallation of new versions...)

Any ideas?

I suggest you install the latest indigo - the installer creates some registry values which blendigo uses to locate the executable.

Latest version as in latest stable "2.0.12" or latest as in beta 2.2.9? I already have version 2.0.12 installed...

The latest beta is 2.2.12, which is soon to become the 2.2 stable release. If you're worried about installing something labelled 'beta' you won't have long to wait for the next stable release.

I would recommend you install 2.2.12 for now, there's many bug fixes and new features been introduced since 2.0.12

I just reinstalled Indigo version 2.2.12 64bit on my Windows 7 system in the default directory : c:\program files\Indigo Renderer (it must have overwritten all previous files).

I created a new folder on my D drive and copied the Blender 64bit files in it (version 2.49b) from the ZIP file found on the blender.org web site. Then, I installed the new version 2.2.11-d installer (which seems to still be labeled "Blendigo v2.2.11 -b" in the Blender Python GUI by manually selecting the new script folder.

Tried a simple render, and I got the same error message?

This is really strange because I don't have any problem with another machine with a node licence where I also have Blender installed? Indigo starts fine!!!

That most certainly is not true. You should have a good look at what files you have installed. If you were really running 2.2.11-d it would say exactly that in the GUI.

Oops! OK, reinstalled blendigo 2.2.11-d and it does indeed show the proper version number. Unfortunately, I still have the same error. Here are the screen shots with the version number:

OK, thanks for taking the time to update. Now I know what you've got, we can start to dig to the bottom of this issue.

Firstly, I'd like to say that you don't need Indigo on your path to make Blendigo work. However, I can see the convenience if you like to run indigo manually, and we need to find out if that is conflicting with the way Blendigo is supposed to work.

On my machine, adding indigo to the path does not cause this or any other errors.

Second, we should check what Indigo data you have in the registry, regarding installation path.

The line where Blendigo says "Could not find Indigo executable. I looked for ..." should print out a full path to the .exe that is stored in the registry. Since the path is missing, we should check that the installer worked correctly.

Seeing as you seem able to use the CLI and set paths, I'll assume you can look in the registry for me (regedit) and see if you have the following key present:
HKEY_CURRENT_USER/Software/Glare Technologies/Indigo Renderer/InstallDirectory

If that is there, and it it set to the correct location then we know that the Indigo Installer works OK, and the problem lies in Blendigo.

Here is a snapshop of my registry :



Ok, it seems that the installation did not complete properly than? Here are some info on my setup if it can help:

The workstation is on an AD domain and locked with Windows policy. In order to install the application, the installation file is run as Windows Domain Admin (actually the ultimate admin : schema admin, etc.) on my workstation. Doing so would remove all protection and let the application install every files requested and modify any registry keys.

I tried to reinstall Indigo. I still get the same keys in the registry under "Indigo Renderer".

Can you go up one level and show us what's in the main 'Indigo Renderer' key ?

Sure can!

you went up 2 levels! I want to see the one in between!

As I suspected, it's an Indigo Installer issue. On Vista 64bit I have this:

It is strange that it works fine on some workstation and not on others! I guess it could be related to the Windows AD policies!

In the mean time, I imagine I can just create the missing keys manually!