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

Textures in model-viewer - completely black #736

Closed
mischoko opened this issue Aug 31, 2019 · 16 comments
Closed

Textures in model-viewer - completely black #736

mischoko opened this issue Aug 31, 2019 · 16 comments
Assignees
Milestone

Comments

@mischoko
Copy link

I've been noticing an issue with model-viewer displaying .gltf models with pure black texture instead of their default diffuse. I haven't tested the .usdz yet.
Is this on my end or is that a global issue?

Thanks

astro_bug

@cdata
Copy link
Contributor

cdata commented Sep 3, 2019

Thanks for reporting @mischoko . It looks like this may be a bug, as we have received another report in #679 (comment) suggesting that some models have regressed.

If you could help us out, our original demo at https://model-viewer.glitch.me/ does not exhibit the problem. Could you share the model and <model-viewer> configuration that reproduces this problem?

Also, if you can share the browser and hardware you took that screenshot on, that would be very helpful as well 🙏

@mischoko
Copy link
Author

mischoko commented Sep 3, 2019

Hmm, to give you a 100% answer I will have to check all my devices both iOS and Android. As far as I'm able to check the issue at the moment, I can tell that one of my desktops with Chrome v. 76.0.3809.132 is having this black-material bug even with the astronaut demo. However, my Android Phone with the exact same version of Chrome seems to be doing just fine.
Tomorrow I'll quadruple-check with my other desktops and mobile devices to get a bit of broader analysis.

@cdata
Copy link
Contributor

cdata commented Sep 3, 2019

Thanks for that detail @mischoko . Given what you have described, it sounds like the bug could be hardware dependent. If you can share any details of the GPU in your desktop, that would be very helpful.

Also, could you share what model your Android phone is?

@mischoko
Copy link
Author

mischoko commented Sep 3, 2019

I've done a quick check on my other PC via Teamviewer and as you have mentioned, it seems to be a problem of this particular hardware setting. The Android is Honor 7A.

As for my setup at the moment - it's just a random conglomerate of pieces I threw together before I finish my main build. It does not even have a proper graphics card. I run it on in-built Intel HD 4600. Also, Win 7 if that's relevant in any way.

@cdata
Copy link
Contributor

cdata commented Sep 3, 2019

That's very helpful info, thanks @mischoko !

@cdata cdata added this to the v0.6.1 milestone Sep 3, 2019
@mischoko
Copy link
Author

mischoko commented Sep 3, 2019

@cdata No problem, I'll get you an update tomorrow when I get it tested on other devices as well.

@mischoko
Copy link
Author

mischoko commented Sep 4, 2019

Alright, I've done some testing with 3 Samsungs (no idea about the chrome version or the phones themselves) 1 iPhone X, and 1 Honor 6A - everything worked fine. Also iPad pro 2017 and 2018 both OK on Safari and Chrome. Other two desktops of unknown hardware configurations - OK.

So I think it's safe to say that it might very well be an issue with my hardware in the PC I mentioned in the previous comment.

@AytoMaximo
Copy link

If you could help us out, our original demo at https://model-viewer.glitch.me/ does not exhibit the problem. Could you share the model and <model-viewer> configuration that reproduces this problem?

I'll try to share some information too. As I've already mentioned in #679 my device (Xiaomi Redmi 4A) was previously rendering black objects, but in the case of model-viewer.glitch.me there is no object visible at all.

In our own case we're using the following config:
<model-viewer ar src="https://237529.selcdn.ru//awespace/product/6190/8786.glb" alt="3d model Faradise" auto-rotate camera-controls background-color="#ffffff" ios-src="https://237529.selcdn.ru/faradise/product/6190/8786.usdz" ></model-viewer>

And it's black everywhere (PC, iOS..) and also not visible at all on Xiaomi device.

@cdata cdata modified the milestones: v0.6.1, v0.7.0 Sep 6, 2019
@elalish
Copy link
Contributor

elalish commented Sep 9, 2019

I'm closing this as no repro, and since #679 has also been resolved as unrelated. Feel free to reopen if you find any standard hardware that reproduces it.

@elalish elalish closed this as completed Sep 9, 2019
@androidparth90
Copy link

androidparth90 commented Oct 30, 2021

I am facing the same issue with one of my models (.glb). below is the link to download the same. Can this one be re-opened please?

https://drive.google.com/file/d/1H_xq6xqd7s9jht8i1ZmIvZXe11NflPeB/view?usp=sharing

my model appears like this

Screen Shot 2021-10-30 at 2 07 44 PM

My code

<model-viewer 
seamless-poster shadow-intensity="1"
data-name="sample model"
ar
background-color="#ffffff"
ar-modes="scene-viewer quick-look"
src="assets/models/sample.glb" 
ios-src="assets/models/sample.usdz"
alt="A 3D model" auto-rotate camera-controls>
</model-viewer>

@elalish
Copy link
Contributor

elalish commented Nov 1, 2021

No, black models can be from any of dozens of unrelated problems. Many are simply incorrectly exported GLBs. Please search the open discussions and if you can't find anything helpful, file an issue with the entire template filled out so we can determine what the problem is.

@SilvioDiMatteo
Copy link

SilvioDiMatteo commented Nov 11, 2021

I'm facing this issue too, on iOS, in the 3D view, some parts of the model are total black, if I switch to AR it is totally correct.
The weird thing is that if I reload the scene, the model starts working properly in the 3D view too.

Hardware: iPhone 11
OS: iOS 15.0.2

@samaneh-kazemi
Copy link
Collaborator

samaneh-kazemi commented Nov 11, 2021

@SilvioDiMatteo Hi, this is an iOS issue and we're waiting for them to fix it.
As a workaround you can pin v1.8 until the fix comes, e.g.

 <script type="module" src="https://unpkg.com/@google/model-viewer@1.8.0/dist/model-viewer.min.js"></script>

@Tommyhuls
Copy link

@samaneh-kazemi
Any news on this issue? We are using meshoptdecoder and this seems to not work with v1.8...

@elalish
Copy link
Contributor

elalish commented Dec 8, 2021

There are open issues for this; unfortunately nearly all rendering bugs results in black pixels, so you can't assume any two issues are automatically related by looking at the render. The most recent is a Safari 15.1 bug, and there's a work around coming down in the next three.js release, which we'll pick up in our next release, probably in January.

@Udara-Sampath
Copy link

This also happened to me, I tried completely changing texture names and relinking them before exporting as .glb and it worked

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

9 participants