Texture swap incorrectly (?) accounted for when exporting modified .babylon scene from Sandbox

Questions
,
4

No problem @sebavan , thanks for all the hard work! :slight_smile:

I’ve been playing with the Sandbox some more tonight, and I have had similar issues. I will report my findings here, as it feels all this might be related.

This time I was trying to downgrade the quality of a texture present in the same .babylon file used so far.

Steps in FireFox 78.14.0esr (CentOS 8.4)

  1. import original .babylon file,
  2. select texture to be modified in scene explorer,
  3. under ‘preview’, click ‘edit’,
  4. change both width and height, and click ‘resize’,
  5. click ‘save’; this produces an empty PNG file, but with the right dimension,
  6. close texture editor; the inspector shows the updated texture dimensions,
  7. click ‘edit’,
  8. click ‘save’; this time the expected texture file is produced (right dimensions, not empty),
  9. under ‘tools’, click ‘export to babylon’; the exported file does not take into account the texture modification.
  10. add .png extension to texture file, which for some reason was missing in FF,
  11. under ‘preview’, click ‘load texture from file’ and load the texture file created in step 8,
  12. Repeat step 9. This time the new .babylon file takes into account the texture modification.

Similar story in Chrome version 93.0.4577.82, except for the following:

  • the .png extension is added automatically,
  • once the correct PNG is generated (on second attempt in Chrome too), it is about twice as large as the file generated by FF.
  • this size difference seems to cascade once the files are imported back to the scene: when diff’ing the babylon scenes obtained in Chrome and FF, the ‘url’ field for the modified texture contains about twice the data in Chrome.

I cannot share the files that I am working on, but if you can’t reproduce the issue, let me know and I will try to produce a stripped down version of the original file.

I hope this helps! :slight_smile: