Stingray generated a lot of "intermediate" data (shader caches, compiled physics data). To keep the Perforce depot clean, teams had to create strict exclusion lists in their .p4ignore file (or via workspace views). You didn't want to check in the DCC cache folder—it could balloon to gigabytes in size and was easily regenerated by other users.
To run a professional studio on Stingray, the default setup wasn't enough. You needed the Advanced Configuration: stingray perforce full
Stingray Perforce bridges the Stingray engine and Perforce Helix Core to provide an asset-aware, collaborative source control experience optimized for game development. It emphasizes locking for binaries, stream-based branching, editor-integrated workflows, and CI-triggered processing to keep teams in sync and builds reproducible. Stingray generated a lot of "intermediate" data (shader
Related search suggestions will follow.
Note: If you meant a different "Stingray" (e.g., F5's API gateway), please clarify. The following is based on the known Perforce security auditing tool. To run a professional studio on Stingray, the