-
Notifications
You must be signed in to change notification settings - Fork 39
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
Model ends up without texture #68
Comments
|
Hi @sayduck-daniel . This is definitely odd. I am also seeing all files and references working when opening the usdz file. I also locally converted the original glTF and it looks to work as expected. Are you converting to usdz with Also are you on the lastest master of |
ok... I understand what is the problem... It was no need for me to build 30h of source code for libraries needed by USD or for me to have to compile from source LLVM or CLANG. The problem comes from how I call gltf2usd. Initially, I was doing it with a full path:
Then when I switch from Debian to Amazon Linux 2 on EC2, while installing stuff I simplify my script to do instead:
So long story short, I just spent 80h in total for nothing 👍 Relative paths, is it something on your side or USD side? I can open an issue on their repo if needed. |
Ah that makes sense. I think the relative paths would probably have to be handled within this tool. Feel free to file and issue here or make a PR if you think it’s a quick fix! |
Could you add this to the README file? Just in case someone else false in this trap. |
@sayduck-daniel actually I had a thought. The converter was able to transfer the textures so the issue may actually be with usdzip. I’ll try to reproduce when I get some time. But I’ll make a note to update the readme |
@sayduck-daniel I just merged a change to support relative paths in the generated usdz file. I basically change to the directory of the usdc file and switch all paths to relative so |
Thanks, I'm gonna try o^when we next deploy the latest of USD and your code. I let you know ASAP |
Usdzip can not handle relative paths, i already filed a report on USD forum I am not sure if gltf2usd should fix this with a workaround. |
this line which used to work now fails
This line has to be given now in the latest version instead So you must specify a directory now.... |
@MrDChristop thanks for flagging the issue. I made a recent change that converts the usd file path to absolute path for now. |
Hi. Where is the commit for this? |
@MrDChristop the commit is here at the bottom of gltf2usd.py: https://github.com/kcoley/gltf2usd/pull/83/files |
I'm trying to get a GLTF converted in USDZ but somehow, my model ends up without any texture. When I uncompress the .usdz the texture file is in there.
For some context, I installed last week USD by Pixar and gltf2usd on a Debian on AWS EC2. It worked, I was able to export and get a nice looking USDZ.
Then I proceed to do the same again but on an Amazon Linux 2 on AWS EC2 and after some first tests, I see the USDZ doesn't display its texture. I taught it was because of some library compatibility or such kind of problem so I keep digging but now when I resolve myself to go back to use Debian I try again to convert the same GLTF and I get the same without texture model.
I wonder if this could come grom gltf2usd? Is there something obvious I'm missing here?
The text was updated successfully, but these errors were encountered: