samme

```js function preload() { this.load.tilemapTiledJSON( "map", "assets/tilemaps/maps/multi-tileset-v12.json" ); this.load.once( "filecomplete-tilemapJSON-map", function (key, type, data) { this.load.setPath("/assets/tilemaps/maps/"); for (var tileset of data.data.tilesets) { this.load.image(tileset.name, tileset.image); } }, this ); } ```...

This may be #6474 . GIDs are "global" because they're unique within the tilemap (not a tileset). You assign GIDs with the `gid` argument in [addTilesetImage()](https://newdocs.phaser.io/docs/3.60.0/focus/Phaser.Tilemaps.Tilemap-addTilesetImage). You can make GIDs...

I think that the description for [Phaser.Types.Animations.AnimationFrame.duration](https://newdocs.phaser.io/docs/3.70.0/Phaser.Types.Animations.AnimationFrame) is wrong and it should be like [Phaser.Animations.AnimationFrame#duration](https://newdocs.phaser.io/docs/3.70.0/focus/Phaser.Animations.AnimationFrame-duration).

I think 2e4b43b is technically a breaking change, because [AnimationFrame#duration](https://newdocs.phaser.io/docs/3.70.0/focus/Phaser.Animations.AnimationFrame-duration) did correctly describe Phaser's behavior.

Please try https://github.com/phaserjs/phaser/pull/6793

It's `add.spine()` that adds to the "spineTextures" cache and the Texture Manager, and the Spine plugins prefix texture keys differently. So maybe the plugins could handle this better.

Now removes all Spine assets.

Someone reported [a similar issue in Phaser 3](https://phaser.discourse.group/t/weird-text-render-problem/13146).

Hi. I'd assumed that in v3.16 people would just use the built-in Scale Manager instead of the plugin. I haven't tried it yet myself so I don't really know.

Looks like a direct-control platform's `body.prev` is identical to its `body.position` during the collision, so the friction vector is (0, 0).