Search Issue Tracker
Fixed in 1.1-pre.6
Votes
1
Found in [Package]
2020.2.7f1
2020.3
2021.1
2021.2
Issue ID
1322530
Regression
No
Events are not called in the order they were added when they are modified in the middle of the call by other listeners
How to reproduce:
1. Open attached project "InputSystemBug.zip"
2. Open "SampleScene" scene
3. Enter Play Mode
4. Press Spacebar
5. Observe Console window
Expected result: Output is A [new line] B
Actual result: Output is A [new line] C
Reproducible with - 1.1.0-preview.3 (2019.4.22f1), 1.1.0-preview.3 (2020.3.5f1), 1.1.0-preview.3 (2021.1.14f1), 1.1.0-preview.3 (2021.2.0a12)
Could not test (errors) - 2018.4
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
- With specific Windows 10 settings, the player window resolution does not match the values passed into Screen.SetResolution()
- Material leaks memory when using PostProcess-Layer
- [URP] Adreno GPU is not getting the required vertex data
- [DX12] ShaderData.VariantCompileInfo.ShaderData contains 38 extra bytes on DirectX 12
- Dynamic lights still show up in the Profiler consuming time when "Main Light" and "Additional Lights" are disabled in the UniversalRP-HighQuality asset
Resolution Note (fix version 1.1-pre.6):
Fixed in 1.1-pre.6