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.
PMREMGenerator EnvMaps only work with one renderer
See original GitHub issueDescription of the problem
I don’t know if it is expected or if I miss something, but it looks like the envmap textures generated by PMREGenerator and the renderer specified at that time cannot be re-used with another renderer.
In this example, the envmap is generated using renderer. If the scene is rendered with renderer2, it doesn’t work.
Replace var pmremGenerator = new THREE.PMREMGenerator( renderer );
by var pmremGenerator = new THREE.PMREMGenerator( renderer2 );
on line 49 to check the difference.
Three.js version
- Dev
- r115
Browser
- All of them
OS
- All of them
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (2 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
@sciecode I see this a bit different since the issue I linked was focused about the valid combinations of
PMREMGeneratorandWebGLRenderer. Hence, I think this discussion belongs to it.By the way, this is not a duplicate of #18976.
This is about sharing a texture between WebGL contexts, which is impossible due to WebGL limitations. The other issue was about using instances of
PMREMGeneratorwith multiple contexts and having the textures replaced because of scoping, which was fixed with your PR.Issue should still be closed, because there’s nothing we can do about it. But I just wanted to be clear about it.