Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Materials with emissiveIntensity under 1 are exported with an emissive way too bright with GLTFExporter
See original GitHub issueStarting with r129 and the modification for #21849 the emissiveFactor exported with GLTFExporter ignores emissiveIntensity
I’m not sure to undestand exactly why the emissiveIntensity is now ignored completely at GLTF export, but it broke something for us. Materials with an emissiveIntensity that is between 0 and 1 are now exported like their emissiveIntensity would be 1 on three <= r128, so they’re way too bright.
Shouldn’t the exporter rather multiply by the emissiveIntensity then clamp the result or something ?
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I’d be fine with scaling and then clamping, yes. FWIW there is a proposal upcoming (still a draft though) to allow an “emissive strength” parameter in glTF as well: https://github.com/KhronosGroup/glTF/pull/1994.
I think the exporter should instead scale
emissivebyemissiveIntensity– but limit the scaling, so no color component exceeds one.Doing so will prevent hue shifts. It will also prevent issues like this one from being raised.
Alert with an appropriate warning if the intensity was limited during export.