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

[3ds Max] If texture folder set to same as glTF location, image uri is incorrect #685

Closed
PatrickRyanMS opened this issue Nov 14, 2019 · 3 comments
Assignees

Comments

@PatrickRyanMS
Copy link
Member

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.

@Drigax
Copy link
Contributor

Drigax commented Nov 14, 2019

Hey @elpie89 , I remember you added support for exporting to a separate texture folder via #532 , can you help explain the use-case for this?

@elpie89
Copy link
Contributor

elpie89 commented Nov 14, 2019

I'll take a look at this asap

@Drigax
Copy link
Contributor

Drigax commented Nov 14, 2019

Much appreciated.

@Drigax Drigax added the 3dsmax label Nov 14, 2019
@thomlucc thomlucc assigned elpie89 and unassigned Drigax Nov 14, 2019
@elpie89 elpie89 mentioned this issue Nov 21, 2019
@Drigax Drigax closed this as completed Nov 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants