can no longer build at all

[rustylabs]

Running cargo r I get this issue:

thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', /home/raj/.cargo/registry/src/index.crates.io-6f17d22bba15001f/blue_engine-0.4.28/src/render.rs:59:14
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

[ElhamAryanpur]

I see, please write your OS and environment, I do not know how to reproduce it yet

[rustylabs]

I use same os as you man lol Sent from Proton Mail mobile

…

-------- Original Message --------

On 4 Jan. 2024, 3:50 pm, Elham Aryanpur wrote: I see, please write your OS and environment, I do not know how to reproduce it yet — Reply to this email directly, [view it on GitHub](#51 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AZDKAUH5ALY2PFH2PKIPQTTYMYYJ5AVCNFSM6AAAAABBMJZPS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZWGMYDQNBTGI). You are receiving this because you authored the thread.Message ID: ***@***.***>

[rustylabs]

Moved to 0.5, no longer having issues, closing ticket.

[rustylabs]

I am on 0.5 and still issue persists.

[rustylabs]

thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', /home/raj/.cargo/registry/src/index.crates.io-6f17d22bba15001f/blue_engine-0.5.0/src/render.rs:59:14
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

[Gipson62]

This happens because wgpu can't find your GPU, so the engine stops, are you sure your GPU is accessible, or you're on a device with one?

[rustylabs]

@Gipson62 I don't know why doing a ful system update messes chnages my drivers, thanks for letting me know.

[Gipson62]

Know that when you get this type of error (in render.rs line 59) it's a GPU error from wgpu. And yeah, sometimes drivers are messed up on some Linux distro because of system updates.

[ElhamAryanpur]

Yeah gipson is right, that error is from engine not being able to get access for rendering, which means driver not working correctly

[rustylabs]

Yep now working thanks