Yet Another Blender Egg Exporter (YABEE)

Pipeline
,
161

Really hoping this exporter doesn’t get abandoned like the other ones because without this there’s still no way to get animations into panda from blender, even after a year…

I 100% agree that it would be far more user friendly and usable if it supported the blender interface.

162

Actually looks like someone made GUI frontend for an older version in the 3rd page
sites.google.com/site/gf4f56d4g6 … e_10_UI.py

Come on ninth :slight_smile:

163

Ok ) convinced )

164

:smiley:

165

Hello. Is there a list of missing features?
I think you should make one like a TODO list. That way people will know exactly what they exporter does and does not support and you (or someone else) won’t need to remember what you wanted to add next.

I’d suggest changing the name. It doesn’t seem right now with the “Blender’s”, correct way would be “Yet Another Blender Egg Exporter” (YABEE), but even that is too long and there really aren’t other exporters out there which work on something more than just a blank cube.
How about something simpler like “Eggxporter”? Just a suggestion.

I’d also strongly suggest to host it in a site like sourceforge.

If you want I could help with creating a html documentation for the script like the one for Chicken.

Anyway, thanks.

166

I uploaded source to the GoogleCode. I think the “Issues” tab can be used as TODO.
http://yabee.googlecode.com
As for name - ok, I changed it to “Yet Another Blender Egg Exporter”. I think it’s “Yet another” becouse many people still use Blender 2.49 and Chicken, also there are other ways to export models from Blender into Panda.
I would be glad if you will help me with the documentation )

I hope tomorrow, after tomorrow i’ll upload UI for the YABEE

167

Well, both Chicken and another even more deprecated egg exporter were both for Blender 2.4, which is “another” program with it’s own UI and API. But regardless, the main reason I don’t like such names is they are too long, abbreviations are not as easy for the tongue and memory and is not very original.
That’s for you to decide though. I only think “Eggxporter”, or “Eggporter” or another shorter name is easier to remember. Maybe even “Kuritsa”, lol.

OK, I’ll write a html doc when you finish the GUI.

168

Hi all.
I was using the script (the last version) with my model and I recived this error message:

TypeError: Matrix multiplication: not supported between 'mathutils.Matrix' and 'mathutils.Vector' types

Anyone knows how to fix it or have any information?

lot of thanks and by the way congratulations for the creators of this genial script, helps me a lot!!

169

hm. last time i checked it was still a warning that this operation would no longer be supported.

so instead of
matrixvector
you would have to do
vectormatrix

so swapping every matrix*vector operation in the script might help. didnt try it tho.

170

This operation was changed in the Blender 2.59, so i think that you use an earlier version, and I suggest you to update Blender.

171

rev.11 with UI
Should be installed as the plugin in the Blender addons directory.

172

ui is really nice.

getting a error in 2.60 as the use_twosided call was moved. details to be found here:
blender.org/documentation/bl … html#id140

use_image was removed.

173

Really nice ninth.
One thing I would suggest, is to have a text entry field where people could specify their “bin” directory of Panda. That way you could easily make use of pview and egg2bam/pzip, like Chicken.

174

Same here. Works fine after commenting out the lines 558 and 559 in egg_writer.py.

The UI is really nice indeed and it makes the script much more user friendly. Before, it was a bit problematic to use. Keep up the good work ninth.

175

Nice GUI. Let me know when you’ll be happy with the way it is so I’ll write the html doc.

As for the script itself, I get this error when trying to export a model with single texture.

location:<unknown location>:-1
WRITE main EGG to C:\Users\Me\Desktop\untitled.egg
Traceback (most recent call last):
  File "C:\Program Files (x86)\Blender Foundation\blender-2.60a-release-windows3
2\2.60\scripts\addons\io_scene_egg\__init__.py", line 318, in execute
    sett.get_bake_dict())
  File "C:\Program Files (x86)\Blender Foundation\blender-2.60a-release-windows3
2\2.60\scripts\addons\io_scene_egg\yabee_libs\egg_writer.py", line 1012, in writ
e_out
    file.write(get_egg_materials_str())
  File "C:\Program Files (x86)\Blender Foundation\blender-2.60a-release-windows3
2\2.60\scripts\addons\io_scene_egg\yabee_libs\egg_writer.py", line 918, in get_e
gg_materials_str
    used_textures = tb.bake(BAKE_LAYERS)
  File "C:\Program Files (x86)\Blender Foundation\blender-2.60a-release-windows3
2\2.60\scripts\addons\io_scene_egg\yabee_libs\texture_processor.py", line 160, i
n bake
    assigned_data = self._prepare_images(btype, params[0], params[1])
  File "C:\Program Files (x86)\Blender Foundation\blender-2.60a-release-windows3
2\2.60\scripts\addons\io_scene_egg\yabee_libs\texture_processor.py", line 109, i
n _prepare_images
    self._save_obj_props(obj)
  File "C:\Program Files (x86)\Blender Foundation\blender-2.60a-release-windows3
2\2.60\scripts\addons\io_scene_egg\yabee_libs\texture_processor.py", line 93, in
 _save_obj_props
    props['uvs'].append((uvd.use_image, uvd.image))
AttributeError: 'MeshTextureFace' object has no attribute 'use_image'

location:<unknown location>:-1

location:<unknown location>:-1
176

Really nice work, thank you !

177

Get that one too. Any idea what to do?

178

For now, either completely avoid setting textures in Blender, or use “Simple” mode in Tex. processing field.

EDIT:
On a side note, this thread really needs to become sticky.

179

Thanks to all for the feedback and advice )
Now fixed for use in the Blender 2.60a link

180

I tested the new script and it seems to work with a model with a single texture. But one thing quickly caught my eye: why are the textures renamed and placed in a folder “tex”?