Open ScottVordem opened 4 days ago
Huh, EA app actually does start just fine, I guess it was just a one time hiccup for that specific program.
For some applications it may be important that they are launched from the correct working directory. If you check the poperties of the OBS link, you'll see that it has a working directory set:
So in your start command, you need to switch to that directory first. On my installation, this command works:
cd "C:\Program Files\obs-studio\bin\64bit" && "C:\Program Files\obs-studio\bin\64bit\obs64.exe"
If an application does not find some files, it's usually a good indicator that the working directory is wrong.
Ah, I had a suspicion that it was the working directory!
I have OBS installed on a different drive, so the command you gave did not work for me. But I did figure out how to launch it properly with what you gave me.
This is what worked for me with OBS installed on a different drive for anyone else with a similar problem.
E: && cd "E:\Program Files\obs-studio\bin\64bit" && "E:\Program Files\obs-studio\bin\64bit\obs64.exe"
Replace all instances of E:
with your drive letter.
Short Summary
There seems to be an issue on how Kando handles the launching of programs. OBS Studio launches with an error (from OBS, not Kando) saying it "can't find the locale (US-en.ini)" and therefore won't launch because it can't find the locale, but launching OBS normally (via the exe directly or Start Menu shortcut) works as expected. I'm not sure why this is the case. OBS isn't the only one though, the EA app also does not launch properly through Kando but does not have an error and seems to silently fail to launch.
There could be more, but these are the ones I personally experience to not launch properly with Kando.
Steps to Reproduce the Issue
Kando Version
v1.1.0
Installation Method
Via an installer downloaded from a release on GitHub
Desktop Environment
Windows
Environment Version
Windows 11 23H2
Additional Information
No response