BabylonJS / BabylonJS/BlenderExporter
Using AddOn with Blender 4.x
- Dominant language
- Python
- Stars
- 308
- Forks
- 57
- PR merge metrics
- No merged PRs in 30d
Description
Good day :) I last used the Blender to Babylon AddOn in december 2021, and now I need to use it again, in connection with a React app I have that uses Babylon and I need to export blender models to babylon to use them in the react app. My updated Blender setup uses GeoNodes so I need to use the latest 4.x versions of Blender
What is the status of the addon? is it being maintained? I went to the github and I see that I can only download a zip file that is called: Blender2Babylon-3.3x.zip
will that only work with Blender 3.3 and earlier ones? it won’t work with the Blender 4.2?
is the Addon no longer active? but still working with older blender versions?
I definitely need to keep using the same system because all my code of the react app is made to work with the results of that addon, and I bet that changing now to use a different export would create a huge mess in my app.
At the moment for each model that I import in Babylon I have four files:
model.babylon
model.babylon.manifest
model.log
model_baked_DIFFUSE.jpg
and If I look at the .log file, I see the versions that I have been using:
Exporter version: 2.80.0, Blender version: 2.80 (sub 75)
========= Conversion from Blender to Babylon.js =========
the 2.80 versions, and also in the past I also used these:
Exporter version: 6.4.6, Blender version: 2.82 (sub 7)
========= Conversion from Blender to Babylon.js =========
the problem now is that the update of my blender pipeline is now based on geo nodes so I cannot use blender 2.80 anymore, now I need to use blender 4.2 yes or yes,
thank you for any clarifications, info, tips :)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by inspecting Blender2Babylon-3.3x.zip and the exporter version information in the cited .log files, then compare the add-on's stated support with the Blender 4.2 and GeoNodes setup described here. Done means establishing and documenting whether the existing exporter supports that setup or what compatibility work is required for the React/Babylon pipeline.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, react
- Domain
- tooling, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100