sebbbi / rust_test Goto Github PK

Hi

When I run the sdfrender on my nvidia-1050-maxq laptop, it is basically ok but I can notice some flickering on certain positions (see attachment . e.g upper right ). Is this sort of accuracy issue?

Followed your instructions exactly (did not have Rust nor VulkanSDK installed, so they are all the latests stable versions), and cargo run --release --bin rendersdf gives me:

error[E0432]: unresolved import `ash::version`
   --> C:\Users\woute\.cargo\registry\src\github.com-1ecc6299db9ec823\vk-mem-0.2.2\src\lib.rs:753:18
    |
753 |         use ash::version::{DeviceV1_0, DeviceV1_1, InstanceV1_0};
    |                  ^^^^^^^ could not find `version` in `ash`

For more information about this error, try `rustc --explain E0432`.
error: could not compile `vk-mem` due to previous error

Hey, I tried building this project on a new install of rust and everything but I'm running into a few errors (there are 12 but here are 2 examples):

"error[E0308]: mismatched types
--> src\vulkan_base.rs:351:34
|
351 | physical_device: pdevice,
| ^^^^^^^ expected struct ash::vk::definitions::PhysicalDevice, found struct PhysicalDevice
|
= note: perhaps two different versions of crate ash are being used?

error[E0308]: mismatched types
--> src\vulkan_base.rs:352:25
|
352 | device: device.clone(),
| ^^^^^^^^^^^^^^ expected struct ash::device::Device, found struct vulkan_base::ash::Device
|
= note: perhaps two different versions of crate ash are being used?"

I tried building on various different versions of rust compiler but either they fail to run or they throw the above errors (1.45.0 - 1.50.0). Do you know what might be wrong/if there is a specific rust version I need to use? This is on a Windows machine.

I have been fallowing this project and wonder if it's still active? The second test!

When running in both debug and release modes, I am getting the following error message:

thread 'main' panicked at 'attempted to zero-initialize type `ash::Device`, which is invalid', C:\Users\Sam\.rustup\toolchains\nightly-x86_64-pc-windows-msvc\lib/rustlib/src/rust\library\core\src\mem\mod.rs:623:9`

When tracing through in the debugger, this seems to originate in a bug in the vk_mem crate's Default implementation for AllocatorCreateInfo here. Calling AllocatorCreateInfo::Default() initializes the ash::Device struct with mem::zeroed() as seen here, which according to the runtime panic message is invalid (although I'm not familiar with the specific Rust rules which prevent this.)

In order to avoid this bug in the vk_mem crate, the Default::default() call needs to be avoided here and the default values need to be initialized manually, i.e.:

let allocator_create_info = vk_mem::AllocatorCreateInfo {
    physical_device: pdevice,
    device: device.clone(),
    instance: instance.clone(),
    flags: vk_mem::AllocatorCreateFlags::NONE,
    preferred_large_heap_block_size: 0,
    frame_in_use_count: 0,
    heap_size_limits: None,
};