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?

Thank for your questions! 1. Do I still need to keep paying for the Indie license in the next years? The indie license is a single payment. It is not "per year". 2. Also, if my game (which is live but has never received new updates) starts getting more and more revenue till it crosses the ...

Isn't 100k gross income too low as a threshold? I mean let's say your game makes 110k, you'll be forced to pay the hefty sum of 9000 for a Pro license, representing nearly 10% of your gross income, which means it could be 20-30% or even more of your net income! and that's for 1 platform only! Yes, ...

Symbols for all our binaries are available in the private folder. Did you try searching there?

We are using Unity TouchScreenKeyboard.Open for opening the keyboard. How would achieve what you want with that API? If you find a way, you can modify NoesisUnity.cs (line 509) #if UNITY_2018_1_OR_NEWER keyboard_ = TouchScreenKeyboard.Open(text, keyboardType, true, multiline, secure, false, "&q...

Thank you for the tickets! (#3241 #3240)

We also provided a hot-fix for #3240.

The critical one is an uncaught divide by zero error Unfortunately, this is something we broke in 3.2.3 (for Wasm). It is already fixed, please create a ticket and I will provide a hot-fix. There are also a couple of minor issues with the makefiles - NoesisGUI-wasm.mk uses backslashes in paths, so ...