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

project does not run on Windows #48

Open
krehera opened this issue Dec 29, 2019 · 3 comments
Open

project does not run on Windows #48

krehera opened this issue Dec 29, 2019 · 3 comments

Comments

@krehera
Copy link

krehera commented Dec 29, 2019

When trying to run on Windows (using Vulkan) I got the following error:

Error: Error { inner: Inner { source: None, backtrace: None, error: ConfigError(File(Os { code: 123, kind: Other, message: "The filename, directory name, or volume label syntax is incorrect." })) } }

I posted in the Amethyst discord -- I wanted to reach you directly as mentioned in the Readme, but no Discord username/number is mentioned. If you need more info, you can reach out to me there. Chish#2578

@krankur
Copy link
Member

krankur commented Dec 30, 2019

@krehera Thanks for logging the issue. Last I checked, the game was running fine on Windows. But that was a long time ago. Will look into this as soon as I get access to a Windows system.

@Jazarro
Copy link

Jazarro commented Dec 30, 2019

If I run cargo run from inside the space menace root directory on Windows 10, the game runs just fine. However, if I then try to run ./target/debug/space-menace.exe, it does produce the same error you are reporting.

The problem seems to be that some of the relative links to files in the /assets/ or /resources/ folders are run from a different directory and are therefore not resolving. A short-term fix is to only run the game using cargo run.

@bacongobbler
Copy link

The game uses the application_root_dir utility function provided by amethyst. From the docs on application_root_dir:

Returns the cargo manifest directory when running the executable with cargo or the directory in which the executable resides otherwise, traversing symlinks if necessary.

So you need to move both the executable as well as the configuration (assets/ and resources/) to the same directory for the executable to resolve the path correctly.

Or just use cargo run as @Jazarro mentions.

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

4 participants