Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2021.2.X
Votes
0
Found in
2018.4.35f1
2020.3
2021.1
2021.2
2022.1
Issue ID
1353761
Regression
No
[Perforce] Unnecessary checkout for .dll files when Reimporting them in the Editor
How to reproduce:
1. Open a new project
2. Add the attached "MeshExtension.dll" to the Assets folder
3. Create a Perforce stream for this new project and submit all relevant files, including MeshExtension.dll
4. Enable VCS integration in Unity connecting to your Perforce stream
5. Right-click MeshExtension.dll in Unity and select Reimport
Expected: The MeshExtension.dll is reimported and not checked out in Perforce as there are no required API changes
Actual: The MeshExtension.dll is checked out in Perforce without any changes
Reproducible with: 2020.3.16f1, 2021.1.17f1, 2021.2.0b7, 2022.1.0a6
Can't test with: 2019.4.29f1 (Errors from the .dll file when Reimporting)
Note:
- Opening the project in a newer version also causes the MeshExtension.dll to checkout
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Long Prefab save times when using Unity 2022.2 and higher
- Console displays error "UnityException: Creating asset at path Assets/Scenes/ .scenetemplate failed." during scene template saving
- "Development Build" watermark is shown in non-development UWP release builds
- Console errors appear when the Inspector is set to Debug and a GameObject is selected
- A script public variable value is not used when set in the Inspector window
Resolution Note (fix version 2022.1):
Already fixed in version 2022.1.0a12
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.13f1