Blendigo for v1.1.5
- Borgleader
- Posts: 2149
- Joined: Mon Jun 16, 2008 10:48 am
the same hereApollux wrote:I need some help here guys:
Whenever I enable "Alpha" on the renderer tab Indigo 1.1.7 crashes. No matter the Bidirectional or any other setting.
Anything I could do to get the alpha channel from the rendered image?
i think it's bug that Ono not discovered yet

Check normals, dude!




Thanks, at least isn't me overlooking something silly or extremely simple. I´ll post it on the Bug&Request forum them (unless Ono follows this, I'm not sure).SmartDen wrote:the same hereApollux wrote:I need some help here guys:
Whenever I enable "Alpha" on the renderer tab Indigo 1.1.7 crashes. No matter the Bidirectional or any other setting.
Anything I could do to get the alpha channel from the rendered image?
i think it's bug that Ono not discovered yet
On another issue: Any idea on when the "layer" option for materials will be implemented on Blendigo? That feature is way too cool !
I found something else adrift:
When rendering an animation with the "USE GUI" option selected everything works fine, but when "USE GUI" is unselected I get an error from indigo_console and the render fails for every frame.
After some test the problem was pinpointed to the .igs path containing blank spaces. Turns out that if GUI is selected quotation marks are added before and after the file path, but that doesn't happen if the console version is selected, thus the console parser tries to read everything after the first space as a command line option.
A quick look inside blendigo_v115.py shows this (I´m not a python programmer, but I remember by BASIC lessons from my youth days).
Inside def launchAnimIndigo(filename), on the "If UseGUI.Val" part:
and for the "else" part:
Notice the missing \"" on the else part, right before the +realpath ?
Already fixed on my local copy
When rendering an animation with the "USE GUI" option selected everything works fine, but when "USE GUI" is unselected I get an error from indigo_console and the render fails for every frame.
After some test the problem was pinpointed to the .igs path containing blank spaces. Turns out that if GUI is selected quotation marks are added before and after the file path, but that doesn't happen if the console version is selected, thus the console parser tries to read everything after the first space as a command line option.
A quick look inside blendigo_v115.py shows this (I´m not a python programmer, but I remember by BASIC lessons from my youth days).
Inside def launchAnimIndigo(filename), on the "If UseGUI.Val" part:
Code: Select all
f.write("start /min /belownormal /wait indigo.exe \""+relpath(indigopath, makename(filename, '-'+string+'.igs'))+"\" -t "+str(Threads.val)+" -o \""+relpath(indigopath, makename(filename,'-'+string+'.png'))+"\"\n")
Code: Select all
f.write("start /min /belownormal /wait cmd.exe /c indigo_console.exe "+relpath(indigopath, makename(filename, '-'+string+'.igs'))+" -o "+relpath(indigopath, makename(filename,'-'+string+'.png'))+"\n")
Already fixed on my local copy

Hello there,
I'm not able to use the uv_set feature.
I have a cube with two different uv set for color and bump.
The exporter always export only one set so Indigo complains that "UV set with index 1 was exposed, but the UV set data was not provided"
Both uv_set were unwrapped.
Hint: it seems that only the selected (for editing) UV is exported.
Bye
Roberto
I'm not able to use the uv_set feature.
I have a cube with two different uv set for color and bump.
The exporter always export only one set so Indigo complains that "UV set with index 1 was exposed, but the UV set data was not provided"
Both uv_set were unwrapped.
Hint: it seems that only the selected (for editing) UV is exported.
Bye
Roberto
I've got a new problem, most likely not reported before:
I want to render a scene with Indigo 1.1.5 and Blendigo 1.1.5 and I get the following error:
Anybody with the same experience?
BTW: It renders fine with Indigo 1.0.9....
I want to render a scene with Indigo 1.1.5 and Blendigo 1.1.5 and I get the following error:
There are no textures nor uv-coordinates in this scene, and just ~270.000 Polies...IndigoDriverExcep: SceneLoaderExcep: syntax error while parsing Vec3
Anybody with the same experience?
BTW: It renders fine with Indigo 1.0.9....
- Attachments
-
- Error report:
- Error.png (125.95 KiB) Viewed 4501 times
Who is online
Users browsing this forum: No registered users and 26 guests