Update for Bevy v0.17

[adrien-bon]

bevy-related dependencies

Migration guide : https://bevy.org/learn/migration-guides/0-16-to-0-17/

Name	Status	PR / Branch / Release
bevy	✅	0.17.2
bevy_ecs_tilemap	✅	0.17.0
bevy_rapier2d	On-going PR	dimforge/bevy_rapier#678 dimforge/bevy_rapier#680
avian2d	✅	0.4.0
bevy_inspector_egui	✅	0.34.0
iyes_perf_ui	On-going PR	IyesGames/iyes_perf_ui#35

bevy_ecs_tiled TODO list

• build with default features
• build with physics / avian features
• build with physics / rapier features
• build with user_properties feature
• check all examples are working (see below)
• upate documentation / documentation examples
• migration guide
• push to main + official release

Examples list

• map_anchor
• map_basic
• map_events
• map_parallax
• map_reload
• map_settings
• map_spawn_delay
• orientation_hexagonal
• orientation_isometric
• orientation_orthogonal
• physics_avian_controller
• physics_avian_orientation
• physics_avian_settings
• physics_custom
• physics_rapier_controller
• physics_rapier_orientation
• physics_rapier_settings
• properties_basic
• world_basic
• world_chunking

[adrien-bon]

Merged #148 into dev
Waiting for remaining dependencies to update and release an official version before publishing

[chpio]

Avian integration for objects seems to be buggy. Using current dev branch #081651ba12d33cbed7e60abe458683188a0b6def

correct, bevy-16 (code):

wrong placement of the collider, bevy-17 (code):

[adrien-bon]

I encountered the same issue when porting physics example: objects collider were all messed up.
To fix that, I now attach the RigidBody on the collider parent, ie. the object layer, and not on the collider itself.
See the example here.

Since I did not change the tilemap hierarchy, I assumed Avian changed behaviour and that we cannot attach a RigidBody to a collider entity anymore, but I may be wrong here.
Would need more time for investigation.

[chpio]

Is there a reason, why the tile-colliders aren't affected, but object-colliders are?

[adrien-bon]

I belive that's because objects usually have a non-default Transform, contrary to tiles layer.
IIRC, the issue was the Transform on the collider entity "negated" the Transform from the parent object, resulting in an overall position of (0, 0).
I definitelly need to spend more time on this to get an answer.