Search Issue Tracker
Fixed in 5.4.0
Votes
0
Found in
5.1.3p3
Issue ID
730245
Regression
Yes
[Perforce] Duplicating an asset with Perforce intergration doesn't set file as writable
To reproduce:
1. Inport and set-up perforce
2. Sync a PSD texture from Perforce, but do not check it out
3. In the Project view duplicate an asset that is not already checked-out
4. Double click the texture in the Project view to open in Photoshop (you
may need to set Photoshop as your default image editor)
5. Make a change to the texture and press Ctrl-S to save the image.
6. You will receive an error that the file could not be saved. The error is a result of the file being read-only.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Textures] CubemapArray API forces duplicate code because you cannot access individual cubemaps directly
- Duplicating a Prefab instance in the Scene will cause instances of the same Prefab to be disabled and re-enabled
- GUI.Button and GUILayout.Button stay in the normal GUIStyleState even when the normal GUIStyleState is changed to another one
- Particle System mesh UV coordinates change when mesh's geometry layout is changed on import
- [Windows] The Unity import progress is not shown in the Windows taskbar
Add comment