Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.61f1
6000.0.47f1
6000.1.0b6
6000.2.0b5
6000.3.0a1
6000.4.0a1
Issue ID
UUM-108541
Regression
No
Asset is shown as not checked out but is editable when adding a scoped registry
Steps to reproduce:
- Create a new project
- In project settings setup scope registry:
## Name: {{Keijiro}}
## URL: {{https://registry.npmjs.com}}
## Scope: {{jp.keijiro}}
- Install Noise Shader in the Package Manager
- In Asset Broswer's search, enter: t:VisualEffectAsset t:VisualEffectSubgraph
- Select In Packages label to show assets that are in Packages folder
- Open 06_Firework VFX
Actual results: Notification "Check Out to modify" is present, whole vfx is tinted showing it as uneditable, although there is no checkout button and vfx can be edited anyway
Expected results: VFX functions as usual and doesn't get interfered by VCS integration
Reproducible with versions: 22.3, 6000.0, 6000.1, 6000.2, 6000.3
Not reproducible with versions:
Can’t test with versions:
Tested on (OS): macOS
Notes:
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
- Non-editable Repeat - X and Repeat - Y settings appear when UI Builder Canvas Background is set to image
- Volume Profile Add Override font size is too small
- Build Profiles window Build Profiles functionality breaks when the newly created Build Profile has a lot of symbols in the name
- Crash on PlayableGraphBindings::DestroyOutputInternal when entering Play Mode in a specific project
- Editor Freezes when instantiating TMP text formatted with rich text tags in non Latin languages
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note:
Forward-ports for this version need to be handled at a later time.