Search Issue Tracker
Not Reproducible
Votes
0
Found in
2021.3.20f1
2022.2.9f1
2023.1.0b6
2023.2.0a3
2023.3.0a3
6000.0.0b11
7000.0.0a1
Issue ID
UUM-29088
Regression
No
Wrong script is opened when double-clicking the runtime error in the Console
How to reproduce:
1. Open the project ”IN_31123”
2. Open the “-MAIN resizing UI” Scene
3. Enter the Play Mode
4. Wait until the 4th error “NullReferenceException: Object reference not set to an instance of an object MovementSwitcher.Awake () (at Assets/MovementSwitcher.cs:31)” pops up
5. Double-click the error
Expected result: “MovementSwitcher.cs” script is opened
Actual result: “AgeingAction_Transmute.cs” script is opened
Reproducible with: 2021.3.11f1, 2021.3.20f1, 2022.2.9f1, 2023.1.0b6, 2023.2.0a3
Couldn't test with: 2020.3.46f1, 2021.3.10f1 (due to compiler errors)
Reproducible on: Windows 10 Pro
Notes:
- Reproducible with Visual studio and Rider
- Couldn’t reproduce with first error “ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index System.Collections.Generic.List`1[T].get_Item (System.Int32 index) (at <9aad1b3a47484d63ba2b3985692d80e9>:0)
LoadProceduralCreature+<LoadCO>d__17.MoveNext () (at Assets/Scripts/Game/LoadProceduralCreature.cs:99)” in the Console
- 4th step could take up to 5 min
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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
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.