How mathyasgiudici/polimi-aui-magicorchestra works
Project Type and Key Purpose
• The project is a Unity-based interactive application aimed at brain-training through three games (InstruMaps, Quanti Numeri, and Sinfonia di Luci). Its goal is to offer different activities that challenge and train memory in an immersive, multi-sensory environment.
• It supports two modes of operation—a guided “story mode” and split, independent game modes—while also allowing an as-context-free experience.
Key Components (as discovered from the file structure)
a. Game Engine & Scenes:
– The central Unity engine (evidenced by folders like Assets, ProjectSettings, Packages, and Unity-specific file types).
– Multiple Scenes (under Assets/Scenes) corresponding to various game states (e.g., Launcher, CutScenePlayer, Game2, InstruMaps, MagicOrchestra, etc.)
b. Game Modes and Controllers:
– “MagicOrchestraScripts” contains subdirectories for each game (e.g., Game1_InstruMaps, Game2, Game3_CorsiTest) as well as general controllers in “GeneralController.”
– Controllers and managers (ExperienceManagerComunication, GameCanvasControllers, etc.) manage game flow, state, UI, and interactivity.
c. Input and Sensor Integration:
– Presence of scripts such as KinectBodySkeleton, KinectMapper, and UDPListenerForMagiKRoom indicates integration with smart sensors and possibly Kinect hardware.
– “Smart Object Sensor” scripts show that physical objects in the smart space are monitored and controlled.
d. Multimedia & Resources:
– Assets include audio (Assets/Resources/Audio and UIgraphics/Sounds), video (Assets/StreamingAssets/Videos), sprites, fonts, and materials.
– These resources are used within the different scenes to support the multi-sensory brain training experience.
e. External Plugins and APIs:
– The LightShaft and YoutubeAPI folders, along with Plugin directories (e.g., Assets/Plugins/GitHub), indicate incorporation of multimedia and external service integrations (like YouTube content).
– They provide advanced rendering (for video playback, effects) and access to external content.
Architectural Patterns and Design Principles
• The project follows a component-based modular design typical of Unity projects. Each game mode and sensor management component acts as an independent module.
• There’s a clear separation of concerns—input handling and game state management (logic are separated from asset management and UI).
• Controllers and Managers, along with utility scripts and parameter settings, suggest a design where independent components communicate primarily through well-defined interfaces or event messaging systems.