Build #135 (Linux) - shift/backspace/capslock keys output "?" character instead [PARTIALLY RESOLVED]

Interkarma · Post by **Interkarma** » Sat Oct 13, 2018 9:01 am

This was reported on reddit in the following spot.

https://www.reddit.com/r/daggerfallunit ... 8/e7okzvs/

I don't have any more information on this right now. Anyone else experiencing this?

Interkarma · Post by **Interkarma** » Sat Oct 13, 2018 12:19 pm

Just confirming this one. "Event.current.character" seems to be processed badly in the Unity Linux Player for 2018.2.11. Trying to find a workaround if possible.

Edit: Have a workaround for this in DFU code, but problem is still present in console input. This is just using a standard input field in Unity's own UI controls. There's definitely something a bit weird about input in Unity 2018.2.11f1 under Ubuntu 18.04. I might have to sit on this one for a bit to see what Unity do about it.

Interkarma · Post by **Interkarma** » Sat Oct 13, 2018 2:08 pm

OK, I've implemented my workaround for DFU. The console is still impacted though, because this is a Unity bug and console uses standard Unity UI. Fortunately DFU has custom input and UI layers, so I can workaround in my own code.

One fix would be to re-implement the console using DFU's DagUI. The only reason this wasn't done originally is that I was still building UI system when Lypyl added the console. I'll consider doing this if problem isn't resolved fully by Unity by the time I'm ready to leave pre-alpha.

I'm not shifting from Unity 2018.2.x before release, but will tick up minor versions for bug fixes as they become available.

Daggerfall Workshop Forums