Bridging 3D and AR Unity Workflows

Current Status: We have successfully implemented a system that creates a project, uploads a .glb model to Firebase, and allows the Unity app to download and view that model in a standard 3D View. We have also verified that basic AR tracking works in a separate test scene. The Problem/Task:I need to bridge these two workflows. Specifically, when a user is in the 3D View of their downloaded model and clicks the "AR View" button, the app must:Scene Transition: Transition from the Main/3D scene to the dedicated AR View scene (referencing the structure in AR View.unity). Data Persistence: Pass the downloaded model data (or its local cache path) into the AR scene without re-downloading it.Dynamic Spawning: Configure the Object Spawner and SingleSpawnController in the AR scene to use this dynamic model instead of a static prefab. UI/Functionality Integration: Ensure the specific professional features—such as the Opacity Slider, Position Locking, and Confirm Exit Popup—are fully functional with the dynamic model.