This has been fixed today.

Thanks, please next time do not reopen closed threads.

I am not sure your fix makes sense. For example, NoesisXamlEditor is already unregistering views in OnDisable() method.

Unregistering a view before rendering with it seems suspicious to me.

Thanks for the ticket (#3278)!

Thanks for the ticket!

If you are in Unity, you can also entirely disable keyboard in the view and enable actions to drive the navigation. This way you can redefine the inputs to your needs.

It seems Emscripten was updated to 3.1.38 in Unity 2023.2.0 and this could be the problem you are experimenting. I assume that previous versions of Unity (with Noesis 3.2.2) works fine for you?

Could you please create a ticket for it?

Are you getting this problem in both D3D11 and D3D12 renderers? Just commenting the Graphics.ExecuteCommandBuffer line fixes the issue? Could you please paste the relevant code here?

We could also use one of the InputScopes for this (like Private). Would this a valid solution for you?

Could you please create a ticket for this?

Are you reproducing this with our samples too?