-
Notifications
You must be signed in to change notification settings - Fork 7.1k
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
DynamicLayer - wrong bounds with scrollFactor #3893
Comments
The issue is the tile culling (rather than the scrollFactor) because it was assumed that the LayerData Just pinging @mikewesthad - can you see anything wrong with the current approach in https://github.com/photonstorm/phaser/blob/master/src/tilemaps/components/CullTiles.js ? It passes whatever I throw at it, but there's so many weird edge-cases in tilemaps who knows. |
This did not fully fix the issue. Open same example, add this line:
Same thing happens. |
This is taking up far too much time, so, for now, I'm disabling culling entirely on a layer if you have a scroll factor <> 1. Renders fine and will do for now. |
I can take a look at cull tiles tomorrow and see if anything jumps out. Edit: Yeah, what you did with disabling culling entirely for now seems reasonable. |
Seems to work fine in v3.12.0-beta2 :) |
Test steps:
Open and run this example:
http://labs.phaser.io/edit.html?src=src/game%20objects/tilemap/tests/visual%20culling%20check.js
Look at the small red, pink and yellow tiles. Move camera right. They disappear.
Any ideas why the bounds are not computed correctly? As I test that on different Phaser versions, it seems to be fine in 3.6, but broken in 3.7.1 and above.
The text was updated successfully, but these errors were encountered: