You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On both Linux systems I've tested (Fedora and Slackware), Valkyrie 2.6.0 is unable to locate Mansions of Madness.
From Player.log the relevant line appears to be:
Could not find main assets file: /Mansions of Madness_Data/resources.assets
However, the file exists:
$ file file "$HOME/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/Mansions of Madness/Mansions of Madness_Data/resources.assets"
/home/klaatu/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/Mansions of Madness/Mansions of Madness_Data/resources.assets: data
Steps to reproduce:
On Linux, launch Valkyrie.x86_64
Click Locate the game button on start screen
[Application hangs]
Valkyrie Version
2.6.0
Desktop
OS: I've tested both Slackware 15 and Fedora 40
Browser: Not applicable, I think, but I use Firefox. No browser was involved with this error.
Some users were able to solve the installation problem with that files. It was created for android. Not sure if it's fully compatible with Lynux. I could do a similar package for Windows, if that helps.
Then I launched valkyrie.x86_64 and it behaved the same: It told me that Mansions of Madness had to be installed, and offered to let me either install it (it's already installed) or to locate it. When I click the button to locate, it hangs.
Player log is basically the same (minor differences in thread IDs, but otherwise identical).
It seems to not know where to look for Mansions of Madness or my Steam library, maybe?
Describe the bug
Seems identical to #1681
On both Linux systems I've tested (Fedora and Slackware), Valkyrie 2.6.0 is unable to locate Mansions of Madness.
From
Player.log
the relevant line appears to be:However, the file exists:
Steps to reproduce:
Valkyrie Version
2.6.0
Desktop
Complete log file attached.
Player.log
The text was updated successfully, but these errors were encountered: