Difference between revisions of "Common Bugs"
→MoveTo Oddities: Added note about needing pathgrid at target for MoveTo with Actor.
imported>QQuix (→MoveTo on Containers: Added a common workaround) |
imported>Syscrusher (→MoveTo Oddities: Added note about needing pathgrid at target for MoveTo with Actor.) |
||
| Line 122: | Line 122: | ||
Another workaround (works also on other 'unmoveable' 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, thou. | Another workaround (works also on other 'unmoveable' 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, thou. | ||
=== MoveTo for Actors may require pathrid === | |||
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]] | ||