Description

A licensee has reported an issue with Perforce source control integration. The issue is related to the source file for an asset that was imported into the editor. If this source file is also checked into perforce, the source file gets move along with the .uasset if it is moved in the Editor while the source control integration is enabled.

The issue here is either that the source file is moved with the .uasset when it is moved or that the source file is not marked for add when it is moved.

Regression?: No
This occurred in 4.20

Steps to Reproduce
  1. Create a project that is checked into a Perforce repository (or use an existing one such as QAGame
  2. Enable source control with Perforce in the editor
  3. Place a WAV file into a folder in the Content directory of the project
  4. Add the WAV file to Perforce
  5. Import the WAV file into the editor to create a .uasset in that same directory.
  6. Save the new .uasset and check it in
  7. Move the .uasset to a different folder
    Result: From looking at the Workspace tab of Perforce, note that the .uasset and the source file (the WAV) have both been moved to the new directory but the Source file has not been marked for add
    Expected: The Source file is either still in its original directory or it is also marked for add when being moved along with the .uasset

Have Comments or More Details?

There's no existing public thread on this issue, so head over toAnswerHub just mention UE-70630 in the post.

1
Login to Vote

Backlogged
ComponentTools
Affects Versions4.204.214.224.23
CreatedFeb 26, 2019
UpdatedFeb 26, 2019