New enableOfflineSupport property to avoid checking for .manifest

[davrous]

Hi guys,

 

 We often have this question: why does babylon.js generate a failing XHR request for this strange .manifest file? It's because it was the only way I've found to check if the user would like to cache into our IndexedDB layer the scene and/or the textures: http://doc.babylonjs.com/page.php?p=22231

 

 But it often generates confusion and some people are not interested in our offline features. We're currently working on a big project (top secret for now but to be launched by the end of the year) where the developers have requested to avoid having those XHR useless requests for them.

 

 I’ve just updated the code. I’ve added an enableOfflineSupport boolean property set to true by default (to keep the current default behavior for our users). If you’re set the value to false, we won’t query anymore for a .manifest file for potential IDB usage.

 

Usage:

 

        var engine = new BABYLON.Engine(canvas, true);

    engine.enableOfflineSupport = false;

 

                Both importMesh and load functions on our SceneLoader object are impacted. So, simply setting this boolean in your code should remove all failing .manifest XHR calls. I’ve pushed the update on our github repo. Files affected:

 

• https://github.com/BabylonJS/Babylon.js/blob/master/src/babylon.engine.ts

• https://github.com/BabylonJS/Babylon.js/blob/master/src/Loading/babylon.sceneLoader.ts

 

Bye,

 

David