Timeline for Why the MoveTowards make the transform moving nonstop?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 12, 2022 at 15:06 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Feb 12, 2022 at 15:03 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Oct 15, 2021 at 15:00 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jun 17, 2021 at 13:01 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| May 18, 2021 at 12:37 | answer | added | ShoulO | timeline score: 0 | |
| May 15, 2021 at 23:52 | comment | added | DMGregory♦ | Note that when you move an object with its transform, instead of a rigidbody, that's handled as a teleportation. The object is removed from the physics scene (calling OnTriggerExit if the object is currently overlapping any applicable colliders), then re-added again (calling OnTriggerEnter if applicable). So these teleports every frame could be calling OnTriggerExit again and again, ratcheting up your target position every time... | |
| May 15, 2021 at 23:13 | history | asked | Daniel Lip | CC BY-SA 4.0 |