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

Merging color and alpha to one texture when they use different UV channels #1229

Closed
dmitri-fm opened this issue Oct 1, 2020 · 10 comments
Closed

Comments

@dmitri-fm
Copy link

Texture merging will cause problems if color texture and alpha texture use different UV channels.
img

@julienduroure
Copy link
Collaborator

As requested in issue template, please indicate what version you are testing?
Some recent fix has been merge, so it may be solved in recent builds.

Also providing a test case file will help saving time. I know that we can recreate it from you screenshot, but having a test case directly usable same time :)

@scurest
Copy link
Contributor

scurest commented Oct 1, 2020

Cf #1068

@dmitri-fm
Copy link
Author

So it could be a problem with channel split?
I will try to make some tests later...

@j-conrad
Copy link

j-conrad commented Oct 1, 2020

Possibly related to #1219?

@scurest
Copy link
Contributor

scurest commented Oct 1, 2020

Oh, different UV maps. I thought the problem was the channel splitting.

It isn't possible to use different UV maps (or samplers, or texture transforms) for base color and alpha in glTF. There was another issue about this today: #1230.

A warning is already printed to the console about the sampler bit:

WARNING: More than one shader node tex image used for a texture. The resulting glTF sampler will behave like the first shader node tex image.

@dmitri-fm
Copy link
Author

A warning is already printed to the console about the sampler bit:

So it gives a warning and generates a wrong texture?
Maybe just export single color texture?

@scurest
Copy link
Contributor

scurest commented Oct 2, 2020

Maybe just export single color texture?

What does that mean?

@julienduroure
Copy link
Collaborator

No answer from the user since 1 month
Maybe we can add a more visible warning (in popup like suggested in another ticket for another warning)?

@donmccurdy
Copy link
Contributor

I don't think there is any way for the exporter to fix this — in general it would be nice if we could show more user-visible warnings when we detect that something won't export correctly, but (without a clear mechanism to do that) I'm not sure we need to keep this issue open.

@julienduroure
Copy link
Collaborator

Closing this ticket, as there is no bug here.
About better warning, this will be handled somewhere else. No need to keep this ticket open for that

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

No branches or pull requests

5 participants