Advanced Texture bug

Bugs
1

Hi,
I have created two texts using advanced texture.
https://playground.babylonjs.com/#TMHF80#1052
I am saving the scene as babylon file.
But when I open the saved Babylon file in sandbox, the sandbox’s output is not matching with PG sample’s output.

PG

image
image808×595 21.6 KB

sandbox

image
image999×655 23.5 KB

Thanks
Gopinath Vellingiri

2

@msDestiny14 is our GUI expert and might have a look shortly

4

Wow. Great find!.

I did a check and downloaded the entire scene as a HTML and got no issues, woo! So looks like we got a boo boo somewhere in the Babylon file serialization. I’ll get to the bottom of it and let you know!

3 Likes
5

We have an issue for that now Advance Texture Bug, Babylon file appears to save incorrectly. · Issue #11605 · BabylonJS/Babylon.js (github.com), I’ll take a look at it next :slight_smile:

1 Like
7

Hi! Thank you for reporting this issue :slight_smile: Apologies for taking so long to investigate. Unfortunately we lost track of it with the holidays upon us. However, we have found the cause of the issue and we have a fix for you.

The root of the problem is that the serializer does not work well when objects in the scene share the same name. Object IDs are based off of names, so the loader can get confused about which object you’re pointing to. This can lead to incorrect material or texture assignment. A quick and dirty fix is to change two things:

  1. Make the names (and thus the IDs) of the meshes (the planes) distinct
  2. Make the IDs of the materials distinct. Changing the names isn’t enough, because the ID is generated upon creation. Unfortunately, the way that AdvancedDynamicTexture.CreateForMesh works at the moment, it will always create a material with a hard-coded name, inevitably leading to a collision if you call it more than once. But you can manually change the ID yourself.

I’ve made both changes in the PG here:
Size Plane Based on Dynamic Texture | Babylon.js Playground (babylonjs.com)

This can now export a correct .babylon file :slight_smile:

We are going to go in and fix these issues in the codebase, but in the meantime, this should solve your issue. Please let us know if you have more questions, and again, sorry for the late reply!

5 Likes
9

Fix is in PR right now: Serialization: Use unique IDs for materials and multimaterials by darraghjburke · Pull Request #11734 · BabylonJS/Babylon.js (github.com)

5 Likes
10

Fix is merged :slight_smile:

4 Likes
12

Thanks a lot.

1 Like