io_scene_gltf2: Blender 4.0 and above missing "glTF Embedded (.gltf)" option. #105196
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#105196
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Blender Version
Broken: 4.0.2, 4.1.0 ced066e0c8db, 4.2.0 06d3627c4398
Worked: 3.6.x
Short description of error
Prior to 4.0, there was a glTF exporter settings to export as plain-text format ".glTF", with data embedded instead of separated.
Exact steps for others to reproduce the error
File > Export > glTF 2.0.
Select the "Format" drop-down, and see the option is now missing.
Is this an intended deprecation of this feature? Or are there plans to bring it back?
Thanks.
It was removed on purpose as part of
097bf234f6
@JulienDuroure can shed light on the topic a bit.
Hello,
Yes, this is an intentional behavior.
We'd like to get some user feedback: Why it was your preferred option, and why was it better than glb or Separated glTF in your workflow/pipeline.
Please comment here to give us some feedback: https://github.com/KhronosGroup/glTF-Blender-IO/issues/2148