Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix the Navigation Mesh component export for Blender 4.2 #312

Merged
merged 1 commit into from
Oct 19, 2024

Conversation

Exairnous
Copy link
Contributor

@Exairnous Exairnous commented Oct 14, 2024

Add an extra dummy value to the Navigation Mesh component when exporting from Blender 4.2.
Hubs expects the value for the Navigation Mesh to be an empty dictionary, but the glTF exporter attempts to strip these out.
To combat this, the Hubs exporter uses a dummy value that gets stripped down to an empty dictionary by the glTF exporter, but in Blender 4.2 the glTF exporter added in an additional call to strip out empty values and ended up removing the component entirely.

Fixes #311

Add an extra dummy value to the Navigation Mesh component when exporting from Blender 4.2.
Hubs expects the value for the Navigation Mesh to be an empty dictionary, but the glTF exporter attempts to strip these out.
To combat this, the Hubs exporter uses a dummy value that gets stripped down to an empty dictionary by the glTF exporter, but in Blender 4.2 the glTF exporter added in an additional call to strip out empty values and ended up removing the component entirely.

Fixes #311
@Exairnous Exairnous added this to the 1.6.1 milestone Oct 15, 2024
@Exairnous Exairnous merged commit a425fff into master Oct 19, 2024
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

navmesh does not work in Hubs - Blender 4.2.2 seams not to export the navmesh component correctly
1 participant