Search Issue Tracker
Duplicate
Votes
0
Found in
5.6.0f3
Issue ID
903105
Regression
No
Cannot change any project settings after setting Perforce as Version Control Mode in Editor settings
To reproduce:
1. Create new project
2. Go to Project Settings -> Editor
3. Set Version Control Mode to Perforce
4. Go to Project Settings -> Time
5. Observe disabled fields
Expected: changing Version Control Mode to Perforce should not prevent a user from changing other settings
Actual: other project settings are disabled when Version Control Mode is changed to Perforce
Reproduced in 5.4.5p1, 5.5.3p1, 5.6.0f3, 5.6.0p2, 2017.1.0b1
Comments (1)
-
perry_garg
Jul 11, 2020 08:13
Open -> EditorSettings.asset
and change
m_ExternalVersionControlSupport: Perforce
to
m_ExternalVersionControlSupport: Hidden Meta Files
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
This is a duplicate of issue #898826