Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
Issue ID
1136601
Regression
No
[Perforce] HDRP Volume profile can't be checked out via the Hierarchy Inspector
How to reproduce:
1. Create a new HDRP project
2. Set it up to use Perforce's version control
3. In the Hierarchy Window create an empty game object and add the "Volume" component
4. Under the "Profile" setting click "New" and observe that you can create new overrides to it (the "Add Override" button isn't greyed out)
5. Submit all new files to perforce and observe the empty object again
Expected result: the override button is greyed out and there is a way to check out the profile file to unlock editing (or alternatively there is a warning message telling users to check out the profile file through the Project Window)
Actual result: the override button is greyed out but there is no way to check out the profile file to unlock editing from the Inspector Window
Reproduced in: 2019.2.0a8 with (HDRP 5.7.1; HDRP 5.2.1)
Note: To unlock the file editing you'd need to find the profile file in the Project Window and check it there
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note:
Low priority feature request, we might reconsider it again at some point