GLTFLoader: Scene hierarchy not consistant between Chrome and Firefox.
See original GitHub issueI just found out the order of children in a traverse ‘traverse’ loop in a (glb file):
object.traverse( function ( child ) {
//to something with child
});
is different on Chrome and on Firefox.
Actually, on Chrome, the order seem to be random ( is different each time the page is refreshed)
Tested with a glb file exported from blender, on Chrome & Firefox linux and window 10, with three 112
Is this a known issue or is there a work around for this?
using threejs 112 & GLTF loader as of today’s version : 2020/02/28
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:9
Top Results From Across the Web
GLTFloader not working in Firefox, Opera, Edge - three.js forum
Dear Reader, did build a scene with an animated object, using the GLTFloader. in Chrome it works in Firefox not, Edge also not, ......
Read more >Threejs does not load gltf model on chrome android
I am trying to display a simple GLTF 3d model in my website. It works on desktop Mac and windows as well as...
Read more >How actors are organized - Firefox Source Docs
They are organized in a hierarchy for easier lifecycle and memory management: once a parent is removed from the pool, its children are...
Read more >Build Course Boilerplate - React Three Fiber Tutorials
Now to start creating our working folders and files. Open a command/terminal prompt and create a new folder on your system somewhere. mkdir...
Read more >What's New | Babylon.js Documentation
Major updates · Infinite Morph Targets: When supported (WebGL2+) you are no more limited to 4 morph targets per mesh (Deltakosh) · Added...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Oh sorry I made PR #15587 including this fix but it had a response time impact and I didn’t have time to think how to resolve, and ended up closing the PR so far.
I think it’s good to first fix only this issue. IIRC I explained the root issue in #15561, not hard to fix. Please feel free to try.
Fixed via #25058.