Difference between revisions of "Common Bugs"
m
Typo: "pathrid" -> "pathgrid"
imported>Kivan m (Changed header) |
imported>Kivan m (Typo: "pathrid" -> "pathgrid") |
||
Line 125: | Line 125: | ||
Another workaround (works also on other 'unmovable' objects), when you get the object at the destination, is to [[Disable]] the object in one frame, [[Reset3DState]] in the next frame and [[Enable]] it in the third frame. The object will flicker, though. | Another workaround (works also on other 'unmovable' objects), when you get the object at the destination, is to [[Disable]] the object in one frame, [[Reset3DState]] in the next frame and [[Enable]] it in the third frame. The object will flicker, though. | ||
=== MoveTo for Actors may require | === MoveTo for Actors may require pathgrid === | ||
In some situations, using MoveTo on an Actor may ''appear'' to not work right unless the destination has a valid pathgrid to guide them. The symptom of this problem is that the MoveTo appears to work normally, but the Actor remains at the target only for a few seconds, then is moved to a nearby pathgrid in the same cell. The solution is to make sure the target area for a MoveTo on an Actor has a valid pathgrid, using World...Edit Cell Grid Path in the Construction Set. This isn't really a problem with MoveTo, but it can seem to be such until you realize the underlying cause. | In some situations, using MoveTo on an Actor may ''appear'' to not work right unless the destination has a valid pathgrid to guide them. The symptom of this problem is that the MoveTo appears to work normally, but the Actor remains at the target only for a few seconds, then is moved to a nearby pathgrid in the same cell. The solution is to make sure the target area for a MoveTo on an Actor has a valid pathgrid, using World...Edit Cell Grid Path in the Construction Set. This isn't really a problem with MoveTo, but it can seem to be such until you realize the underlying cause. | ||
[[Category:Troubleshooting]] | [[Category:Troubleshooting]] |