[X3D-Ecosystem] Dec 10 - Ecosystem Meeting Agenda

[John Carlson]

Sure, Doug Sanden started the io_scene_x3dv Blender exporter, and I tried
to help, but I got embroiled in both import and export.  Eventually, when
it came to integrate into Blender source, there were too many changes, the
code had diverged, so I switched back to XML export, where I have a couple
of WIP PRs I could use help on:

https://projects.blender.org/extensions/io_scene_x3d/pulls

The main things I worked on were animation import and HAnim, but I got
stuck on one of Vince’s examples “sand runner” or something, trying to
maintain dual hierarchies for bones and geometry (there’s probably some way
to do one hierarchy in blender???).  The suggestion is to make bones
optional, but there’s no evidence one can do skin weights without bones
(can you find some?).  Also, the imported bone animations didn’t follow the
X3D animation.   Reading documentation or following other examples is
probably critical here.

I have other animation import attempts here, for non-HAnim, which were more
successful:

https://github.com/coderextreme/X3DJSONLD/tree/master/blend/localtest


Well, now you know why I know so much about X3DPSAIL, why I had to change
it, etc.

“Recent” work has delved into support for multiple TimesSensors through
Blender actions, tracking animations on import back to originating
TimeSensors and creating animation “actions” as Michalis revealed in a
meeting.  Hopefully, we should be able to support anything that
 Blender-glTF supports as far as interactivity, but that’s a whole separate
project for glTF, last I heard.

I think the best thing to do is work on export until it’s complete, and
then focus on import.  Doing both is probably too much at the same time.

When we want to do X3D to glTF, then we can work on X3D import.  Let’s get
export done, because many people want that.

My main suggestion is to follow what Blender does, unless X3D wants to
break away again.

Some people are really stuck on the X-Z plane being the floor, but that’s
not going to happen.  False floors are acceptable.  Unless you want to fork
Blender.


BTW, everyone, Blender 5 is available.

John


On Wed, Dec 10, 2025 at 2:35 AM Bergstrom, Aaron via X3D-Ecosystem <
x3d-ecosystem at web3d.org> wrote:

> I’m going to add this to the discussion.
>
>
>
> I didn’t know about it.
>
>
>
> *From:* John Carlson <yottzumm at gmail.com>
> *Sent:* Wednesday, December 10, 2025 2:05 AM
> *To:* X3D Ecosystem public discussion <x3d-ecosystem at web3d.org>
> *Cc:* Bergstrom, Aaron <aaron.bergstrom at und.edu>
> *Subject:* Re: [X3D-Ecosystem] Dec 10 - Ecosystem Meeting Agenda
>
>
>
> I looked through the minutes, and there is already an exporter based on
> x3d.py (aka x3dv.py)
>
>
>
> https://github.com/coderextreme/BlenderX3DSupport/tree/main/io_scene_x3dv
>
>
>
> Enjoy!
>
>
>
> This also tries to handle EMPTY Blender Objects and converts them to X3D
> objects of various types, based on a naming convention.
>
>
>
> John
>
>
>
>
>
> On Wed, Dec 10, 2025 at 12:59 AM Bergstrom, Aaron via X3D-Ecosystem <
> x3d-ecosystem at web3d.org> wrote:
>
> All,
>
>
>
> Here’s my proposed Agenda for the meeting in the morning:
>
> *Agenda Topics*
>
>    - Blender Topics - Materials
>    - Blender Exporter in General
>    - Maya Exporter
>    - Open Discussion
>
>
>
> I apologize for sending this out so belated.
>
>
>
> Below is the Zoom Link and Meeting Agenda can be found on the Web3D
> website:
>
>
> https://www.web3d.org/calendar/2799/x3d-ecosystem-working-group-meeting/2025-11-12t140000-2025-12-10t140000-2026-01
>
>
>
> Aaron
>
> --
> X3D-Ecosystem mailing list
> X3D-Ecosystem at web3d.org
> http://web3d.org/mailman/listinfo/x3d-ecosystem_web3d.org
>
> --
> 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/20251210/4c87e102/attachment.html>