A "full" setup isn't a one-click installer. It is a configuration philosophy. If your Stingray project is not running on Perforce, you are not shipping—you are gambling.
The integration allows you to input your Perforce server details (P4PORT), username, and workspace directly into the Project Settings. Once connected, Stingray treats the project folder as a controlled depot.
Stingray treats everything as data (compiled resources). Perforce allows teams to track changes to both raw source assets and compiled target data cleanly. stingray perforce full
For game development, "Stingray Full" wins. For plain text source code, Git LFS is sufficient.
Provides a framework for building graphical editors, diagrams, and dashboards with drag-and-drop capabilities. Objective Edit: A "full" setup isn't a one-click installer
| Feature | Stingray Perforce Full | Git LFS | | :--- | :--- | :--- | | | Native (exclusive checkout) | Requires git-lfs-lock (add-on) | | Large File Speed | Incremental (delta transfers) | Full file on every change | | Folder permissions | Per-directory ACLs | Repository-wide only | | Partial checkout | Sparse workspaces (native) | Sparse-checkout (slower) | | Unreal/Unity integration | Plug-in built-in | Third-party (GitHub Desktop) |
For a developer using the "Full" integration, the workflow looked like this: The integration allows you to input your Perforce
Once configured, the daily workflow inside Stingray follows a strict checkout-modify-submit lifecycle. Modifying Assets