DrDebug Preset Workflow
DrDebug separates local debugging from the team's official revision control baseline. This prevents accidental Perforce checkouts and keeps your local experiments safe.
1. Project Presets (The Official Baseline)
- This is the master configuration for the project, set by the Project Owner/Lead.
- Saving: Requires a dummy file named
TD_Admin.txtfile in the plugin config folder to trigger admin mode which shows "Save Project Preset" Button. Clicking Save Project Preset automatically checks the asset out via Perforce. - The team syncs to latest and uses this as their foundational setup.
2. User Presets (Local Overrides)
- These are local, Perforce-invisible overrides for specific views (e.g., Albedo Debug).
- Saving: Tweak your settings and click "Save Mode". This saves locally and will never trigger a P4 checkout prompt.
- Clearing: Click Reset Mode to throw away your local tweak.
3. The Smart Logic The system is built to prevent you from baking debug settings into the final game.
- Smart Save: If you click Save Project Preset while using a local User Preset (like Albedo Debug), the plugin updates the official baseline in Perforce but ignores your active debug state.
- Smart Reset: Clicking Reset to Project Preset snaps all global settings back to the Lead's official baseline, but it leaves your active User Presets alone. Your local work is protected.
- Resetting everything: First reset all modes manually using the "Reset Mode" button that'll clear each mode, then you can "Save Project Preset" for all or "Reset to Project Setting" for all