Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

lutris -d doesn't output debug #106

Open
sukulent opened this issue Feb 17, 2021 · 2 comments
Open

lutris -d doesn't output debug #106

sukulent opened this issue Feb 17, 2021 · 2 comments

Comments

@sukulent
Copy link

When I start game using lutris -d lutris:rungame/game-identifier it just starts the game and ends with command prompt. No debug output.

I had this problem on 0.5.2 after some scary upgrading I am on 0.5.8.3 and this problem persist. But now I have some of my games broken, because I use Proton and also I use gloriuseggroll proton.

Is there some right way to solve these? I am kinda tired of googling stuff already.

thanks

@strycore strycore transferred this issue from lutris/lutris Feb 22, 2021
@strycore
Copy link
Member

can you run the games normally from the client?
why are you using Proton-GE and not our builds?
Are you using LUTRIS_ENABLE_PROTON or are you using some weird workaround to still use Proton?
For the games that you wish to get console log for, have you enabled the WINEDEBUG option?
Have you checked the lutris log file?
Do you already have lutris open when you run your game?

@sukulent
Copy link
Author

Thanks for the reply
I can run games normally.
I used proton, namely 3.16 I think to run wargaming game center and world of tanks. When wot once crashed on start I have just tried one wine version after another and because I was running old version of lutris (debian it is) I had proton normaly in the list to chose from.
I am not using any workaround for proton, If I understood the internet correctly, there are wine builds which are virtually the same but without steam or something. So I need to try wine versions until will hopefully work again.
I am not sure what option do you mean, setting "Output debugging info" doesn't fix it.
I did not checked lutris log file, where it is?
In Lutris, clicking "Show logs" opens a window and shows log as it always did.
It looks like I have never run lutris -d with lutris closed. It seems like it's working as expected when lutris is not open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants