Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix SubMesh IsGlobal #12529

Merged
merged 2 commits into from
May 16, 2022
Merged

Conversation

BlakeOne
Copy link
Contributor

@BlakeOne BlakeOne commented May 16, 2022

Currently IsGlobal returns true if the subMesh has all the vertices of the mesh but it should check if the subMesh also has all the indices of the mesh IMO.

Because otherwise the mesh's full bounding info is returned by getBoundingInfo when the subMesh has all the vertices but only some of the indices of the whole mesh. E.G. the subMeshes created by CreateTiledGround, which shouldn't return the bounding info for the whole mesh but currently are.

Forum discussion w/ test PGs: https://forum.babylonjs.com/t/find-or-define-center-point-of-submesh/30400/3

@azure-pipelines
Copy link

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

@azure-pipelines
Copy link

@BlakeOne
Copy link
Contributor Author

Should it all be on one long line instead? It used to say what the formatting problem/solution was but now I can't find that info anymore, for the last few PRs that had formatting errors...

@rdw-software
Copy link

Should it all be on one long line instead? It used to say what the formatting problem/solution was but now I can't find that info anymore, for the last few PRs that had formatting errors...

You can run npm run format:fix to let prettier resolve the formatting issue :)

The error is also displayed in the logs, though it could be difficult to find. Or you can see it by running npm run format:check.

@BlakeOne
Copy link
Contributor Author

BlakeOne commented May 16, 2022

The error is also displayed in the logs, though it could be difficult to find.

I used to be able to find what the particular formatting issue was (and on what line), now all I can find out is that there's a formatting error in the file without the needed details to fix it, ever since the build/validation system changed recently I think.... But I'll try running the prettier locally to see if it fixes the issue.

Okay I ran the format fixer locally and re-committed, one long line it is then... Thanks! :)

@azure-pipelines
Copy link

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

@azure-pipelines
Copy link

@RaananW RaananW merged commit 1af21e4 into BabylonJS:master May 16, 2022
@BlakeOne BlakeOne deleted the BlakeOne-Fix-SubMesh-IsGlobal branch May 16, 2022 15:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants