KhronosGroup / glTF

glTF – Runtime 3D Asset Delivery
Other
7.19k stars 1.14k forks source link

Undefined behaviour of light (and audio) under viewer scale #2162

Open hybridherbst opened 2 years ago

hybridherbst commented 2 years ago

A growing usecase of glTF is the use for e-commerce products and lightweight interactive experiences, especially on mobile and with Augmented Reality in mind.

While working in this area for many projects, we found that currently, some behaviours are entirely undefined in the glTF spec and thus all viewers either do it obviously wrong (because it's nowhere mentioned) or have differing behaviour.

Ideally, there would be a non-normative section in the glTF spec (or similar) that talks about behaviour under viewer scale, encourages extensions where that matters to explain how they assume to work, and thus serves as a rough guiding principle. I don't think this would need to be normative right now, but I imagine that in the future with more extensions that range into interactivity and spatial cases, this is becoming more of an issue.


Consider the typical scenario of placing a model in AR with model-viewer, and the model has spatial audio. Should scaling the model down to 10% of the size

Unfortunately such considerations were omitted from lighting in glTF, and thus lighting in AR is often broken right now.

To explain why that's not trivial, here's my take:


Here's some examples from

https://user-images.githubusercontent.com/2693840/121874453-a87a8900-cd07-11eb-9191-7b7ad9bf30b9.mp4

Note that when placing the model in AR, the effect is correct; but when scaling the model, the appearance is that the lights get brighter and closer to each other! That's not what you want when you're scaling down a little architecture model of a city with some street lights!

And a live problematic file that shows that artistic intent gets immediately lost upon viewer scale

References

hybridherbst commented 11 months ago

@DrX3D I think with more and more AR and VR usecases where glTF is used, it would be great to get some guidance on this topic. Just delegating to implementors to individually figure it out has proven problematic, as essentially all I heard is "it's undefined in glTF, why should we care". There could at least be a note ackowledging the problem and suggesting what solutions might be.