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

glTF Exporter: Non-ASCII characters corrupted in exported data #7030

Closed
yushimatenjin opened this issue Oct 13, 2024 · 2 comments · Fixed by #7034
Closed

glTF Exporter: Non-ASCII characters corrupted in exported data #7030

yushimatenjin opened this issue Oct 13, 2024 · 2 comments · Fixed by #7034

Comments

@yushimatenjin
Copy link
Contributor

Description

Hello,

I've encountered an issue while using the PlayCanvas glTF Exporter.
It appears that the exporter is not functioning correctly when entity names, materials, or textures contain non-ASCII characters.

Version

  • PlayCanvas Engine v2.1.0

Steps to Reproduce

  1. Here are the sample project and execution URLs:
  1. Attempt to export the models using the glTF Exporter:
    a. Model with English-only content
    b. Model with Japanese characters in entity/material/texture names
    c. Model with emoji in the entity name
  2. Try to load the exported models in PlayCanvas Viewer and Blender

Result

1. English Only

  • Entity name + texture + material name are in English.

result001

  • This worked normally, and I could load it without issues in both the PlayCanvas Viewer and Blender.

2. Containing Japanese characters

  • Entity name + texture + material name are in Japanese.

result002

  • The model can be viewed in the PlayCanvas Viewer but entity names appear corrupted, indicating that the export wasn't successful
  • I couldn't import the exported model data into Blender

3. Containing emojis

  • Entity name includes an emoji.

emoji003

  • This model couldn't be loaded even in the PlayCanvas model viewer.

Has anyone else experienced this problem or know of a workaround? Any assistance would be greatly appreciated.

Thank you for your help.

@willeastcott
Copy link
Contributor

Thanks for the detailed bug report. It was very useful to resolving the problem! 🙏

@yushimatenjin
Copy link
Contributor Author

Thank you so much for your quick response to this !!

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 a pull request may close this issue.

2 participants