Search Issue Tracker
By Design
Votes
0
Found in
2017.4
2018.4
2019.1.14f1
2019.2
2019.3
2020.1
Issue ID
1178215
Regression
No
The excute order of Native Plugin's OnUpdate and GL.IssuePluginEvent is sometimes doubled up
To reproduce:
1) Open the attached project and scene
2) Build and run on Windows
3) Wait a few seconds for the console to fill
4) Copy all content in the console and paste it out into text editor
Expected: The order is always alternating between OnUpdate and OnRenderEvent
Actual: Rarely, you get doubled up events, like this:
OnUpdate
OnRenderEvent
OnUpdate
OnUpdate
OnRenderEvent
OnRenderEvent
OnUpdate
OnRenderEvent
Reproduced in 2017.4.0f1, 2019.1.14f1, 2020.1.0f1
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 (2020.1.X):
By design, plugin events happens from the render thread