Scene Pilot Pro Bridge
intermediate featureScene Pilot Pro Bridge
The SPP Bridge connects Editor Doctor Pro to Scene Pilot Pro. When both products are installed, every SPP ISceneCheck runs across every scene in the project plus every prefab whose check class is decorated as prefab-safe. The findings surface in the Doctor's Scenes tab alongside native EDP checks.
How the bridge is gated
The bridge code lives in a separate asmdef (EditorDoctorPro.Editor.SPPBridge) gated by the scripting define EDP_SPP_PRESENT. Unity sets the define automatically via the asmdef's versionDefines entry when ScenePilotPro.Editor is present in the project; remove SPP and the define clears on the next recompile.
Net result:
- SPP installed - the bridge asmdef compiles, the Doctor exposes the Scenes tab, and the next scan runs every bridged check.
- SPP not installed - the bridge asmdef is excluded from compilation entirely. The Doctor hides the Scenes tab. No compile errors, no orphan references, no manual define management.
What the bridge runs
The bridge runs in two passes per scan:
- Scene pass. EDP opens each scene in scope (Build Settings scenes by default, or every scene in the project with Include All Scenes on), runs every SPP scene check, and restores your original scene setup when it finishes.
- Prefab pass. The SPP checks that are safe to run on prefabs also run against every prefab in scope. How many prefab-safe checks you have depends on your SPP version - the checksRun array in a JSON report shows the exact set after a scan.
Results map to EDP findings under the Scenes category. Severity inherits from the SPP check; the fix tier is always Manual, since in-scene fixes are best applied in Scene Pilot Pro itself.
Pre-flight, cancel and cost
The bridge aborts pre-flight if any scene currently loaded in the editor is dirty or untitled. A dialog explains why and lists the scenes you need to save (or close) first - the bridge needs a clean snapshot so it can restore the editor's scene set at the end.
Once running, the bridge respects the Doctor's Cancel button: cancellation kicks in between scenes and between prefabs so worst-case the user waits for the current scene's checks to finish. The first scan dominates wall-clock time: opening 30+ scenes sequentially takes a while. Subsequent scans hit the per-scan cache.
Suppression and severity overrides
Bridged findings carry the SPP CheckId as their EDP rule id. Suppress them and override their severity exactly like native EDP findings (via the Doctor row context menu or the Settings Rules / Suppression tabs).
scan object in a JSON report. An empty array means SPP discovered zero checks (broken SPP install); a non-empty array with zero issues means your scenes are clean.
Suggest an improvement
Help us improve this documentation page.