docs: anonymise project asset names in source comments
Measured figures are kept; only the studio-specific level and asset names are generalised, and the Perforce rationale is reworded to describe the class of setups rather than this one project. Co-Authored-By: Claude Code <noreply@anthropic.com>
This commit is contained in:
@@ -536,7 +536,7 @@ FAssetUsageExporter::FResult FAssetUsageExporter::CopyExpandedPackages(const TAr
|
||||
|
||||
const bool bWasPresent = FileManager.FileExists(*DestinationPath);
|
||||
|
||||
// This repository is Perforce-primary, so the source .uasset is very often read-only on
|
||||
// Perforce-primary repositories keep unopened files read-only, so the source .uasset is very often read-only on
|
||||
// disk. Windows CopyFile carries that attribute across, which would make the export folder
|
||||
// read-only too - and then an Overwrite-policy re-export fails on its own previous output.
|
||||
// Clear the flag on both ends of the problem: before writing over an existing file, and
|
||||
|
||||
Reference in New Issue
Block a user