-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Canvas examples on MacOS don't work #342
Comments
Realizing it’s possible I confused which code was which release/under development. |
I can't seem to reproduce the issue on macOS 10.15.3. The examples work as intended, even after a
Yes, that's correct.
We upgraded
|
No, they fail in the same way. |
Okay I did some searching, 99e020c seems to break it |
What happens if you disable |
That does it! With antialiasing off the clock works. |
Ok! Does the |
Ahhh nope. It loads and I get a panic when I press left or right. Don't think I realized there was more to it than just getting the image to show up when I tested above. Here's a backtrace:
|
Seems to be the related to this issue: gfx-rs/wgpu-rs#91 |
The If it works for you until you press left or right, then |
Hmm yeah I see msaa-line starts at 4, but then whether I go to 2 or 8 it panics.
|
You do, the buttons are there. This is probably a bug in the blit I double checked the shaders and the logic, and I am not sure what could exactly be causing it. I can't reproduce it. It works on my MacBook and my desktop with Linux and Windows. |
Oh I thought you were referring to the little white squares. Today is pretty much the first time I've looked at Rust, and the first time I've looked at this (awesome looking) library, so its likely this is either very wrong, or obvious: but I dug around a bit more to at least try to find where, and it seems like maybe it's related to the way these lines work? https://github.com/hecrj/iced/blob/d807ef367e0257ba54f8cf38708a7a61e28a4acb/wgpu/src/triangle.rs#L290-L358 When antialiasing is on, |
Yes, that is expected. When MSAA is enabled, in order to not overwrite the contents of the next frame, we need to resolve to a texture and blit it. I believe the blit part of the process somehow doesn't work in your system. |
FWIW, I have had similar reports with macOS 10.14.16 causing black screen in |
I'm still getting the issues with the canvas when compiling from master (038f75e) when antialiasing is turned on. I confirmed that turning off shows the grid and other stuff. Also on OSX 10.14.6. See `cargo tree -p game_of_life` output
|
Posting here because this seems like the same issue I'm having, but mine's even worse somehow. When
the OS crash log shows this backtrace: https://gist.github.com/JarrettBillingsley/7f67fbb15f62fe3dda087283aedb1e7b Setting I'm on a 2015 Macbook Air running mac OS 10.15.5 with intel HD graphics 6000. |
@JarrettBillingsley It doesn't seem like the same issue. |
(responded on Zulip) |
0.1.1 seems to have broken the Canvas widget on Mac OS. When trying to run the clock, solar_system, bezier_tool examples on MacOS 10.14.6 get a blank, white, screen where I believe the Canvas is supposed to be. Running game_of_life presents a gray screen, and all the surrounding menu components but does not show any of the white "cell" pieces.
Manually switching to the 0.1 branch and testing the ones that exist there seems to work fine.
The text was updated successfully, but these errors were encountered: