kjn_void
Topic Author
Posts: 2
Joined: 08 Jan 2026, 09:52

UI feels one frame behind

19 Mar 2026, 16:24

Background and setup:
A single Noesis view, configured as this
https://freeimage.host/i/qw1OnlR

Translations from world space to UI space are handled by ViewModels that place UI elements on the map rather than as part of the HUD.

I’ve tried adjusting the script execution order so that the camera (using Cinemachine) and the ViewModels run before the Noesis view. Reversing the order does have an effect; the on-map UI elements end up even further behind.

In practice, this issue is only noticeable during camera panning or zooming, so the lag is very small—likely just a single frame.

Is there a way to make on-map UI elements update in lockstep with Unity sprites and other native Unity objects?
 
User avatar
jsantos
Site Admin
Posts: 4822
Joined: 20 Jan 2012, 17:18
Contact:

Re: UI feels one frame behind

19 Mar 2026, 20:12

Our view runs by default in LateUpdate. At that point, we capture the current state of every UI object and send it to the render thread to be displayed in the next frame.

Do you think you could create a small repro that I can take a look at?
 
kjn_void
Topic Author
Posts: 2
Joined: 08 Jan 2026, 09:52

Re: UI feels one frame behind

02 Apr 2026, 19:09

I'll try to create a very small example showing this effect.

A related questions is then: the checkbox that switches between UI-space and world-space UI for Noesis views wouldn't change anything with respect to rendering ordering, right? It would just affect what transforms that are applied?
 
User avatar
jsantos
Site Admin
Posts: 4822
Joined: 20 Jan 2012, 17:18
Contact:

Re: UI feels one frame behind

06 Apr 2026, 19:08

I'll try to create a very small example showing this effect.
Thanks for this!
A related questions is then: the checkbox that switches between UI-space and world-space UI for Noesis views wouldn't change anything with respect to rendering ordering, right? It would just affect what transforms that are applied?
That checkbox actually changes the following:
  • DPI scaling is disabled
  • The projection matrix of the camera is used
  • Depth-testing against the camera z-buffer is enabled
The rendering order itself should remain the same.

Who is online

Users browsing this forum: No registered users and 4 guests