Description

With Virtual Assets setup in a project, when an asset is deleted and the changelist then submitted via revision control, the virtualization system will attempt to read the deleted asset.

The submit via revision control will still be successful, but this causes needless errors to be reported in the output log.

Steps to Reproduce
  • Create a new project, and set it up to use Virtual Assets ([Link Removed])
  • Set up a local perforce depot for use with revision control, ensure that a readonly/partitioned workspace is supported by configuring the db.have table with p4 configure set client.readonly.dir="location here"
  • Configure revision control in the project to point to the perforce server
  • Add any asset to the project and submit to perforce via revision control
  • Delete the previously added asset and submit with revision control to perforce
  • Note the submit goes through, but an error is reported in the output log as the Visualization system is unable to read the now deleted file
Callstack

"LogSerialization: Error: Could not open the file '/Game/Test/MyTestAsset' for reading due to system error: 'The system cannot find the path specified.' (3))

Have Comments or More Details?

There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-248267 in the post.

0
Login to Vote

Fixed
ComponentUE - CoreTech - VirtualAssets
Affects Versions5.5.3
Target Fix5.6
Fix Commit40125471
CreatedFeb 17, 2025
ResolvedFeb 19, 2025
UpdatedFeb 19, 2025
View Jira Issue