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

Unable to run the binary #35

Open
lhauspie opened this issue Nov 25, 2020 · 1 comment
Open

Unable to run the binary #35

lhauspie opened this issue Nov 25, 2020 · 1 comment

Comments

@lhauspie
Copy link

Hi,

I encouter some trouble to run the game.
I'm a Rust newbie, so maybe I don't run the application with the right way.

From local build, I have this log trace:

$ ./target/debug/starlight-1961 
Error: Error { inner: Inner { source: None, backtrace: None, error: ConfigError(File(Os { code: 2, kind: NotFound, message: "No such file or directory" })) } }

From the release alpha 7, I have this one:

$ ./starlight-1961 
[INFO][amethyst::app] Initializing Amethyst...
[INFO][amethyst::app] Version: 0.15.3
[INFO][amethyst::app] Platform: x86_64-unknown-linux-gnu
[INFO][amethyst::app] Amethyst git commit: UNKNOWN
[INFO][amethyst::app] Rustc version: 1.48.0 Stable
[INFO][amethyst::app] Rustc git commit: 7eac88abb2e57e752f3302f02be5f3ce3d7adfb4
[INFO][winit::platform::platform::x11::window] Guessed window DPI factor: 1
[WARN][gfx_backend_vulkan] Unable to find extension: VK_KHR_wayland_surface
[WARN][rendy_factory::factory] Slow safety checks are enabled! Disable them in production by enabling the 'no-slow-safety-checks' feature!
[ERROR][gfx_backend_vulkan] Could not enumerate physical devices! Initialization of a object has failed
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: ErrorMessage { msg: "No physical devices found" }', /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/amethyst_rendy-0.15.3/src/system.rs:148:81
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Thanks in advance.

@suspistew
Copy link
Owner

Hi,

The binary is dependent of the assets folder (configs, levels, sprites, ...) . You have two choices :

  1. Go to the project's root path and run cargo run --releases vulkan

  2. Copy the assets folder into your target/debug folder

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