xamlexporter Work Item Rss Feed

Created Issue: Port to Blender 2.6x [19082]

Tonko — Wed, 19 Dec 2012 11:57:35 GMT

Title says it all

Commented Issue: port to blender 2.5 [13778]

ModiCharly — Wed, 06 Jul 2011 13:36:43 GMT

The current version of the exporter script does not run in blender 2.5. It need be ported to the new python 3.1 syntax and use the new blender APIs.
Comments: ** Comment from web user: ModiCharly **

Hello,

I am currently developping an addon for Blender 2.5x exporting Blender scene into WPF xaml viewport.

You'll find it on my blog:
http://www.charly-studio.com/blog/blender-2-5-wpf-xaml-exporter/

Please, do not hesitate if you encounter any problem with it or if you have any feedback. I can't promise I will make it evolve instanlty but I'll do my best to release an helpfull final version at the end!

Hope it will help! :-)

Charles

Created Issue: XAML Exporter and Blender 2.49b with 64bit machine [15369]

kennywoo89 — Sat, 19 Feb 2011 03:25:42 GMT

I use xaml_export.py as guide but when exporting - error appear and fail to export to xaml
64bit machine or Python(i use Python 2.6) ?

Commented Issue: port to blender 2.5 [13778]

bitbonk — Mon, 09 Aug 2010 05:22:07 GMT

The current version of the exporter script does not run in blender 2.5. It need be ported to the new python 3.1 syntax and use the new blender APIs.
Comments: ** Comment from web user: bitbonk **

I don't think anyone is dedicated to this project anymore. I can't reach TheRHogue.

Commented Issue: port to blender 2.5 [13778]

vmrocha — Fri, 06 Aug 2010 13:45:23 GMT

The current version of the exporter script does not run in blender 2.5. It need be ported to the new python 3.1 syntax and use the new blender APIs.
Comments: ** Comment from web user: vmrocha **

Is there any estimate of when it will be available?

Created Issue: port to blender 2.5 [13778]

bitbonk — Sat, 24 Jul 2010 00:01:26 GMT

The current version of the exporter script does not run in blender 2.5. It need be ported to the new python 3.1 syntax and use the new blender APIs.

Commented Issue: No module named BPyMesh [10743]

vmrocha — Wed, 21 Jul 2010 20:22:01 GMT

Running Blender 2.49b, XAML Exporter gives this error:

Traceback (most recent call last):
File "<string>", line 1, in <module>
File "C:\Program Files\Blender Foundation\Blender\.blender\scripts\xaml_export
.py", line 90, in <module>
import BPyMesh
ImportError: No module named BPyMesh
Comments: ** Comment from web user: vmrocha **

Use the zipped dist of blender. It comes with all the required libs.

Created Issue: export Geometry and Materials as Ressources [11972]

bitbonk — Mon, 01 Mar 2010 21:46:20 GMT

Let me decide if I want to tecide Geometry and Materials as Resources or inline.

Created Issue: let me decide between ModelVisual3D and Model3DGroup [11971]

bitbonk — Mon, 01 Mar 2010 21:45:02 GMT

We really need a way to configure wich items in the scenegraph get exported as ModelVisual3D and wich ones as Model3DGroup. ModelVisual3D has some unique features that are needed but not for all parts in the scenegraph need it.

Commented Issue: No module named BPyMesh [10743]

bluemarble — Fri, 15 Jan 2010 19:14:46 GMT

I found a solution, go to http://www.koders.com/python/fid30278B946111D882EA61D8CD236E7638C0000AA1.aspx?s=opengl and download bpy_mesh.py and install it where you installed the xaml_export.py file.

more files will cascade, keep downloading and installing then the problem seems to go away

Commented Issue: No module named BPyMesh [10743]

bluemarble — Fri, 15 Jan 2010 18:55:55 GMT

I am experiencing the same problem, when I search Google I get plenty of the same issue with other export scripts. It could be an issue related to my installation of Blender so I am currently reviewing all possibilities.

I did not have a scripts directory so I created one in C:\Program Files\Blender Foundation\Blender\.blender\scripts and deployed the xamlexporter there. I did notice that the standard exporters dissapear as soon as I created the scripts folder and deployed the xaml exporter script there. I am sure this is not right either.

Created Issue: Probleme Blender -> convert XAML -> Expression Blend [10833]

JoeWifi — Mon, 26 Oct 2009 17:56:45 GMT

Lorsque l'on met une image comme texture d'un mesh plane dans blender on la voit dans le rendu blender.
Lorsqu'on exporte en xaml dans blend, on retrouve le plane, mais sans l'image. Pourtant on retrouve l'image dans les propriétés des matériaux OB_Plane pour les faces Material et BackMaterial.

Created Issue: No module named BPyMesh [10743]

ericjohannsen — Sun, 11 Oct 2009 01:14:09 GMT

Commented Issue: newIndices and tuple comparisons in writeMesh

TheRHogue — Thu, 08 Jan 2009 22:51:53 GMT

There is a section of code in writeMesh that does not appear to be working correctly:

<code>
# If this index is already mapped scan our entries to see if
# there is already a position/normal/textureCoordinate set
# which matches.
for i in indexMap[index]:
if positions[i] == position and normals[i] == normal and textureCoordinates[i] == textureCoordinate:
newIndices.append(index)
continue
</code>

The position/normal/textureCoordinate vectors are being compared to tuples in the corresponding lists, but the type difference seems to be causing the condition to evaluate false everytime. Putting in a trace statement gives a clue as to what might be wrong:

trace("%s==%s" % (positions[i], position))
(1.0, 0.99999994039535522, -1.0)==[1.000000, 1.000000, -1.000000](vector)

Altering this and comparing tuples to tuples fixes it (e.g., positions[i] == tuple(position), ...) , but then an array out of bounds error will occur when textureCoordinates[i] is evaluated if mesh.faceUV was false.

However, it does not seem that appending to newIndices in this location and continuing to the top of the inner for loop is going to produce the desired effect anyway, i.e. if the goal is to reuse an existing "new index" for the face and not map the same vertex again. Instead of appending a new position/normal/uv to the WPF verts in the code that comes afterward, it should skip the appending part if newIndex was already found in the map, so that duplicate verts are not mapped twice. Something like the following:

<code>
newIndex = -1

if not indexMap.has_key(index):
indexMap[index] = []
else:
# If this index is already mapped scan our entries to see if
# there is already a position/normal/textureCoordinate set
# which matches.
for i in indexMap[index]:
if positions[i] == tuple(position) and normals[i] == tuple(normal) and (mesh.faceUV == False or textureCoordinates[i] == tuple(textureCoordinate)):
newIndex = i
break;

if newIndex >= 0:
newIndices.append(newIndex)
else:
# We do not already have a matching position/normal/textureCoordinate
# for this index so we create one and add it to our indexMap.
indexMap[index].append(len(positions))
newIndices.append(len(positions))
positions.append(tuple(position))
normals.append(tuple(normal))

if mesh.faceUV:
textureCoordinates.append(tuple(textureCoordinate))
</code>
Comments: ** Comment from web user: TheRHogue **

After some investigation, Blender is creating duplicates for UV purposes. In the case of a Cube, 3 duplicates per vertex are needed to set a unique UV position.

In the case of solid color, duplicates can be removed, but normals would need to be averaged.

So, it appears the code should just be removed. Blender should be removing duplicates, not the exporter.

Created Issue: newIndices and tuple comparisons in writeMesh

a2spicer — Sun, 07 Dec 2008 22:43:41 GMT

Closed Issue: option to export selected items as separate modelvisual3d

TheRHogue — Sun, 15 Jun 2008 23:16:45 GMT

We should have an option export selected objects in blender as individual modelvisual3d objects within the same scene. So one doesn't have to reasemmble the whole scene afterwards. This is especially cumbersome if you need to exactly repostion everything the way it was in the blender scene.
Comments: the latest version now supportes parent\children relationships with model3dgroup.

Closed Issue: option to export camera and light

TheRHogue — Sun, 15 Jun 2008 23:15:51 GMT

There should be a additional option to export camera(s) and lights of the scene as well. In that case not just the Model3dGroup is created but also a ViewPort3D object that contains the lights and the camera. I am not sure how it could be achived to export multiple cameras since ViewPort3D only supports one. Maybe instead of export the actual camera object we just export some ressource data that contains the setup information for the cameras that we could bind to if we want to switch the camera.

For blender lights that are not supported in WPF we could
a) not export it (and write that to console)
b) progamatically create a light that matches it at closely as possible.

This way I could export the complete scene setup as desired. Setting up the lights and cameras afterwards is sometimes a tedious task, especially if I want to have them the same way I had them in blender.
Comments: lamps and cameras are exported. If you want something exported, just make sure it is selected.

CREATED ISSUE: geometry with multiple materials is not exported correctly

bitbonk — Mon, 10 Mar 2008 14:47:25 GMT

When I have a blender object with multiple unconnected meshes and assign a material to each of the meshes the materials are exported but the assignmen to the meshes gets lost. This is probalby due to the fact that the exporter exports one blender object as one mesh even if the object consists of multiple meshes

COMMENTED ISSUE: option to export selected items as separate modelvisual3d

bitbonk — Fri, 29 Feb 2008 21:23:51 GMT

Of course one could export the whole thing as one big modelvisual3d with lots of seperate geometrymodel3d but this is often not desired e.g. when you want to be able to click individual objets.

CREATED ISSUE: option to export selected items as separate modelvisual3d

bitbonk — Fri, 29 Feb 2008 21:19:29 GMT