Blendigo for Blender 2.5 BETA

[dougal2]

Any updates since last month? I just tried ef_19f82ca.zip + indigo_BETA02 with Blender 2.53 beta and when i switch over to Indigo as a render engine all im getting are empty panels.

Things are still changing pretty fast with Blender at the minute, and there is very little that is new in the exporter since BETA02.

If you really want an updated version for the latest blender, I can try to do it this weekend.

[Borgleader]

Any updates since last month? I just tried ef_19f82ca.zip + indigo_BETA02 with Blender 2.53 beta and when i switch over to Indigo as a render engine all im getting are empty panels.

Things are still changing pretty fast with Blender at the minute, and there is very little that is new in the exporter since BETA02.

If you really want an updated version for the latest blender, I can try to do it this weekend.

I'm just wondering why my panels are empty Maybe I screwed up the installation?

[dougal2]

Certainly the blender version you have is too new for the BETA02 exporter.
I think there might be another issue too - perhaps broken release or installation ?

[dakiru]

Certainly the blender version you have is too new for the BETA02 exporter.
I think there might be another issue too - perhaps broken release or installation ?

I tried it before (with blender 2.53) and it's the same as Borgleader's experience - nothing on the panels.

[Borgleader]

It seems the first chunk of errors (everything before the "indigo initialized" line) can be "fixed" by deleting the netrender folder. The rest seems to have to do with stuff being call with 'no_bg' as an argument which is invalid somehow.

EDIT:
Open ef/ui.py (in a text editor)
Replace all "no_bg" with "emboss" and the errors will go away

It still wont render because apparently "Output path is not writable" but...the menus show up

[Borgleader]

I grabbed the latest version of the ef folder from your website...

What is : t(**a) ? I commented it and the errors went away but with this version of the ef folder, indigo doesnt appear in the render engine menu.

Ok so I opened all of the ef files from the ef19f82ca & the version i found on your website and i looked at the differences between the two.

Oddly I dont remember t(**a) giving errors with ef19f82ca but it does with the other version. And by adding two blocks of code from the plugin.py (or engine.py i cant remember) i was able to get indigo to appear in the render engine menu. But the actual panels wouldnt show up -.-;

i hope im not confusing you

[dougal2]

I grabbed the latest version of the ef folder from your website...

What is : t(**a) ? I commented it and the errors went away but with this version of the ef folder, indigo doesnt appear in the render engine menu.

Ok, I take the hint, i'l post up a new beta this weekend

[Borgleader]

I want to help!

[dougal2]

I want to help!

OK, the current code is in two parts.

Looks like you already found the EF library: http://github.com/doughammond/exporterframework
Use the 'download source' button on the github page to get a .zip of the current code.
Copy the ef/ folder from that repository into your scripts/io/ folder.

Then you need the Blendigo code: http://github.com/doughammond/blendigo-2.5
Copy the sources/indigo folder into your scripts/io/ folder.

The code that is currently on github requires a version of blender that is newer than the official 2.53 beta release. You can grab very new builds from http://graphicall.org/

[Borgleader]

Ok so I grabbed both:
doughammond-blendigo-2.5-f56d2ca.zip
doughammond-exporterframework-a61891e.zip

and I'm running Blender 2.5 rev31168

from properties_data_camera import CameraButtonsPanel

This line seems to be causing problems:
"Cannot import name CameraButtonsPanel" in file indigo/panels/camera.py

also I dont see indigo in the list of engines but i figure its probably because of the error (since I dont see an "indigo initialised" message either)

[dougal2]

... and I'm running Blender 2.5 rev31168 ...

That's too old
Something closer to r314XX would be better.

[Borgleader]

... and I'm running Blender 2.5 rev31168 ...

That's too old
Something closer to r314XX would be better.

w00tles!

Again, nuked the netrender folder and now the menus are working! Tyvm dougal2, I'll report when i break it

[Borgleader]

Output path still not writable

[dougal2]

Output path still not writable

And what have you set the output path to ?

[Borgleader]

Output path still not writable

And what have you set the output path to ?

Same directory as the .blend file (in the text box i think it shows up as // but before it was set to /tmp\ and it wasnt working either)