search

rfvgyhn / min-ed-launcher

Minimal Elite Dangerous Launcher
MIT License
271 stars 10 forks source link

[0.7.3] Not launching the game "Couldnt get machine id" #70

Open Zetabite opened 2 years ago

Zetabite commented 2 years ago

System:

Proton: GE-Proton7-41

Launch Options: tilix -e ./MinEdLauncher %command% /autorun /autoquit /edh4

Log: [10:08:00 INF] Elite Dangerous: Minimal Launcher - v0.7.3+486163a7 [10:08:00 INF] Elite Runtime Platform: Steam CobraBay Version: 0.4.6725.0 Products Dir: /home/zetabite/.local/share/Steam/steamapps/common/Elite Dangerous/Products [10:08:00 ERR] Couldn't get machine id: Unable to find wine directory. Make sure either STEAM_COMPAT_DATA_PATH or WINEPREFIX is set Press any key to quit...

Zetabite commented 2 years ago

Somehow works now, wtf

Zetabite commented 2 years ago

It worked after reboot, but once i quit the game, it has the same issue again.

rfvgyhn commented 2 years ago

Can you post a run from your log file at $XDG_STATE_HOME/min-ed-launcher/min-ed-launcher.log (~/.local/state if $XDG_STATE_HOME isn't set)?

rfvgyhn commented 2 years ago

I'm not familiar with tilix so perhaps it handles env vars different than what the code expects. This error occurs when STEAM_COMPAT_DATA_PATH or WINEPREFIX aren't set. Steam sets STEAM_COMPAT_DATA_PATH as part of proton's launch process.

A couple things to try:

A kludgy workaround would be to manually set STEAM_COMPAT_DATA_PATH. This points to Elite's compatdata folder. tilix -e STEAM_COMPAT_DATA_PATH=/[your steam path]/steamapps/compatdata/359320 ./MinEdLauncher %command% /autorun /autoquit /edh4

Zetabite commented 2 years ago

its not proton, since i tried with 6.3 too.

min-ed-launcher.log

rfvgyhn commented 2 years ago

The log shows what I expected. STEAM_COMPAT_DATA_PATH isn't set (Env: is blank in the log file). I also tried tilix with default configuration on my system and it works fine. I'm not sure why env vars aren't being passed on to the process.

I also made a mistake when giving the example command for setting the env var manually. It should be STEAM_COMPAT_DATA_PATH=/[your steam path]/steamapps/compatdata/359320 tilix -e ./MinEdLauncher %command% /autorun /autoquit /edh4

Are you perhaps launching the game differently than normal (i.e. not clicking the play button within steam)? Unfortunately, I can't really think of another reason why that env var wouldn't be set.

Zetabite commented 2 years ago

cant think of any other way of launching elite dangerous. i launch it as you said via play button. i could imagine that i possibly have something set up differently for tilix, but i wouldnt know where to look for that

rfvgyhn commented 2 years ago

I'd recommend trying a different terminal emulator to try and rule out a tilix issue (I use alacritty).

Does manually setting the env var have the same problem?

Zetabite commented 2 years ago

with konsole it works without issue, so i will use this for now. but keep it open, so we can possibly figure out why my tilix is causing it