Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2019.2.0b4
2019.3.0a1
2019.3.0a9
Issue ID
1169190
Regression
Yes
Perforce credentials are reset when switching asset database versions
How to reproduce:
1. Create a new project in your Perforce Workspace folder
2. Open it and set it up to use Perforce
3. Change the asset database version
4. Save the project and reopen it
5. Observe the Perforce credential fields
Expected result: the fields are saved and are still filled out after the restart, perforce is connected automatically
Actual result: the fields are empty after the restart and perforce connection is broken
Reproduced in: 2019.3.0a9, 2019.3.0a1, 2019.2.0b9, 2019.2.0b4
Not reproducible in: 2019.2.0b3, 2019.2.0a6
Couldn't test with 2019.2.0a5, 2019.1.10f1, 2018.4.4f1, 2017.4.30f1 (no second asset pipeline version)
Note: reproduces both when switching from v1 to v2 and vice versa
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