Err value: couldn't open file' about rust-doom HOT 6 CLOSED

The filenames are case sensitive (unless you're on windows). Therefore you should either rename the wad file to "doom1.wad" or use --iwad DOOM1.WAD.

Or, if that's fine, it might not be the WAD, could you build in non release mode and run with RUST_LOG and RUST_BACKTRACE set as follows

cargo build
RUST_LOG=debug RUST_BACKTRACE=1 target/rs-doom --iwad doom1.wad

To see where the issue stems from? The only other thing I can think of is that you're not running rs-doom from the right folder (its should be the repo's root, where Cargo.toml is).

from rust-doom.

Yep, I'm using the correct file casing.

rust-doom/target$ ls -la
total 9008
drwx------ 6 jdunlap jdunlap 4096 Oct 15 01:01 .
drwxr-xr-x 6 jdunlap jdunlap 4096 Oct 13 03:55 ..
drwx------ 9 jdunlap jdunlap 4096 Oct 15 01:01 .fingerprint
drwx------ 2 jdunlap jdunlap 4096 Oct 15 01:01 deps
-rw-r--r-- 1 jdunlap jdunlap 4196020 Oct 15 01:01 doom1.wad
drwx------ 2 jdunlap jdunlap 4096 Oct 15 01:00 native
drwx------ 5 jdunlap jdunlap 4096 Oct 14 05:58 release
-rwxr-xr-x 1 jdunlap jdunlap 4998760 Oct 15 01:01 rs-doom

Here's the debug statement:

RUST_LOG=debug RUST_BACKTRACE=1 ./rs-doom --iwad doom1.wad
INFO:rs-doom::wad::archive: Loading wad file 'doom1.wad'...
task '

from rust-doom.

Again, you have to run the binary from the repo's root i.e. where the Cargo.toml file is, not from the target directory. That's also where the doom1.wad file should be too:

rust-doom$ ls
screenshots src target Cargo.toml doom1.wad doom.toml LICENSE README.md

rust-doom$ RUST_LOG=info RUST_BACKTRACE=1 target/rs-doom --iwad doom1.wad
...
...

from rust-doom.

I've had the same problem. When runing from root not target folder it's working.

from rust-doom.

Interesting. Could you please send me the output of running ls -lR in the repo's root so I can see all the files under that. Also could you attach the output of RUST_LOG=debug RUST_BACKTRACE=1 target/rs-doom --iwad=doom1.wad as well (essentially what @jadbox attached).

Thanks!

Gah! Sorry @Sekhmet, I misread your comment as "it doesn't work when running from root".

from rust-doom.

Yep, running from the repo root fixed this issue.

from rust-doom.