Search the Community

I'm currently working on a project that has both a live and development version, utilizing offline storage and .manifest files for all of my Scene objects. Everything works as expected until I run the old project after having just run the new one in Chrome, specifically. The latest versions of the .scene files are always loaded from the cache, despite the older version number in their .manifest files. I did some digging, and found this: Database.prototype._loadVersionFromDBAsync = function (url, callback, updateInDBCallback) { ... transaction.oncomplete = function (event) { if (version) { // If the version in the JSON file is > than the version in DB if (_this.manifestVersionFound > version.data) { _this.mustUpdateRessources = true; Notice that the version number comparison operator is >, not !=. Shouldn't the comparison be != to cover any changes to the .manifest file version, regardless of its age? I've changed this on my end, and all is well now.

Hi, We have a few questions concerning the cameraExposure and cameraContrast properties on PBRMaterial. Have these properties been lost during the update to 3.1 ? It would be something like this : https://playground.babylonjs.com/#JRCQTE#2 Here, the spheres have the same contrast and exposure. I think it was not the case before. Also, we love the new workflow for PBR (specular glossy and metallic roughness), but it does not expose this property at all. Is there a way to achieve this kind of result with the new workflow ? note : we kinda did it through material["_imageProcessingConfiguration"].contrast = v; But it tends to cause WebGL warnings (INVALID_VALUE: uniformBlockBinding: invalid uniform block index) and randomly overexpose our scene. Thanks a lot for your help ! We'd take any info you have about this properties, Best regards,