`CameraComponent.follow` follows the local position of a nested target
メンテナーはふだん 1 日以内に返信
評価
この issue はまだ評価されていません。
説明
What happened?
FollowBehavior moves its owner towards target.position (follow_behavior.dart#L55-L58), which is the target's position relative to its parent. When the target is a child of another PositionComponent, that isn't where the target is in the world, so CameraComponent.follow points the camera at the wrong place.
For example, with a knight that is a child of a moving platform and stands at (32, 30) on it, the camera looks at (32, 30) in the world, wherever the platform is. As the platform moves, the camera stays where it is and the knight leaves the screen. follow(target, snap: true) has the same problem, since it sets the viewfinder's position to target.position too (camera_component.dart#L389).
The same happens when a FollowBehavior is used between two components with different parents, e.g. a follower in one container following a target in another.
What do you expect?
The camera follows the target wherever it is in the component tree, as it does for a direct child of the world.
How can we reproduce this?
- Add a
PositionComponent(the platform) to the world, and move it. - Add the component to follow as a child of the platform.
- Call
camera.follow(knight). The camera follows the knight's position on the platform, not its position in the world.
What steps should take to fix this?
FollowBehavior will convert the target's position into the coordinate system of the owner's position when the target is a PositionComponent with another parent than the owner: into world coordinates through absolutePosition for an owner that isn't a PositionComponent, such as the camera's Viewfinder, and through absoluteToLocal and positionOf for a PositionComponent owner. When the target and the owner have the same parent, target.position is used as before. CameraComponent.follow will use the same position for snap.
Targets that aren't PositionComponents, such as a PositionProviderImpl, are followed at their position as given, as before. Until the fix is released, a nested target can be followed with camera.follow(PositionProviderImpl(getValue: () => knight.absolutePosition)).
Do have an example of where the bug occurs?
import 'package:flame/components.dart';
import 'package:flame/game.dart';
import 'package:flame/palette.dart';
import 'package:flutter/widgets.dart';
void main() => runApp(GameWidget(game: ReproGame()));
class ReproGame extends FlameGame {
@override
Future<void> onLoad() async {
world.add(RectangleComponent(size: Vector2.all(2000)));
final platform = MovingPlatform(position: Vector2(100, 100));
final knight = RectangleComponent(
position: Vector2(32, 30),
size: Vector2(16, 28),
anchor: Anchor.bottomCenter,
paint: BasicPalette.red.paint(),
);
world.add(platform..add(knight));
camera.follow(knight, snap: true);
}
}
class MovingPlatform extends RectangleComponent {
MovingPlatform({super.position})
: super(size: Vector2(64, 40), anchor: Anchor.center);
@override
void update(double dt) {
position.x += 100 * dt;
}
}
https://github.com/user-attachments/assets/eb723755-e2dc-4399-aaae-994319cf2c19
Expected: the red knight stays at the center of the screen while the platform carries it. Actual: the camera stays at (32, 30) and the knight moves off the screen.
Relevant log output
Nothing is logged or thrown.
Execute in a terminal and put output into the code block below
[√] Flutter (Channel stable, 3.50.0, on Microsoft Windows [Version 10.0.22631.6199], locale en-US)
• Flutter version 3.50.0 on channel stable
• Framework revision ab2912035e (10 days ago), 2026-11-09 08:50:21 -0800
• Engine revision 371f77202a
• Dart version 3.14.0
• DevTools version 2.61.0
[√] Windows Version (11 Pro 64-bit, 23H2, 2009)
[√] Android toolchain - develop for Android devices (Android SDK version 36.1.0)
[√] Chrome - develop for the web
[√] Visual Studio - develop Windows apps (Visual Studio Community 2026 18.11.2)
[√] Connected device (3 available)
[√] Network resources
• No issues found!
Affected platforms
All
Other information
No response
Are you interested in working on a PR for this?
- I want to work on this
- 主要言語
- Dart
- スター
- 10.8k
- フォーク
- 1.1k
- 平均マージ
- 2日 4時間
- マージ済み PR(30日)
- 61
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
flame-engine/flame のほかの issue
-
Timer with tickCount stays finished after start() or reset()対応中かも @matthewalberto が今日担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 66/100
flame-engine/flame#4240 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
`ComponentPool` returns components to the pool while they are still in use, and loses components removed before mounting対応中かも @ufrshubham が 18 日前に担当しました。 オープンbug
flame-engine/flame#4191 · 担当者 1 名 ·
メンテナーはふだん 1 日以内に返信
-
Move the flame_studio debugging features to flame_devtools対応中かも このイシューにリンクされたプルリクエストがオープン中、またはマージ済みです。 オープンenhancement
難易度 5/5 1週間以上 初心者へのやさしさ 35/100
flame-engine/flame#4176 ·
メンテナーはふだん 1 日以内に返信
-
discussion enhancement
難易度 5/5 1週間以上 初心者へのやさしさ 25/100
flame-engine/flame#4175 ·
メンテナーはふだん 1 日以内に返信
-
enhancement
難易度 5/5 1週間以上 初心者へのやさしさ 35/100
flame-engine/flame#4174 ·
メンテナーはふだん 1 日以内に返信
flame-engine/flame の issue をすべて見る
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 74/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
メンテナーはふだん 2 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
spotiflacapp/SpotiFLAC-Mobile#935 ·
-
documentation
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
chriskelly/wish-together#193 ·
メンテナーはふだん 1 日以内に返信
-
area: player feature request
難易度 2/5 1〜3時間 初心者へのやさしさ 65/100