| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004450 | NoesisGUI | Unity | public | 2025-10-24 18:43 | 2025-10-27 13:01 |
| Reporter | stonstad | Assigned To | jsantos | ||
| Priority | normal | Severity | major | ||
| Status | resolved | Resolution | no change required | ||
| Product Version | 3.2.10 | ||||
| Summary | 0004450: Noesis 3.2.9 Performance Regression | ||||
| Description | I'm seeing substantially increased update times in NoesisView.LateUpdate(). The culprit appears to be the addition of a MeshRendererFinalizeUpdate and ParticleSystem.EndUpdateAll method. It is adding 1ms of CPU time per frame rendered. See enclosed screenshot. Is this related to the new MeshGeometry feature? I am not aware of using any particle systems in conjunction with Noesis. | ||||
| Platform | Any | ||||
 |
I disabled every Unity game object containing a particle system. This ParticleSystem.EndUpdateAll overhead identified within Noesis.Update remains. It appears to be coming from Noesis. |
 |
That's definitely not Noesis. But I don't know why it is happening inside our Is this a View rendering to a texture? |
|
|
With deep profiling I can see that it is introduced via a Graphics.ExecuteCommandBuffer call that appears to originate in Noesis. encl. screenshot Update 1. I'm not seeing any command buffer actions associated with the camera associated to the Noesis View. The view uses overlay mode for rendering. I'm still looking. Please feel free to close this issue. I'll include a link to a forum question re: this topic in Unity Discussions. image-2.png (209,412 bytes) |
|
|
https://discussions.unity.com/t/profiling-and-graphics-executecommandbuffer-injected/1691976 |
|
|
Thanks for the post! I will keep watching it. This definitely smells like a Unity hack to solve something on their side. |
