App::clearKeyState not getting numpad ascii code properly in 2.11

[Lales.Charles]

Dear Unigine support,

Just upgraded 2.10 -> 2.11, and get an issue with numpad key not recognized anymore.
This used to work properly, from keyboard 0...1 as numpad 0..1

		for (int i = 0; i < 10; i++)
			if (App::clearKeyState(48 + i) == 1) //num key 0..1
				[...]

But now it seems to detect null 0 when I scan all ascii code, what ever the numpad key pressed is:

		for (int i = 0; i < 256; i++)
			if (App::clearKeyState(i) == 1)
				Log::message("hum hum");

Is it normal?
Do you reproduce?

Kind regards,
Charles

[Lales.Charles]

Hi,

Very weird behavior.. i get it working in 1 case:
- No plugin -> KO
- Plugin IG/CIGIConnector -> KO
- Plugin AppVive -> OK

Kind regards,
Charles

[javier.serrano]

Hi, had same issue with '+' key in 2.11.0.2 app. Also with engine.app.getKeyState('+').

Don't know if it is related but also XPad controls make same issue with ControlsXPad360::getStateButton(CONTROLS_XPAD360_BUTTON_A)

Regards, Javier

[silent]

javier.serrano
You can use Unigine Input (Windows only) to workaround this issue with XPad controls: xpad360_00.cpp
getKeyState('+') will work only for '+' key from numpad, for regular '+' key you need to use '=' sign.

Lales.Charles
Thanks for the additional information, we are currently trying to reproduce it.