Search Issue Tracker
Active
Under Consideration for 6000.6.X
Votes
0
Found in
6000.0.70f1
6000.3.11f1
6000.4.0b12
6000.5.0a9
6000.6.0a1
Issue ID
UUM-137592
Regression
No
Multiple errors are thrown in the console while using perforce when moving an asset using shortcuts
Steps to reproduce:
1. Open the attached “IN-136347_perforce_test_project.zip”
2. Connect to your workspace in Perforce (Edit → Project Settings → Version Control)
3. Submit the test project to Perforce in the Version Control window
4. Cut (Ctrl/Cmd + X) the file “MyPrefab” (Project → Prefabs/Folder A)
5. Paste (Ctrl/Cmd + V) it in Prefabs/Folder B
6. Observe the Console and the Project windows
Actual Result: Multiple errors are thrown in the Console and the move fails
Expected Result: The move succeeds
Reproducible with: 2023.1.0a3, 6000.0.70f1, 6000.3.11f1, 6000.4.0b12, 6000.5.0a9, 6000.6.0a1
Reproducible on: macOS Sequoia 15.7.3 (M1 Max)
Not reproducible on: No other environments tested
Workaround: Manually dragging the prefab into the other folder does not reproduce the issue
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Play Mode framerate drops significantly when moving the mouse cursor with high polling rate
- Create workspace does not update the Unity Version Control and Branch Explorer windows leading to multiple clicks on “Create workspace” which throws an “already exists” error when Creating a workspace with the Branch Explorer window open
- Default and Result encoding properties have blank dropdowns by default when opening the Unity Version Control Settings
- Crash on "StoredGraphicsBuffer::GetGfxBufferID" when activating VFX via extention of Activation Track in Timeline window
- [Linux] Stack trace file path and line number information is missing when IL2CPP Stacktrace Information is set to "Method Name, File Name, and Line Number"
Add comment