Welcome to the Splines discussion thread. You can use this thread to ask for help, share feedback, and have discussions about the Splines package. Introduction Splines provides a shared solution for path-based tooling, meaning: As an artist, you now have built-in ability to - Animate cameras, characters, particles or anything else along a path! - Create fences, walls, paths and other details that require placing many objects along a path - Easily build and modify tubes, wiring, and similar objects As an artist, you can expect same basic visuals, shortcuts, and tooling when working with any Spline-based features - no need to learn and re-learn As a tool/feature developer, you can use Splines as a base for your own solutions (for yourself, the Asset Store, etc) Resources Documentation Scripting API Changelog Requirements The minimum required Unity version is 2022.1 Getting started Download Unity 2022.1 or newer through the Hub. Open your project in Unity and go to Project Settings > Package Manager Go to Window > Package Manager. Search for "Splines" and install Use "GameObject > Spline > Draw Spline Tool ..." to begin creating your first Spline Current state Splines 2.0 is the currently available release, with numerous improvements vs 1.x: Ability to draw connected and disconnected branches More tangent controls and modes Ability to select and edit multiple spline elements simultaneously Default components for Animating, Instantiating, and Extruding along a Spline Improved element visuals and interaction API, bug fixes, and more - see the Changelog for details What's next Splines 2.1 (coming soon) is landing soon with more artist-focused features and general polish. Future releases will be bug fixing and maintenance - no new features are currently planned. Feedback In terms of feedback, we're especially looking for: Can you think of any use cases that are not covered yet? Are there any workflows that are unclear or missing? Is there anything that is unclear or that you don’t understand? Are there any issues or unclear parts in the documentation? Please share your feedback in this thread. How to report bugs Ideally, we'd like any bugs reported through the built-in bug reporter tool, as that will automatically provide us with some relevant context. When reporting bugs, please: Attach a (stripped) project when there are issues with X. Attach X files when there are issues with X. Have a look at this page for more information and best practices around bug reporting. Once you have submitted a bug report through the bug reporter, please feel free to start a discussion about it in this thread. Thank you for your interest, we're looking forward to your feedback!