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

Manual Content: Manual incorrectly says that precise per frame collision masks have a different bounding box per subimage #7735

Closed
KormexGit opened this issue Sep 22, 2024 · 1 comment
Assignees
Labels
docs-bug GameMaker Manual Bugs

Comments

@KormexGit
Copy link

KormexGit commented Sep 22, 2024

Description

On the manual page for the sprite editor, under the collision mask section, is the following:
"Finally you can set the Bounding Box limits for the mask. The bounding box is the name given to the rectangular area that the sprite mask fits in. Only pixels inside this bounding box are used for the mask and will be involved in collision checking, and by default this is automatically computed, taking the alpha tolerance into account. If you have "precise (per frame)" checked then this will be separate for each sub-image too."

The bolded part is not actually true, manual mode precise per frame masks use the same bounding box for every subimage.

GameMaker_fPOeI2TlBx.mp4

Even if you use automatic mode so that each subimage has a different mask, bounding box values are still the same between all frames in-game.

Manual Link

https://manual.gamemaker.io/monthly/en/index.htm#t=The_Asset_Editors%2FSprites.htm

@KormexGit KormexGit added the docs-bug GameMaker Manual Bugs label Sep 22, 2024
@gnysek
Copy link
Contributor

gnysek commented Sep 23, 2024

Only pixels inside this bounding box are used for the mask

For me:

  • precise = pixels in bounding box in FIRST frame
  • precise per pixel = pixels in bounding box in CURRENT frame

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs-bug GameMaker Manual Bugs
Projects
Status: Ready for QA
Development

No branches or pull requests

3 participants