Cindigo 1.0 - beta 1
I'm totally not into coding etc. but maybe you could archive this by a workaround using cinemas material preview system.fused wrote:yes, that would be a cool feature! but im afraid i cant let c4d update the material helper tag. at least i found no way. thats why you have to click on the helper again, even if the preview is finished.ZomB wrote:I would love to see the rendering in C4D updates ever second (or a custom time value) and only stopping by hitting a stop button.
(for the actual system, by checking the preview you maybe would like to render it a little bit more, but got to start from Zero again..)
simply assign the Indigo rendering rendering aoutput as a texture for a plane,
then set it to animation and it updates automatically...
maybe this is an idea to start at, or total bullshit ^^
polygonmanufaktur.de
Hmmm... same problem here. 1.0 doesn't work.WLAD wrote:hi fused, i have a problem with the exporter. sinse i have reinstal cinema it doesn not load the 1.0.1 exporter. but the 0.9.3 stil work well. i have tryid the versions 10, 10.1, 10.5 nothing works.
OS - Vista Ultimate 64 bit
Cinema 4D R10 64 bit
edit:
0.93b works, but only with 32bit Version of Cinema4d
Would be awesome fused if you could fix this
@ Behrendt and WLAD:
looks like ill have to compile a 64 bit version of the plugin?!?! ill see what i can do and will update the exporter with a 64 bit version soon.
@ shimo:
you have to choose the indigo dir on your harddrive. you should have downloaded end extracted it before.
@ ZomB:
sounds like a good idea. maybe ill do it like this. or similar.
looks like ill have to compile a 64 bit version of the plugin?!?! ill see what i can do and will update the exporter with a 64 bit version soon.
@ shimo:
you have to choose the indigo dir on your harddrive. you should have downloaded end extracted it before.
@ ZomB:
sounds like a good idea. maybe ill do it like this. or similar.
Behrendt: to compile a 64 bit version, i need the api of a 64 bit c4d r10 (not 10.5).
what i need is the "_api_lib" folder located in "resource" and the folder "cinema4dsdk" located in "plugins". would be nice if you could send it to me via pm!
i dont have a 64 bit version and there is no demo available...
what i need is the "_api_lib" folder located in "resource" and the folder "cinema4dsdk" located in "plugins". would be nice if you could send it to me via pm!
i dont have a 64 bit version and there is no demo available...
ok, ill correct you
from the documentation:
Q: Can I cross-compile my plugins under a regular 32 Bit environment? A: Yes, this is possible, though we recommend that you use a 64-bit environment for testing and bug fixing. To cross-compile you need the 64-bit archive of CINEMA 4D with the 64-bit CINEMA 4D API.
from the documentation:
Q: Can I cross-compile my plugins under a regular 32 Bit environment? A: Yes, this is possible, though we recommend that you use a 64-bit environment for testing and bug fixing. To cross-compile you need the 64-bit archive of CINEMA 4D with the 64-bit CINEMA 4D API.
I think I might have found a bug.
The same scene exported gives with the previous version:
and with the new version:
As you can see the material name is missing. But I checked in the C4D scene, it still is there. I'm using C4D 10.0 32bit.
The same scene exported gives with the previous version:
Code: Select all
<material>
<name>untereTaste</name>
<blend>
<a_name>black</a_name>
<b_name>nullMat</b_name>
<blend_factor>0.5</blend_factor>
<blend_map>
<uv_set>default</uv_set>
<path>Phone_untere_Tasten.jpg</path>
<exponent>1</exponent>
</blend_map>
</blend>
</material>
Code: Select all
<material>
<blend>
<a_name>black</a_name>
<b_name>nullMat</b_name>
<blend_factor>0.5</blend_factor>
<blend_map>
<uv_set>default</uv_set>
<path>Phone_untere_Tasten.jpg</path>
<exponent>1</exponent>
</blend_map>
</blend>
</material>
Who is online
Users browsing this forum: No registered users and 31 guests