[X3D-Ecosystem] Blender X3D Exporter

[John Carlson]

Blender is also probably the only free tool for X3D to glTF, so I hope we
get to the I of I/O as well.

I’m here if you need help on any Blender/X3D stuff, but I’m not extremely
familiar with either, especially the Blender GUI and node system.  I know
very little about the Blender API, other than what I gleaned from addons
and searches.  What I will be pursuing soon is soft body physics in Blender
and how it can be realized in X3D, at first separate from HAnim.

I am most familiar with HAnim and animation in Blender.  But I’m fairly new
to the concept of actions (TimeSensors).

What I think you might find is a large gaps between Blender and X3D.  On
the Blender side, I would look towards EMPTY objects for X3D stuff, perhaps
using a specialized naming scheme.   There are also places to stuff custom
data in Blender objects as well, but I’ve not used them.  And obviously, we
will be looking to enhance X3D with features Blender has, like soft body
physics.

You’ll probably want to maintain both an armature-based skeleton and an
alternative skeleton, unless you can find another way besides armature to
do HAnimJoint skinCoordWeight and skinCoordIndex on export.   There can be
linkages between the armature and normal objects (feature points for
example) which might be difficult to figure out.  And of course, we want to
handle armature from existing Blender models.

On Sun, Nov 30, 2025 at 2:33 AM Bergstrom, Aaron via X3D-Ecosystem <
x3d-ecosystem at web3d.org> wrote:

> All,
>
> Today I ported a portion of the RawKee I/O classes to Blender… well the
> “O” portion of I/O anyway. And by that, I mean I removed the Maya specific
> API calls, and did a very rudimentary stub out for Blender.
>
> I haven’t pushed any of it to the Blender repo yet and probably wont for a
> while, as I still have some work to do to fully understand how Blender
> works under the hood.
>
> I have some experimentation to do with CGE assets for blender, which I
> believe will help me get started.
>
> The way I see it, this work was a necessary step in order to support
> Houdini export and the development of the USD/X3D file translator. So even
> if this group ends up not wanting to add these classes to the Blender X3D
> exporter repo, it’s still worth the time I put into it.
>
> Aaron
> --
> X3D-Ecosystem mailing list
> X3D-Ecosystem at web3d.org
> http://web3d.org/mailman/listinfo/x3d-ecosystem_web3d.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-ecosystem_web3d.org/attachments/20251130/9186cdfe/attachment.html>