Closed Jackymancs4 closed 11 months ago
I don't remember the conversation. why is changing? because there might not be an entity named target? feels like
Could targetComponent also be a referenceParameter of RobotComponent?
I don't remember the conversation.
Wasn't really a conversation. Just me mentioning it:
I'm also experimenting with a TargetComponent, because referencing the entity by name just feels wrong. And a SoftTargetComponent, with just revert its pose to the last validoune once the Jocobian goes crazy with "Bad inverse Jacobian. Singularity?"
why is changing? because there might not be an entity named target?
Semantics mainly. Since the target entity (referenced only by name) has special behavior (like the ability to move or destroy an arm) I think it should be referenced by a type.
This way I can have target1 and target2 and have the arm gravitate from one to the other by disabling them.
Could targetComponent also be a referenceParameter of RobotComponent?
Doesn't feel ergonomic, but I should try it to say.
I'll rebase this onto master. After that, I'll try to get a vehicle to drive until it reaches the target, using a boid-like algorithm.
Stale pull request message
Briefly discussed on the Discord channel.
This PR add a TargetComponent to identify which entity should be the target of the robot.