When was 5.0.0 beta2?
I’m also having a merged meshes issue (with clones) since about 3 weeks. I remember it happened after a nightly update on a friday (I think 3 weeks ago). @RaananW is aware of it and said he would have a look into merged meshes next week. May be this can be added to it. May be it’s part of the same.
OK, well my problem occured as I said only about friday 3 weeks ago. Before that was working fine.
Edit: Apologies, time is running
From my files, the problem occured since February 26. If this can help track it.
Are yours @Deltakosh@RaananW now done with the fix of merged meshes? Should I return investigating (what was working prior to release of v5) or should I still wait for a fix to come? Thx,
Isn’t this going against backwards compatibility?
In 4.2 it only works without mesh.overrideMaterialSideOrientation = null;
but now in 5.2, it only works with mesh.overrideMaterialSideOrientation = null;
I checked using your PG.
Having upgraded Babylon three times, now I’m really afraid of it, because something always breaks.
Each time I wasted at least one to two days of unnecessary debugging. Then followed by several days waiting for the released fix to be on npm. Usually accompanied by dirty quick fixes while waiting (manually changing code in npm node_modules before bundling) in order to release to production.
I mean breaking changes between versions is normal, as long as they are clearly stated in Change logs, and without promising people that it’s backwards compatible.