Blendigo for v0.9
-
- Posts: 6
- Joined: Thu Aug 23, 2007 3:20 am
Hi Kram1032
Can you please tell me some more exactly where that script would be found? I would be glad to put some test to it.
Anyway, you are right - the idea is working in Kerkythea. I use KT and Indigo, side by side, both are quite powerful renderer. I've just looked at in an XML file from the Blender2K exporter yesterday. Yes, the static particles are there as small polys (quite many of them in a moderately diff scene, as you can imagine). So the idea is right there and working (off course it is not the perfect solution, but working). Any scene, with organic models and hair that I've made so long was rendered in KT, because of this feat of the exporter. How nice it would be the Blendigo would do that too.
Can you please tell me some more exactly where that script would be found? I would be glad to put some test to it.
Anyway, you are right - the idea is working in Kerkythea. I use KT and Indigo, side by side, both are quite powerful renderer. I've just looked at in an XML file from the Blender2K exporter yesterday. Yes, the static particles are there as small polys (quite many of them in a moderately diff scene, as you can imagine). So the idea is right there and working (off course it is not the perfect solution, but working). Any scene, with organic models and hair that I've made so long was rendered in KT, because of this feat of the exporter. How nice it would be the Blendigo would do that too.
The current script is for single edges/vertices only...
It's posted three times, I think, in the forums...
I'll search one of the threads
Edit:
http://www.indigorenderer.com/joomla/fo ... h&start=15
here it is
It's posted three times, I think, in the forums...
I'll search one of the threads
Edit:
http://www.indigorenderer.com/joomla/fo ... h&start=15
here it is
-
- Posts: 35
- Joined: Sat Aug 18, 2007 10:20 am
I've been using Blendigo for the past few days and I really love the script, but there's one thing that's very annoying for me.
Because I'm using a laptop with a slowish 5400rpm harddisk and an even slower FAT32 formatted partition, it takes a while to write out the whole scene file each time. Especially for large scenes it can take a while.
I have no idea if this is possible using the Python scripting in Blender, but wouldn't it be a very good idea to use the .Igs files for material and scene settings only, and to write out objects in the .Obj file format and update them only when it's necessary?
That would cut the time to export files from Blender to Indigo in half on my system. I know that exporting to an object isn't free either, but it's going to be a lot faster when there's only material settings to be changed and / or one or two objects instead of the whole scene database.
The only question is if Python in Blender can execute other Python scripts (and check if it was done succesfully). Hmm..
(this last piece of text was just some brainfarts )
Because I'm using a laptop with a slowish 5400rpm harddisk and an even slower FAT32 formatted partition, it takes a while to write out the whole scene file each time. Especially for large scenes it can take a while.
I have no idea if this is possible using the Python scripting in Blender, but wouldn't it be a very good idea to use the .Igs files for material and scene settings only, and to write out objects in the .Obj file format and update them only when it's necessary?
That would cut the time to export files from Blender to Indigo in half on my system. I know that exporting to an object isn't free either, but it's going to be a lot faster when there's only material settings to be changed and / or one or two objects instead of the whole scene database.
The only question is if Python in Blender can execute other Python scripts (and check if it was done succesfully). Hmm..
(this last piece of text was just some brainfarts )
- deltaepsylon
- Posts: 417
- Joined: Tue Jan 09, 2007 11:50 pm
-
- Posts: 35
- Joined: Sat Aug 18, 2007 10:20 am
I think you could be in for a surprise then. I'm fairly sure I am not the only Indigo-user with a laptop
Also, for large scenes it would probably improve the situation on 7200rpm disks as well (I'm talking about scenes with more than a million polygons here, not a few spheres).
I just took a look at the Python API documentation and there doesn't seem to be any functionality for executing other scripts. Could have overlooked on it though..
Also, for large scenes it would probably improve the situation on 7200rpm disks as well (I'm talking about scenes with more than a million polygons here, not a few spheres).
I just took a look at the Python API documentation and there doesn't seem to be any functionality for executing other scripts. Could have overlooked on it though..
- deltaepsylon
- Posts: 417
- Joined: Tue Jan 09, 2007 11:50 pm
perhaps you are right ( ), i just made a couple of subdivided spheres (5) each with 200 000 faces. I tried to export it, and it kept exporting for 2 minutes until it gave me a memory error.
edit: btw im on a laptop with a 5400 rpm and a 2.13 ghz Pentium M.
edit2: testing the latest indigo exporter for blender right now, been 40 seconds and still not done with the first sphere. The sound my HD is making is scaring me
edit 3: It worked this time, no memory error. Took 2 minutes and 46. Resulting file: 167 MB.
I think doing the save thing as you work would take too long, but maybe the exporter code could be optimized a bit (plz dont flame me on that) for speed, because it sure took a long time to export whereas blender saved the million poly+ scene file in about 2-3 seconds.
edit: btw im on a laptop with a 5400 rpm and a 2.13 ghz Pentium M.
edit2: testing the latest indigo exporter for blender right now, been 40 seconds and still not done with the first sphere. The sound my HD is making is scaring me
edit 3: It worked this time, no memory error. Took 2 minutes and 46. Resulting file: 167 MB.
I think doing the save thing as you work would take too long, but maybe the exporter code could be optimized a bit (plz dont flame me on that) for speed, because it sure took a long time to export whereas blender saved the million poly+ scene file in about 2-3 seconds.
-----
P5N32-C Coffee machine overclocked to 4 cups a minute! still not enough...
P5N32-C Coffee machine overclocked to 4 cups a minute! still not enough...
-
- Posts: 35
- Joined: Sat Aug 18, 2007 10:20 am
Heh
Optimizing wouldn't make much sense, I'd guess. It's Python after all (ie. an interpreted language == slower).
And writing out all the scene data each time doesn't make much sense either, that's why I posted :p
I've read something about an option to include files.. that would be a nice option as well!
Optimizing wouldn't make much sense, I'd guess. It's Python after all (ie. an interpreted language == slower).
And writing out all the scene data each time doesn't make much sense either, that's why I posted :p
I've read something about an option to include files.. that would be a nice option as well!
- deltaepsylon
- Posts: 417
- Joined: Tue Jan 09, 2007 11:50 pm
-
- Posts: 35
- Joined: Sat Aug 18, 2007 10:20 am
- deltaepsylon
- Posts: 417
- Joined: Tue Jan 09, 2007 11:50 pm
- Heavily Tessellated
- Posts: 108
- Joined: Thu Aug 10, 2006 4:20 pm
- Location: Huh?
linux monkeys
This is relevant to 0.9_beta_4s... not spending much time in linux I see. They're simple yet annoying errors...
First error: if you try to spawn blender from inside the directory as one normally spawns an executable from the current directory, it blows up because of the path separator processing doesn't account for having to specify the starting directory:
./blender &
gives, when you try to run the exporter:
"/home/heavily/blender/blender-2.44-linux-glibc232-py25-i386/./.blender/scripts/bpydata/IndigoWrapper.conf"! this file must contain the path to the Indigo directory.
Second error: Unlike Windows, linux is case sensitive. Seems you re-introduced this one. blendigo_v0.9_beta_4s.zip has the file stored as Indigowrapper.conf so even launching with a rooted path:
/home/heavily/blender/blender-2.44-linux-glibc232-py25-i386/blender &
can't find file "/home/heavily/blender/blender-2.44-linux-glibc232-py25-i386/.blender/scripts/bpydata/IndigoWrapper.conf"! this file must contain the path to the Indigo directory.
Third error, well it's more of an omission than an error really, it does not expand the home directory shortcut, treating it as a literal tilde in the path:
can't locate indigo path "~/.wine/drive_c/indigo_09_test3/indigo.exe"! please correct your "/home/heavily/blender/blender-2.44-linux-glibc232-py25-i386/.blender/scripts/bpydata/IndigoWrapper.conf" file.
Other than that, it's rockin' right along...
--------------------
edit:
logic flaw: Hmm it will still process infinite ground plane with bidir toggled on. In this case putting up that textual disclaimer takes as much typing as disallowing it.
something like: if (GroundPlane.val) and (Bidirectional.val): ### ignore user request ?
First error: if you try to spawn blender from inside the directory as one normally spawns an executable from the current directory, it blows up because of the path separator processing doesn't account for having to specify the starting directory:
./blender &
gives, when you try to run the exporter:
"/home/heavily/blender/blender-2.44-linux-glibc232-py25-i386/./.blender/scripts/bpydata/IndigoWrapper.conf"! this file must contain the path to the Indigo directory.
Second error: Unlike Windows, linux is case sensitive. Seems you re-introduced this one. blendigo_v0.9_beta_4s.zip has the file stored as Indigowrapper.conf so even launching with a rooted path:
/home/heavily/blender/blender-2.44-linux-glibc232-py25-i386/blender &
can't find file "/home/heavily/blender/blender-2.44-linux-glibc232-py25-i386/.blender/scripts/bpydata/IndigoWrapper.conf"! this file must contain the path to the Indigo directory.
Third error, well it's more of an omission than an error really, it does not expand the home directory shortcut, treating it as a literal tilde in the path:
can't locate indigo path "~/.wine/drive_c/indigo_09_test3/indigo.exe"! please correct your "/home/heavily/blender/blender-2.44-linux-glibc232-py25-i386/.blender/scripts/bpydata/IndigoWrapper.conf" file.
Other than that, it's rockin' right along...
--------------------
edit:
logic flaw: Hmm it will still process infinite ground plane with bidir toggled on. In this case putting up that textual disclaimer takes as much typing as disallowing it.
something like: if (GroundPlane.val) and (Bidirectional.val): ### ignore user request ?
Who is online
Users browsing this forum: Ahrefs [Bot] and 33 guests