gfx
gfx copied to clipboard
Rendering issues on macOS Catalina
Short info header:
- GFX version:
0.3.1 - OS:
macOS Catalina - GPU:
Intel UHD Graphics 630 1536 MB
I'm seeing this with a project I'm working on via Amethyst. The window will open to a black screen that doesn't update unless I resize the window, then it seems to work okay. Meanwhile, [WARN][gfx_backend_metal::window] No frame is available repeats ad nauseam.
[[package]]
name = "gfx-backend-metal"
version = "0.3.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"arrayvec 0.4.12 (registry+https://github.com/rust-lang/crates.io-index)",
"bitflags 1.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
"block 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)",
"cocoa 0.19.1 (registry+https://github.com/rust-lang/crates.io-index)",
"copyless 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)",
"core-graphics 0.17.3 (registry+https://github.com/rust-lang/crates.io-index)",
"foreign-types 0.3.2 (registry+https://github.com/rust-lang/crates.io-index)",
"gfx-hal 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
"log 0.4.8 (registry+https://github.com/rust-lang/crates.io-index)",
"metal 0.16.0 (registry+https://github.com/rust-lang/crates.io-index)",
"objc 0.2.7 (registry+https://github.com/rust-lang/crates.io-index)",
"parking_lot 0.9.0 (registry+https://github.com/rust-lang/crates.io-index)",
"range-alloc 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
"raw-window-handle 0.1.2 (registry+https://github.com/rust-lang/crates.io-index)",
"smallvec 0.6.13 (registry+https://github.com/rust-lang/crates.io-index)",
"spirv_cross 0.15.0 (registry+https://github.com/rust-lang/crates.io-index)",
"storage-map 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)",
"winit 0.19.5 (registry+https://github.com/rust-lang/crates.io-index)",
]
Thank you for filing! Do you see this happening on the colour-uniform example?
(marking as medium priority because I hope Amethyst can use the new swapchain model (that our quad example shows) instead of the old one)
Hey again! I actually do not see this issue occurring on the colour-uniform example. Guessing that implies an issue on the Amethyst side. I also noticed that the version of gfx-hal and the Metal backend (guessing others as well) is about a half year behind.