dskart / rustcraft Goto Github PK

I'm trying to build on macOS Catalina, but getting the following error:

XType: failed to connect - Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service on pid 0 named com.apple.fonts was invalidated." UserInfo={NSDebugDescription=The connection to service on pid 0 named com.apple.fonts was invalidated.} rustcraft[70247:3351893] Font server protocol version mismatch (expected:5 got:0), falling back to local fonts

I was just about to start writing a block engine on Wgpu, then I found rustcraft. Looks like a great start!

Is this going to be an actively developed project?

If so, the first thing I'd like to contribute to is updating to Wgpu 0.8 and moving the shaders to WGSL. I don't have a lot of time or expertise, so I have no idea if this will take me 5 minutes or 5 months. Interested?

Hi
So, First I git cloned the project,checked the dependencies and ran it with the command cargo run --release -- -c .
Here is the output,

sol@solmate:~/Documents/projects/rustcraft$ cargo run --release -- -c
    Finished release [optimized] target(s) in 6.51s
     Running `target/release/rustcraft -c`
May 07 10:15:34.941 INFO Generating World...
wgpu error: Validation Error

Caused by:
    In Device::create_buffer
      note: label = `Vertex Buffer`
    not enough memory left


thread 'main' panicked at 'Handling wgpu errors as fatal by default', /home/sol/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.7.1/src/backend/direct.rs:1896:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Segmentation fault (core dumped)

Which traces back to ,

fn default_error_handler(err: crate::Error) {
    eprintln!("wgpu error: {}\n", err);

    panic!("Handling wgpu errors as fatal by default");
}

and goes back to ,

pub enum Error {
    /// Out of memory error
    OutOfMemoryError {
        ///
        source: Box<dyn error::Error + Send + Sync + 'static>,
    }, 
    ...

I am a Rust beginner ,and there is one thing I am not able to understand here is that if this program is panicking and is going through the usual process of unwinding then why is it seg faulting here ?