You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had this issue also in bevy and could only fix it by choosing the renderer manual . I saw the same errors popping up in the video from gamefromscratch about this engine ;) https://www.youtube.com/watch?v=1w9f2-pyHtc&t=7s
im not an expert, but this could be related to : wgpu bug: gfx-rs/wgpu#3959 that was created by someone of the bevy team
The text was updated successfully, but these errors were encountered:
here some info about the adapter and os:
GPU - AMD Radeon RX 5700 - Primary/Discrete
VRAM - 8176 MB - GDDR6 1750 MHz
Graphics - AMD Radeon RX 5700
Graphics Manufacturer - Powered by AMD
Usable Memory Size - 8176 MB
Core Clock - 1725 MHz
Total Memory Bandwidth - 448 GByte/s
Device ID - 731F
Revision ID - C4
Vendor ID - 1002
SubSystem ID - 04E4
SubSystem Vendor ID - 1043
Bus Type - PCI Express 4.0
Current Bus Settings - PCI Express 4.0 x16
Driver Version - 23.20.11.04-230921a-396203C-AMD-Software-Adrenalin-Edition
AMD Windows Driver Version - 31.0.22011.4008
Direct3D API Version - 12.1
Vulkan™ API Version - 1.3.262
OpenCL™ API Version - 2.0
OpenGL® API Version - 4.6
Direct3D® Driver Version - 9.14.10.01526
Vulkan™ Driver Version - 2.0.283
OpenCL® Driver Version - 31.0.22011.4008
OpenGL® Driver Version - 23.09.230729_569461f
2D Driver Version - 8.1.1.1634
UI Version - 2023.0921.2013.1996
AMD Audio Driver Version - 10.0.1.30
Driver Provider - Advanced Micro Devices, Inc.
Windows Edition - Windows 11 Professional (64 bit)
Windows Version - 22H2
Possibly related gfx-rs/wgpu#4247, seems there's a bunch of strange issues around AMD/Vulkan/DX12/Windows/OBS.
Surprisingly forcing either DX12 or Vulkan backend fixes it in the case when I reproduced it with OBS, but using the default backend doesn't work, even if the default ends up being DX12 or Vulkan. Very strange. I'll keep this open so that we can track it and related issues, though it doesn't look like it's a bug in Comfy itself, but rather somewhere upstream.
One of the next steps here is just updating wgpu to latest version. It's likely not going to help, but just in case.
THE CODE: (as in the example)
use comfy::*;
simple_game!("Nice red circle", update);
fn update(_c: &mut EngineContext) {
draw_circle(vec2(0.0, 0.0), 0.5, RED, 0);
}
the flood of errors:
I had this issue also in bevy and could only fix it by choosing the renderer manual . I saw the same errors popping up in the video from gamefromscratch about this engine ;) https://www.youtube.com/watch?v=1w9f2-pyHtc&t=7s
im not an expert, but this could be related to : wgpu bug: gfx-rs/wgpu#3959 that was created by someone of the bevy team
The text was updated successfully, but these errors were encountered: