Cindigo 1.1.14 - "instancing terror!"
- zeitmeister
- Posts: 2010
- Joined: Tue Apr 22, 2008 4:11 am
- Location: Limburg/Lahn, Germany
- Contact:
Hmmm... Indigo changelog 1.1.13 > 1.1.14 isn't anything essential cindigo should bother about. So here some more detail or even better a scene with the bug would helpzeitmeister wrote:No problems here using Cindigo 1.1.4 and Indigo 1.1.4 on the mac …
I got problems when I used Cinidgo 1.1.4 with Indigo 1.1.3.
The better you guys debug and post about it, the better Cindigo will become in feature releases
polygonmanufaktur.de
- zeitmeister
- Posts: 2010
- Joined: Tue Apr 22, 2008 4:11 am
- Location: Limburg/Lahn, Germany
- Contact:
Here you can see the error message that Cindigo sent to me with instanced objects and the test scene.
edit by fused: i deleted the image, sry. but it really was too large...
edit by fused: i deleted the image, sry. but it really was too large...
- Attachments
-
- Prueba1.1.14.zip
- (72.35 KiB) Downloaded 205 times
Hey m8...
The error is simply explaint... your object "Arch28_001_01" is disabeled for export (red Dot), so the instanced object is missing the related mesh in Indigo!
Also why so much work with instancing every single mesh???? jus push the whole "Lampara" null objectinto a Indigo or C4D instance and done!
Cindigo supports also C4D instanced, but having a lot of them arround eats up Viewport Performance (like having a forrest of instanced trees etc.). The Cindigo Instance object doesn't displays your instanced object in the viewport, so it saves this memory!!
hope this helped!
**edit**
Anotherthing about your scene: for white material use RGBof max 204, otherwise your diffuse material will be so bright that the light will bounce of "for ever" and scene take much longer to be noisefree!
The error is simply explaint... your object "Arch28_001_01" is disabeled for export (red Dot), so the instanced object is missing the related mesh in Indigo!
Also why so much work with instancing every single mesh???? jus push the whole "Lampara" null objectinto a Indigo or C4D instance and done!
Cindigo supports also C4D instanced, but having a lot of them arround eats up Viewport Performance (like having a forrest of instanced trees etc.). The Cindigo Instance object doesn't displays your instanced object in the viewport, so it saves this memory!!
hope this helped!
**edit**
Anotherthing about your scene: for white material use RGBof max 204, otherwise your diffuse material will be so bright that the light will bounce of "for ever" and scene take much longer to be noisefree!
polygonmanufaktur.de
Thanks to you Rafaello, playing around with your scene I found 2 Bugs with the instancing system. I uploaded the scene agian, altered a little so fused can see what I'm talking about!
1) I have two instanced of your grouped Objects(1x C4D Instance, 1x Cindigo instance), if both areon the bottom of the tree, Indigo throws out an error. if one of the is on the top, no error occurs!
2) wenn exported an Indigo runs, the lampshade doesn't get exported in the instances!
Have fun finding the Bug fused
1) I have two instanced of your grouped Objects(1x C4D Instance, 1x Cindigo instance), if both areon the bottom of the tree, Indigo throws out an error. if one of the is on the top, no error occurs!
2) wenn exported an Indigo runs, the lampshade doesn't get exported in the instances!
Have fun finding the Bug fused
- Attachments
-
- instancing bug.zip
- the c4d scene file!
- (64.02 KiB) Downloaded 213 times
polygonmanufaktur.de
-
- Posts: 51
- Joined: Thu Jul 03, 2008 10:46 pm
- Location: Berlin, Germany
- Contact:
Received "Fatal Error: IndigoDriverExcep: ObjectExcep: Exception while building tree: Memory allocation failed." in an Scene with an instance(external). What does that mean?
second issue: Indigo does not use the assigned material for an external instance (in cinema 4d). I have to rename the material to "default" in the igs.
second issue: Indigo does not use the assigned material for an external instance (in cinema 4d). I have to rename the material to "default" in the igs.
- Attachments
-
- external.rar
- .c4d & .igs files
- (65.34 KiB) Downloaded 199 times
looks like you dont have enough ram.Juniorsatan wrote:Received "Fatal Error: IndigoDriverExcep: ObjectExcep: Exception while building tree: Memory allocation failed." in an Scene with an instance(external). What does that mean?
this is an issue that cant be solved easily. you have to create a material with the name of the material defined in the external file in c4d.Juniorsatan wrote:second issue: Indigo does not use the assigned material for an external instance (in cinema 4d). I have to rename the material to "default" in the igs.
Last edited by fused on Fri Nov 14, 2008 8:14 am, edited 2 times in total.
yeah, right. "thanks" ZomB and Rafaello...ZomB wrote:Thanks to you Rafaello, playing around with your scene I found 2 Bugs with the instancing system. I uploaded the scene agian, altered a little so fused can see what I'm talking about!
1) I have two instanced of your grouped Objects(1x C4D Instance, 1x Cindigo instance), if both areon the bottom of the tree, Indigo throws out an error. if one of the is on the top, no error occurs!
2) wenn exported an Indigo runs, the lampshade doesn't get exported in the instances!
Have fun finding the Bug fused
kidding. glad you found some bugs, i was a little scared of myself!
some progress pics:
- Attachments
-
- the material helper tag is now an object. also the null that holds the materials is a custom object
- mats.jpg (101.64 KiB) Viewed 3924 times
-
- indigo instances now show the bounding boxes of childs of the instanced objects.
- indigo instance.jpg (120.17 KiB) Viewed 3924 times
- zeitmeister
- Posts: 2010
- Joined: Tue Apr 22, 2008 4:11 am
- Location: Limburg/Lahn, Germany
- Contact:
Who is online
Users browsing this forum: No registered users and 26 guests