slipher
slipher
> > Are you talking about using a true fullscreen mode as we can sometimes, inconsistently do in SDL2? > > Yes. At least the behavior from the end-user point...
I expect you would have to be very lucky to get the full stacktrace due to the fully buffered logs...
Actually the problem happens on Linux too. And the stack trace code can still cause this crash even if the feature is disabled: it goes into mutual recursion between `Sys::Drop`...
"Tell the bots what to do" could use some unpacking. Would this be accomplished by changing their behavior tree? By changing the rush score or some similar value which can...
The bind works fine. `hw:[` means the key that is in the location that `[` is on the QWERTY layout. For AZERTY, this is `^`. I agree that `hw:[` is...
Default bind change was merged in https://github.com/UnvanquishedAssets/unvanquished_src.dpkdir/pull/55. I managed to reproduce the `hw:[` bug myself now after testing on Linux (it works correctly on Windows). The problem, which can be...
Maybe I'll close this and make an issue on Daemon listing all of the scenarios where SDL gives us garbage keyboard data.
Still broken with SDL 3. I read that this happens whenever text input is enabled.
Wouldn't it make more sense to put this in Daemon so we can use the same formatting for both?
Oh I was just thinking that Unvanquished can rely on the existence of Daemon but not vice-versa. But if there's some stuff where it automatically finds the config file in...