Blendigo 3.6.5.1
-
- Posts: 1828
- Joined: Mon Sep 04, 2006 3:33 pm
Re: Blendigo 3.6.5.1
Hi guys,
Any word on the Dupligroup export error? Linked objects work fine, it's just Group instances that are giving up.
Any word on the Dupligroup export error? Linked objects work fine, it's just Group instances that are giving up.
Re: Blendigo 3.6.5.1
I think the problem come when section plane feature was implemented, consideration was not taken for empty having no data.
I made a hack, it seems to work if you're desperate, probably it breaks something .
in export/geomtry.py, find:
Add this before if obj.data != None:
thus;
I made a hack, it seems to work if you're desperate, probably it breaks something .
in export/geomtry.py, find:
Code: Select all
if(obj.data.indigo_mesh.section_plane):
xml = SectionPlane(obj.matrix_world.col[3], obj.matrix_world.col[2], obj.data.indigo_mesh.cull_geometry).build_xml_element()
model_definition = (xml,)
self.ExportedObjects.add(self.object_id, model_definition)
self.object_id += 1
return
# Special handling for sphere primitives
if(obj.data.indigo_mesh.sphere_primitive):
xml = SpherePrimitive(obj.matrix_world, obj).build_xml_element()
model_definition = (xml,)
self.ExportedObjects.add(self.object_id, model_definition)
self.object_id += 1
return
thus;
Code: Select all
if obj.data != None:
if(obj.data.indigo_mesh.section_plane):
xml = SectionPlane(obj.matrix_world.col[3], obj.matrix_world.col[2], obj.data.indigo_mesh.cull_geometry).build_xml_element()
model_definition = (xml,)
self.ExportedObjects.add(self.object_id, model_definition)
self.object_id += 1
return
# Special handling for sphere primitives
if(obj.data.indigo_mesh.sphere_primitive):
xml = SpherePrimitive(obj.matrix_world, obj).build_xml_element()
model_definition = (xml,)
self.ExportedObjects.add(self.object_id, model_definition)
self.object_id += 1
return
-
- Posts: 1828
- Joined: Mon Sep 04, 2006 3:33 pm
Re: Blendigo 3.6.5.1
Hey William,
Nice find. Does it work OK with everything else? Can't afford to break anything at the moment, so if it's not safe yet I'll keep nagging Glare
Nice find. Does it work OK with everything else? Can't afford to break anything at the moment, so if it's not safe yet I'll keep nagging Glare
Re: Blendigo 3.6.5.1
I have no idea, use at own risk
Didn't even make a scene/objects for indigo yet, this bug always in the way of using any assets or using any old scenes from other renderers, just couldn't be bothered making all objects local and duplicates real because this results a mess.
Didn't even make a scene/objects for indigo yet, this bug always in the way of using any assets or using any old scenes from other renderers, just couldn't be bothered making all objects local and duplicates real because this results a mess.
-
- Posts: 1828
- Joined: Mon Sep 04, 2006 3:33 pm
Re: Blendigo 3.6.5.1
Some things that could be improved in Blendigo:
- Dupligroups / group instances (NoneType object has no attribute 'indigo_mesh')
- External materials don't seem to work when there is a Blend or Double-Sided Thin material with sub-materials ('no such material as <x>'). I suspect the problem only occurs when there is a sub-sub-material. Seems Indigo saves the first sub-materials in a Blend or Double Sided Thin material, but then doesn't look to see if those sub-materials have any children. Heartless. This may be an Indigo issue with saving materials.
The interface for making materials before was much better, where you could see each material in a stack and could better visualize the material structure.
- Transmittance color needs to be exposed in materials settings (for Double-Sided Thin)
- Depth and Shadow passes need to be exposed in render settings.
- PyNodes are on their way into Blender! Should make Indigo material editing a fair bit easier
- Dupligroups / group instances (NoneType object has no attribute 'indigo_mesh')
- External materials don't seem to work when there is a Blend or Double-Sided Thin material with sub-materials ('no such material as <x>'). I suspect the problem only occurs when there is a sub-sub-material. Seems Indigo saves the first sub-materials in a Blend or Double Sided Thin material, but then doesn't look to see if those sub-materials have any children. Heartless. This may be an Indigo issue with saving materials.
The interface for making materials before was much better, where you could see each material in a stack and could better visualize the material structure.
- Transmittance color needs to be exposed in materials settings (for Double-Sided Thin)
- Depth and Shadow passes need to be exposed in render settings.
- PyNodes are on their way into Blender! Should make Indigo material editing a fair bit easier
-
- Posts: 1828
- Joined: Mon Sep 04, 2006 3:33 pm
Re: Blendigo 3.6.5.1
PyNodes are merged into Blender trunk:
http://projects.blender.org/scm/viewvc. ... bf-blender
Should make Indigo material setup easier?
http://projects.blender.org/scm/viewvc. ... bf-blender
Should make Indigo material setup easier?
Re: Blendigo 3.6.5.1
This stuff would be great!.... so would a bugfix
- Polinalkrimizei
- Posts: 647
- Joined: Sat May 02, 2009 6:59 am
Re: Blendigo 3.6.5.1
Should make users of other exporters pretty jealous
Re: Blendigo 3.6.5.1
Nice find, have committed the fix.William wrote:I think the problem come when section plane feature was implemented, consideration was not taken for empty having no data.
I made a hack, it seems to work if you're desperate, probably it breaks something .
in export/geomtry.py, find:Add this before if obj.data != None:Code: Select all
if(obj.data.indigo_mesh.section_plane): xml = SectionPlane(obj.matrix_world.col[3], obj.matrix_world.col[2], obj.data.indigo_mesh.cull_geometry).build_xml_element() model_definition = (xml,) self.ExportedObjects.add(self.object_id, model_definition) self.object_id += 1 return # Special handling for sphere primitives if(obj.data.indigo_mesh.sphere_primitive): xml = SpherePrimitive(obj.matrix_world, obj).build_xml_element() model_definition = (xml,) self.ExportedObjects.add(self.object_id, model_definition) self.object_id += 1 return
thus;Code: Select all
if obj.data != None: if(obj.data.indigo_mesh.section_plane): xml = SectionPlane(obj.matrix_world.col[3], obj.matrix_world.col[2], obj.data.indigo_mesh.cull_geometry).build_xml_element() model_definition = (xml,) self.ExportedObjects.add(self.object_id, model_definition) self.object_id += 1 return # Special handling for sphere primitives if(obj.data.indigo_mesh.sphere_primitive): xml = SpherePrimitive(obj.matrix_world, obj).build_xml_element() model_definition = (xml,) self.ExportedObjects.add(self.object_id, model_definition) self.object_id += 1 return
Re: Blendigo 3.6.5.1
Luxrender already got basic pynodes support!StompinTom wrote:PyNodes are merged into Blender trunk:
http://projects.blender.org/scm/viewvc. ... bf-blender
Should make Indigo material setup easier?
http://www.luxrender.net/forum/viewtopi ... 962#p94962
Your ad here!
-
- Posts: 1828
- Joined: Mon Sep 04, 2006 3:33 pm
Re: Blendigo 3.6.5.1
Awesome! Exactly what would be amazing with Indigo, along with an ISL node.SaphireS wrote:Luxrender already got basic pynodes support!StompinTom wrote:PyNodes are merged into Blender trunk:
http://projects.blender.org/scm/viewvc. ... bf-blender
Should make Indigo material setup easier?
http://www.luxrender.net/forum/viewtopi ... 962#p94962
Perhaps things like Blender clouds and marble textures could be loosely converted to ISL functions?
Re: Blendigo 3.6.5.1
From my experience with Maya it's not very difficult to set custom nodes up. The most complex part is the one involving the realtime viewport feedback. I for one skipped that part in MtI.
The rest is about defining inputs and outputs types, names and default values mostly. Then comes the exporting stage wich calls outputs and read them before an eventual data processing.
Sorry if I'm trolling, I'm a fool by night as well
The rest is about defining inputs and outputs types, names and default values mostly. Then comes the exporting stage wich calls outputs and read them before an eventual data processing.
Sorry if I'm trolling, I'm a fool by night as well
obsolete asset
Who is online
Users browsing this forum: No registered users and 61 guests