You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
Try to load the exported models in PlayCanvas Viewer and Blender
Result
1. English Only
Entity name + texture + material name are in English.
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.
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.
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.
The text was updated successfully, but these errors were encountered:
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
Steps to Reproduce
a. Model with English-only content
b. Model with Japanese characters in entity/material/texture names
c. Model with emoji in the entity name
Result
1. English Only
2. Containing Japanese characters
3. Containing emojis
Has anyone else experienced this problem or know of a workaround? Any assistance would be greatly appreciated.
Thank you for your help.
The text was updated successfully, but these errors were encountered: