Closed voxelias closed 3 years ago
Thank you for filing! is this on wgpu-0.6? or on master? There is a few links to check wrt debugging:
I'm going to look at it ASAP. In the meantime, if you run the app from Visual Studio, you should see in the output console what D3D validation error is with regards to this operation.
Hello @kvark, I experienced it on the latest master branch at the moment (10f35360a07de9d297eaf5a193ff4e3007665cfe). on wgpu-0.6 both examples (water and shadow) work fine.
Ok, in this case, there is a chance we are seeing https://github.com/zakarumych/gpu-alloc/pull/24 Migration to gpu-alloc happened recently, and it's not tested, and very young. I'm going to look closer at the issue tonight.
For the record, I double-checked the water example on latest wgpu-rs on Win10 with Intel GPU, and it runs without issues.
Could you log the adapter.get_info()
output somewhere?
Ok, I'm not able to reproduce this so far. Please provide the adapter info as well as the output of the test case ran from Visual Studio. This should be easy to fix.
Unable to reproduce on AMD/Windows/Vulkan either
Hello @kvark, sorry for the late response. I have just pulled the latest changes from master and now everything seems to be working (probably the issue can be closed).
Just in case, I am sending the info about my GPU as requested above: My adapter: AdapterInfo { name: "GeForce GT 650M", vendor: 4318, device: 4049, device_type: DiscreteGpu, backend: Vulkan }
Hello! I am working on a renderer.
Execution fails in this function on
wgpu::Device::create_texture
:Full traceback is here:
It happens only on Windows 10. On MacOS everthing works as expected.
The full code is here: lowenware/dotrix you can run the example with
RUST_BACKTRACE=1 cargo run --release --example demo
Is that wgpu issue or I did something wrong?
EDIT: I believe it is on WGPU side. The
water
example fails to start too on Win 10: