Sign in to follow this  
fenomas

Has something changed with mesh merging?

Recommended Posts

Hi,

I recently updated my Babylon files to the latest nightlies. Since doing that, where my scene used to contain a few hundred meshes called "foo", it now contains several hundred more meshes called "foo_merged".

From grepping the source, it seems that these must be coming from BABYLON.Mesh.MergeMeshes, but as near as I can tell that should only get called by functions related to SceneOptimizer stuff, which I've never looked at and am not (consciously) using.

Has something changed (in the last few months) whereby the scene optimizer or some kind of mesh merging might be getting done automatically?

Thanks!

Share this post


Link to post
Share on other sites
1 hour ago, Deltakosh said:

Is it an problem for you? You can still provide your own mesh container if you want

I think you misunderstood my post. I don't know where these meshes came from, or whether they're containers, or what they're for. All I did was update BJS, and my scene had a few hundred new meshes with names like "xyz_merged". I'm asking: is this happening on purpose? If so, what's going on?

Share this post


Link to post
Share on other sites
2 hours ago, Deltakosh said:

It is on purpose :) If you want to mergeMEshes and do not provide a container then we will create it for you

 

Are you using MergeMeshes? Or perhaps the SceneOptimizer?

Okay, third try :) 

 I have never heard of MergeMeshes or SceneOptimizer. I don't know what they do.

I guess, based on the "foo_merged" meshes, that MergeMeshes is getting called in my scene, but I'm not calling it. So I'm asking, was there a recent change in BJS that would call this automatically, and if so, what sort of change was it?

 

Any further info would be great - a link to past discussion, or whatever. Thanks!

Share this post


Link to post
Share on other sites

Update: I found where one of my dependencies is calling MergeMeshes :)

So the question is, can anyone give me a hint what (if anything) has changed with MergeMeshes? (so I can figure out if my dependency needs to be updated)

Thanks!

Share this post


Link to post
Share on other sites

So you called it :)

We did some updates to add support for submeshes. Before the merge cleared all submeshes and returned one single submesh. Now you have the option (off by default) to subdivide the merge and create one submesh for every original mesh

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.