3d-virtual-tour

Store route keys as progress, position, look target, and field of view, then interpolate with timed Hermite keys or a CatmullRomCurve3 spline. Use arc-length sampling for constant speed and quaternion slerp for orientation to avoid direction flips.

Use a navigation state machine where only one controller writes the camera per frame. Save the route coordinate and playback state before entering inspection, blend position and orientation during handoff, and restore the saved state on return.

Yes, but use linked panorama viewpoints rather than implying navigable geometric depth. Panoramic sources lack real 3D geometry, so free walking and collision-based movement are not applicable to that format.

Smooth curves can cut corners between collision-free keys even when waypoints are valid. Inspect the complete interpolated path including near-plane clearance against walls, ceilings, and doorframes, and place keys before, within, and after narrow openings.

No, OrbitControls alone does not provide a walkable interior. Free walking requires a first-person controller such as PointerLockControls with collision detection, floor following, and clearance checks constrained to walkable surfaces.