A collection of experimental Unity tools and algorithms for XR stabilization, physics tracking, editor utilities, and performance optimization.
SuperScience is a collection of experimental tools and algorithms for Unity developers, created by Unity Labs. It provides solutions for XR stabilization, physics tracking, editor debugging, and performance optimization, with each component including example scenes and well-commented code for easy integration and learning.
Unity developers working on XR projects, physics-based interactions, or complex editor tooling who need reliable, tested solutions for common development challenges.
Developers choose SuperScience for its practical, production-tested algorithms that address specific Unity pain points, its educational approach with clear examples, and its focus on performance and stability without requiring extensive custom implementation.
Gems of Unity Labs for our user-base.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Stabilizr effectively reduces unnatural shaking in XR for precise object selection, with minimal lag and a worst-case divergence of only 2 degrees, as shown in the example scene with brooms and pointing sticks.
PhysicsTracker generates smooth velocity and acceleration from non-physics sources like animations or XR input by separating speed and direction tracking, outperforming conventional integration methods for complex motions.
Includes tools like HiddenHierarchy and RunInEditHelper for deep debugging and edit-mode execution management, with practical examples and manual control over MonoBehaviour lifecycles in the editor.
Offers utilities like Color32-to-int conversion for fast color processing and solid texture shrinking, with detailed explanations on reducing memory usage and cache misses, as highlighted in the Solid Color Textures section.
The repository is explicitly experimental with no formal support, frequently evolving and tested only against the latest Unity version, making it risky for production use without thorough testing.
Tools like MissingReferences can crash Unity in large projects due to synchronous loading of all assets, as warned in the README, requiring manual code adjustments to mitigate.
As a collection of separate 'gems,' each tool must be integrated individually with limited unified setup or documentation, relying on example scenes and comments rather than comprehensive guides.