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
If you set the texture folder to the same location as your glTF file, the uri that is encoded looks like:
..%5C FolderName %2F imageName.ext
The %5C is breaking the loading of the glTF. There could be a use case to store glTF files and images in sibling folders, so we need to figure out how to path between them correctly.
To start, we should determine if the path to the glTF and the path to the images folders as set in the exporter are the same and if so, just use the file name as the uri rather than going up one folder and then back down.
It would also be an improvement to the UX if we either spell out in the export window that the texture folder is optional or we add a checkbox to enable the image folder field. Right now, users can interpret the UI as the texture folder is required.
The text was updated successfully, but these errors were encountered:
If you set the texture folder to the same location as your glTF file, the uri that is encoded looks like:
..%5C FolderName %2F imageName.ext
The %5C is breaking the loading of the glTF. There could be a use case to store glTF files and images in sibling folders, so we need to figure out how to path between them correctly.
To start, we should determine if the path to the glTF and the path to the images folders as set in the exporter are the same and if so, just use the file name as the uri rather than going up one folder and then back down.
It would also be an improvement to the UX if we either spell out in the export window that the texture folder is optional or we add a checkbox to enable the image folder field. Right now, users can interpret the UI as the texture folder is required.
The text was updated successfully, but these errors were encountered: