Blendigo for v0.9
- deltaepsylon
- Posts: 417
- Joined: Tue Jan 09, 2007 11:50 pm
I'm not absolutely sure, but I don't think the anim feature works if the .igs files are in a path with spaces in the name. It throws up a fatal exception error.
The hardest part of BEING yourself is FINDING yourself in the first place...
http://thebigdavec.googlepages.com
http://thebigdavec.googlepages.com
There seems to be some sort of problem with the exporter if you take a look at these two movies one is indigo and one is blender they are identical except that the fluid only updates times and the blender version updates 17 times. I've rendered my indigo animation for 17 frames in 4 stops it seems like it only updates the first frame and then remains like that, sorry for my english.
Take a look at the video.
http://www.savefile.com/files/979669
Take a look at the video.
http://www.savefile.com/files/979669
These files will be distributed with Blendigo exporter. It's very strange that you don't have itLutojar wrote:Console message:
INDIGO MATERIAL PREVIEW EXPORT
no preview file found "C:\indigo_v09_test6\previews\IMPsphere.xml"
also no old material preview file found "C:\indigo_v09_test6\previews\IMPsphere.xml", sorry
where did I get this files?

Hi SmartDen,
inside "exportLight()", where you assign the "pathname" variable you get the wrong path, the path of the blender file instead of the "default.igs" path
.
I think you should process the pathinfo from the "export()" function througt all the other function ("exportobjects()", "exportObject()") up to the "exportLight()" function. So it's handled the same way as it is currently for materials (which needs the path for texture-mappings).
I've seen that the GUI sometimes looks a bit strange as there seems to be some controls halfway hidden by other overlaying controls
... i'm not sure if this is only my Blender
but looks funny sometimes
many many many Thanks and best regards, zuegs
inside "exportLight()", where you assign the "pathname" variable you get the wrong path, the path of the blender file instead of the "default.igs" path

I think you should process the pathinfo from the "export()" function througt all the other function ("exportobjects()", "exportObject()") up to the "exportLight()" function. So it's handled the same way as it is currently for materials (which needs the path for texture-mappings).
I've seen that the GUI sometimes looks a bit strange as there seems to be some controls halfway hidden by other overlaying controls



many many many Thanks and best regards, zuegs
Who is online
Users browsing this forum: No registered users and 30 guests