Search Issue Tracker
Active
Votes
0
Found in
2021.3.25f1
Issue ID
UUM-79523
Regression
No
PlasticSCM errors appear when creating a new project
Reproduction steps:
1. Open Unity Hub
2. Select “New project”
3. Select one of the affected versions
4. Select the “3D (Built-In Render Pipeline)” template
5. Uncheck “Connect to Unity Cloud” and “Use Unity Version Control“
6. Press “Create project”
7. When the project is created, observe the Console
Expected result: No errors are logged
Actual result: “Assembly 'Library/ScriptAssemblies/Unity.PlasticSCM.Editor.dll' will not be loaded due to errors:…” errors are logged
Reproducible with: 2021.3.25f1
Not reproducible with: 2021.3.43f1, 2022.3.0f1, 2022.3.44f1, 6000.0.0f1, 6000.0.17f1
Fixed in: 2021.3.26f1
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
- In 2021.3.26f1 errors appear, but they are different and not related to version control
- Tested using Unity Hub 3.8.0 and 3.9.0-beta.2
- The errors do not always appear, so it might take a few tries to reproduce
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment