Search Issue Tracker
Won't Fix
Votes
1
Found in
2021.3.44f1
2022.3.49f1
6000.0.22f1
6000.1.0a7
6000.2.0a1
6000.3.0a1
Issue ID
UUM-83299
Regression
No
"Component (...) had become dangling during an undo operation." warning undoing creating a light
Steps to reproduce:
- Create a new URP project.
- Project View > Create > Rendering > URP Asset (with Universal Renderer).
- Set this newly created asset as the SRP in Project Settings > Graphics.
- Hierarchy > Right-click > Light > Directional Light.
- Press Ctrl+Z.
Actual results:
{code:java}
Component of type MonoBehaviour was added to Directional Light using GameObject.AddComponent() and had become dangling during an undo operation.
Use Undo.AddComponent to correctly add a component which can be handle by the undo system
UnityEditor.EditorApplication:Internal_CallGlobalEventHandler ()
{code}
Expected results: This warning should not appear on such a basic workflow.
Reproducible with versions: 6000.0.32f1, 6000.0.22f1, 2022.3.49f1, 2022.1.0a1, 2021.3.44f1 2021.2.0b1
Couldn't test: 2021.2.0a10, 2021.2.0a1 - couldn't create pipeline asset
Tested on (OS): Windows 11
Notes: warnings are also thrown when undoing Point Light or Spot Light creation
Reverted Fix
A fix for this landed but was reverted. Please see Elvar's comment below: https://jira.unity3d.com/browse/UUM-83299?focusedId=8727738&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-8727738.
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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
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.