Why does a THREE.js gilt clone in another renderer slow down frame rate?












1














I have a gltf-scene added to my main render:



loader.load( 'models/model.gltf', function ( gltf ) {
...
scenes['game'].add( gltf.scene );
}


This works fine and I'm able to make clones without any issues:



loader.load( 'models/model.gltf', function ( gltf ) {
...
scenes['game'].add( gltf.scene );
var myClone = gltf.scene.clone();
scenes['game'].add( myClone );
}


But when I try to add the clone to a second renderer things start to get tricky:



loader.load( 'models/model.gltf', function ( gltf ) {
...
scenes['game'].add( gltf.scene );
var myClone = gltf.scene.clone();
scenes['inventory'].add( myClone );
}


The frame rate drops dramatically when both gilt scenes are within camera view on both renderers. I checked both objects and the seem unique in every way.
Does anyone know what's going on?










share|improve this question



























    1














    I have a gltf-scene added to my main render:



    loader.load( 'models/model.gltf', function ( gltf ) {
    ...
    scenes['game'].add( gltf.scene );
    }


    This works fine and I'm able to make clones without any issues:



    loader.load( 'models/model.gltf', function ( gltf ) {
    ...
    scenes['game'].add( gltf.scene );
    var myClone = gltf.scene.clone();
    scenes['game'].add( myClone );
    }


    But when I try to add the clone to a second renderer things start to get tricky:



    loader.load( 'models/model.gltf', function ( gltf ) {
    ...
    scenes['game'].add( gltf.scene );
    var myClone = gltf.scene.clone();
    scenes['inventory'].add( myClone );
    }


    The frame rate drops dramatically when both gilt scenes are within camera view on both renderers. I checked both objects and the seem unique in every way.
    Does anyone know what's going on?










    share|improve this question

























      1












      1








      1







      I have a gltf-scene added to my main render:



      loader.load( 'models/model.gltf', function ( gltf ) {
      ...
      scenes['game'].add( gltf.scene );
      }


      This works fine and I'm able to make clones without any issues:



      loader.load( 'models/model.gltf', function ( gltf ) {
      ...
      scenes['game'].add( gltf.scene );
      var myClone = gltf.scene.clone();
      scenes['game'].add( myClone );
      }


      But when I try to add the clone to a second renderer things start to get tricky:



      loader.load( 'models/model.gltf', function ( gltf ) {
      ...
      scenes['game'].add( gltf.scene );
      var myClone = gltf.scene.clone();
      scenes['inventory'].add( myClone );
      }


      The frame rate drops dramatically when both gilt scenes are within camera view on both renderers. I checked both objects and the seem unique in every way.
      Does anyone know what's going on?










      share|improve this question













      I have a gltf-scene added to my main render:



      loader.load( 'models/model.gltf', function ( gltf ) {
      ...
      scenes['game'].add( gltf.scene );
      }


      This works fine and I'm able to make clones without any issues:



      loader.load( 'models/model.gltf', function ( gltf ) {
      ...
      scenes['game'].add( gltf.scene );
      var myClone = gltf.scene.clone();
      scenes['game'].add( myClone );
      }


      But when I try to add the clone to a second renderer things start to get tricky:



      loader.load( 'models/model.gltf', function ( gltf ) {
      ...
      scenes['game'].add( gltf.scene );
      var myClone = gltf.scene.clone();
      scenes['inventory'].add( myClone );
      }


      The frame rate drops dramatically when both gilt scenes are within camera view on both renderers. I checked both objects and the seem unique in every way.
      Does anyone know what's going on?







      three.js cloning gltf






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 16 '18 at 20:37









      MasterMek

      61




      61
























          1 Answer
          1






          active

          oldest

          votes


















          0














          Having two renderers is very poor practice, performance-wise. It generates two WebGL contexts, consumes a lot more memory, and essentially negates any efficiencies that the GPU might want to implement. You can have multiple scenes, and multiple cameras, but don't use multiple renderers. You should share one renderer instead, with something like this:



          var renderer = new THREE.WebGLRenderer();
          var scene1 = new THREE.Scene();
          var scene2 = new THREE.Scene();
          var cam1 = new THREE.PerspectiveCamera();
          var cam2 = new THREE.PerspectiveCamera();

          update() {
          renderer.render(scene1, cam1);
          renderer.render(scene2, cam2);
          }





          share|improve this answer





















            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53345045%2fwhy-does-a-three-js-gilt-clone-in-another-renderer-slow-down-frame-rate%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            Having two renderers is very poor practice, performance-wise. It generates two WebGL contexts, consumes a lot more memory, and essentially negates any efficiencies that the GPU might want to implement. You can have multiple scenes, and multiple cameras, but don't use multiple renderers. You should share one renderer instead, with something like this:



            var renderer = new THREE.WebGLRenderer();
            var scene1 = new THREE.Scene();
            var scene2 = new THREE.Scene();
            var cam1 = new THREE.PerspectiveCamera();
            var cam2 = new THREE.PerspectiveCamera();

            update() {
            renderer.render(scene1, cam1);
            renderer.render(scene2, cam2);
            }





            share|improve this answer


























              0














              Having two renderers is very poor practice, performance-wise. It generates two WebGL contexts, consumes a lot more memory, and essentially negates any efficiencies that the GPU might want to implement. You can have multiple scenes, and multiple cameras, but don't use multiple renderers. You should share one renderer instead, with something like this:



              var renderer = new THREE.WebGLRenderer();
              var scene1 = new THREE.Scene();
              var scene2 = new THREE.Scene();
              var cam1 = new THREE.PerspectiveCamera();
              var cam2 = new THREE.PerspectiveCamera();

              update() {
              renderer.render(scene1, cam1);
              renderer.render(scene2, cam2);
              }





              share|improve this answer
























                0












                0








                0






                Having two renderers is very poor practice, performance-wise. It generates two WebGL contexts, consumes a lot more memory, and essentially negates any efficiencies that the GPU might want to implement. You can have multiple scenes, and multiple cameras, but don't use multiple renderers. You should share one renderer instead, with something like this:



                var renderer = new THREE.WebGLRenderer();
                var scene1 = new THREE.Scene();
                var scene2 = new THREE.Scene();
                var cam1 = new THREE.PerspectiveCamera();
                var cam2 = new THREE.PerspectiveCamera();

                update() {
                renderer.render(scene1, cam1);
                renderer.render(scene2, cam2);
                }





                share|improve this answer












                Having two renderers is very poor practice, performance-wise. It generates two WebGL contexts, consumes a lot more memory, and essentially negates any efficiencies that the GPU might want to implement. You can have multiple scenes, and multiple cameras, but don't use multiple renderers. You should share one renderer instead, with something like this:



                var renderer = new THREE.WebGLRenderer();
                var scene1 = new THREE.Scene();
                var scene2 = new THREE.Scene();
                var cam1 = new THREE.PerspectiveCamera();
                var cam2 = new THREE.PerspectiveCamera();

                update() {
                renderer.render(scene1, cam1);
                renderer.render(scene2, cam2);
                }






                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 16 '18 at 21:10









                Marquizzo

                5,51332043




                5,51332043






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53345045%2fwhy-does-a-three-js-gilt-clone-in-another-renderer-slow-down-frame-rate%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Biblatex bibliography style without URLs when DOI exists (in Overleaf with Zotero bibliography)

                    ComboBox Display Member on multiple fields

                    Is it possible to collect Nectar points via Trainline?