# The form data below was edited by norman_morse # Perforce Workshop Jobs # # Job: The job name. 'new' generates a sequenced job number. # Status: Job status; [open/closed/suspended]. Required # Project: The project this job is for. Required. # Severity: [A/B/C] (A is highest) Required. # ReportedBy The user who created the job. Can be changed. # ReportedDate: The date the job was created. Automatic. # ModifiedBy: The user who last modified this job. Automatic. # ModifiedDate: The date this job was last modified. Automatic. # OwnedBy: The owner, responsible for doing the job. Optional. # Description: Description of the job. Required. # DevNotes: Developer's comments. Optional. # Type: Type of job; [Bug/Feature]. Required. Job: job000131 Status: open Project: perforce-software-p4connect Severity: A ReportedBy: jan_van_uytven ReportedDate: 2014/12/12 15:59:34 ModifiedBy: norman_morse ModifiedDate: 2015/10/12 17:04:32 Description: Renaming an asset under Perforce control results in an error message: This doesn't seem to be just limited to FBX files, I'm seeing this problem crop up around many different types of assets. As a quick repro, try this: 1. Add a texture to Perforce, and submit. 2. Rename the texture. It immediately complains: P4Connect - Error The following files could not be checked out: Assets/Textures/<texture_name>.jpg Assets/Textures/<texture_name>.jpg.meta DevNotes: Priority: High Type: Bug