Difference between revisions of "NAVCUT"

Jump to navigation Jump to search
22 bytes added ,  19:16, 30 September 2017
m
Added to the Navmesh category
imported>DavidJCobb
m (→‎Overview: link to Navmesh category)
imported>DavidJCobb
m (Added to the Navmesh category)
Line 32: Line 32:
* Despite some of the issues listed in the "Limitations" section above, a NAVCUT box doesn't need to be thicker than a character model ''if'' the box completely cuts a navmesh into two pieces.
* Despite some of the issues listed in the "Limitations" section above, a NAVCUT box doesn't need to be thicker than a character model ''if'' the box completely cuts a navmesh into two pieces.
* NAVCUT volumes have collision generated at run-time. The engine only does this properly if they use the hardcoded ''CollisionMarker'' base form. Collision primitives placed in the Creation Kit will always be ''CollisionMarker''s.
* NAVCUT volumes have collision generated at run-time. The engine only does this properly if they use the hardcoded ''CollisionMarker'' base form. Collision primitives placed in the Creation Kit will always be ''CollisionMarker''s.
[[Category:Navmesh]]
Anonymous user

Navigation menu