Open DaniAngel opened 2 years ago
no input code changes recently so you need to git bisect to find out if there is really a regression
Thank you for the reply. I will read up on git bisect. I have never used this command. I have been playing around with it a little more and found the underlying problem. I created a launcher for my desktop to run the STK Git version that I compiled and installed. When I launch STK from the launcher, it launches in full screen mode, however it is NOT the active application, thus it doesn't take input from either the controller or the keyboard. My memory of using the keyboard was wrong. I must use the mouse. I don't have to click on the options button...I just have to click anywhere in the STK window to make it the active application. Then both the controller and the keyboard work as expected. Is there a way to modify the launcher to make sure it is the active window? Currently the launcher runs the following command: "/usr/local/bin/supertuxkart" Dani
maybe this will work
try edit your stk-code/lib/irrlicht/source/Irrlicht/CIrrDeviceSDL.cpp and use SDL_WINDOW_FULLSCREEN_DESKTOP instead of SDL_WINDOW_FULLSCREEN
maybe this will work
try edit your stk-code/lib/irrlicht/source/Irrlicht/CIrrDeviceSDL.cpp and use SDL_WINDOW_FULLSCREEN_DESKTOP instead of SDL_WINDOW_FULLSCREEN
Thank you for the reply. Is this something that I need to recompile and build after making the switch? Dani
Yes
maybe this will work
try edit your stk-code/lib/irrlicht/source/Irrlicht/CIrrDeviceSDL.cpp and use SDL_WINDOW_FULLSCREEN_DESKTOP instead of SDL_WINDOW_FULLSCREEN
Thank you for the reply. Is this something that I need to recompile and build after making the switch? Dani
maybe this will work
try edit your stk-code/lib/irrlicht/source/Irrlicht/CIrrDeviceSDL.cpp and use SDL_WINDOW_FULLSCREEN_DESKTOP instead of SDL_WINDOW_FULLSCREEN
This worked!!!! Thank you so much! Dani
Description
I am using the git version. Linux Mint 20.3 Cinnamon. Asus x415 laptop with 20GB RAM and 500GB ssd. Every time I start STK, I have to use the mouse or Keyboard to open the options page. Once the options page is displayed, my wireless, usb ps3 controller will work, until I get on the options page, STK doesn't recognize it. Everything is fine until I quit the game and restart it. Then I have to open the options screen again.
Steps to reproduce
I cloned the git files and compiled and installed from source. Not sure how to determine version. Git was cloned on 8/8/2022. When using a wireless usb ps3 controller, everything seems to work after setting up the controller. Gameplay is good. When I quit the game, and then restart the game, only the keyboard and mouse are detected until I press the options wrench. as soon as I am on the options screen, the ps3 controller works as it is supposed to. Is there a setting I need to change for the game to auto discover the controller without having to click on the options button? The previous version of STK, from the repository worked properly in this regard. However I could not connect to the STK servers with that version, thus the GIT clone, build and install from source route for the latest version.
Configuration
STK release version: Git version
STK Source (PPA, distribution package, official binary, etc.): Git Clone from STK on github (downloaded on 8/8/2022)
System: linux mint 20.3 cinnamon Running on Asus X415 with 20GB Ram, 500GB ssd Graphics card: Intel UHD
CPU: Intel core i3 Gamepads/keyboards models if related to the issue: Afterglow PS3 usb wireless controller
Additional information
stdout.log:
input.xml:
Error message: