I think that is time to let my exporter to see the light!
I began to write this exporter firstly to take confidence with the python API and to play with shaders parameters with the help of an interface.
But time after time the project began to grow until now…
It is an editor/exporter this is why I preferred to keep separated the blender settings from the ones to be exported.
I called it Yable, it stands for “yet another blender exporter” it is a continuosly work in progress, so check the site to know more.
Now it is in a quite stable state of development.
Further enanchements:
-Uv Exporting (on the way);
-Better coding style (OO);
-Total Gui restyling (Have you heard about MHGUI?);
-Whatever comes into my mind.
On the site you will find some info on how to use Yable, it is not complete but it helps.
I hope that this script like others will all the blender user to appreciate the growing quality
of the Yafray renderer…
You already know what I think, but I’ll say it again, nice work Andrea!
To hannibar: The hemilight is now better, to get the same imagequality as in that picture, you now need quite a bit less than the 800 samples Andrea used, which also means that it is faster now.
Jandro also added better anti-aliasing as well as other optimizations to the code. I’m not sure when it will be released though.
Looks like a nice script but for some reason I seem to be having a problem… probably stems from the fact that I barely know how to use yafray and don’t actually understand all of the settings I used when I exported Anyways when I try to “yafray firsttest.xml” it loads the mesh files, then on Sphere.001.xml.gz it says “Exception: STATUS_ACCESS_VIOLATION” and something about a stack trace o_O If anyone knows what this means and/or what to do to fix it… please let me know thanks
Thanks hannibar … what you want to say with this? Well It could be the late hour or the fact that English is not my language … What source you mean, Yafray?
btw : ever thought about coding it in the source ?
To rivwanderer:
“Exception: STATUS_ACCESS_VIOLATION”
So, it happens when yafray execute?
I really don’t know … it is the first time I see this advert.
But I’m sure that Jandro (the guy who wrote yafray) follow this thread so maybe he’s got an idea
of what’s happening…if you want you can send me via private email your xml along with the tar.gz meshes so I can test it … (but please I’m one of the last with a slow connection so stay under 1mega ).
But let me sppend some words about what yable can export:
-all meshes, until now it export ALL layers. So if you got subdivision mesh they will be exported without the “subdivision” so provide to convert them to meshes if you want to see
the “sudivided meshes” in your xml scene;
-yafray doesn’t like void meshes…I mean meshes with no point. In that case yable will export it making yafray crash. I have to fix it;
-yafray doesn’t like as well points belonging to meshes that are, how to say, appended … I mean, points that doesn’t share edges with other points … in the xml file they have the following description:
<p x=“nan” y=“nan” z=“nan”/> very nice, isn’t it?
So, some crashes of yafray are due to the fact that yable does not do a good cleaning of the mesh. In some cases I had to clean myself the meshes in blender and than updating the mesh while exporting.
You already know what I think, but I’ll say it again, nice work Andrea!
Thanks, I know but It is a pleasure to hear it from you.
Thanks hannibar … what you want to say with this? Well It could be the late hour or the fact that English is not my language … What source you mean, Yafray?
[quote]
btw : ever thought about coding it in the source ?
[/quote]
Sorry, I wasn’t very clear about that. I meant the blender source. It would be nice to see yafray well integrated in blender for example.
After a few experiments I’ve come to the conclusion that yafray can’t read the object files generated by the script. (I replaced the objects by a standard yafray sphere for example, and it worked, it rendered) But as long as I use meshes generated by the script, it gives these kind of errors?
when i get the selected object (any mesh) to abjust the material settings script crushes and here is what blender says :
Traceback (most recent call last):
File "c:\Program Files\Blender\Python\yable-beta05.py", line 798, in bevent
worked = getSelectedObject()
File "c:\Program Files\Blender\Python\yable-beta05.py", line 1432, in getSelec
tedObject
blcolors = retrieve_colors(selectedname)
File "c:\Program Files\Blender\Python\yable-beta05.py", line 1182, in retrieve
_colors
obcolor[2]=[mt.mirR, mt.mirG, mt.mirB]
SystemError: error return without exception set
Traceback (most recent call last):
File "yable-beta05.py", line 798, in bevent
worked = getSelectedObject()
File "yable-beta05.py", line 1432, in getSelectedObject
blcolors = retrieve_colors(selectedname)
File "yable-beta05.py", line 1182, in retrieve_colors
obcolor[2]=[mt.mirR, mt.mirG, mt.mirB]
SystemError: error return without exception set
I found a way to render anyway.
When you open the object file in note pad or another simple text editor, you can copy paste everything from that file in the .xml between these two tags.
<mesh>
</mesh>
It works, but it isn’t ideal. At least it has given me the oppertunity to do some tests.
It seems that some of you got problems with the include tag.
I think that I will add a feature that will disable it just to avoid this annoying problem to
continously copy&paste the object info…I will let you know when done.
On http://kino3d.com/~yable you can find a new version of yable…I added a button called “!inc” which disables the include tag. In this case you will get a single and monolithic xml.
I have also modified the point precision (i used %.10f to export points coordinates, now back to %f).
Andrea
I see there is a bug in yafray that only happens on windows with the include tag. Well, I have to say that we don’t test windows version We only compile it, try to render and give it away.
I’ll take a look at that bug and at the void mesh bug.
Anyways when I try to “yafray firsttest.xml” it loads the mesh files, then on Sphere.001.xml.gz it says “Exception: STATUS_ACCESS_VIOLATION” and something about a stack trace o_O If anyone knows what this means and/or what to do to fix it… please let me know 
thanks
).