Make the campus routes walkable #49
Labels
No labels
animation
audio
blocked
bug report
controversial
documentation
easy
feature request
hard
medium
multiplayer
physics
ui
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
elsie/liuverse#49
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
MazeMap carries 690 POIs that are outdoor wayfinding routes, not
places:
Konstrunda Vallais LiU's public art round, and the sculpture-trail issue isone of these.
Stora rundanis the campus loop.En kvart bland djurenis aquarter-hour walk. They are points along a route, and the route itself is not in
the data -- only the points, in order.
Which means the route has to be reconstructed from its own points, in POI-id
order, by walking the sequence. That is a real inference and worth doing
carefully: it is the same shape as the schematic circulation fallback (generate
a plausible thing from the outline we were given), but here the generator is the
survey's own point list rather than a footprint.
A route you can follow, with the artwork and courtyards along it, is the single
best reason to walk a campus that you could otherwise fly over.
Related
Reconstructing a polyline from an ordered POI list is plausible; calling the result "walkable" is the overreach. The engine has no navmesh — collision is a 2-D wall predicate on substeps — so this would not give a route the player can follow, only a line drawn through the woods. Scope it to drawing the route ribbon and its markers, and let the player follow it visually. If you want guidance, a breadcrumb line from the player to the next POI is honest and much cheaper. Don't promise turn-by-turn.
Recontext: there is no navmesh or routing code in
liuverse-world; collision is the 2-Dcan_walk_towall predicate. Reconstructing a polyline from the ordered POI ids would only produce a line to draw, not a route the player can actually follow. Scope this to the route ribbon and its markers, optionally with a breadcrumb to the next POI; do not promise turn-by-turn guidance.