Skip to content
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

Window background is incorrect using Vulkan on Windows #2258

Open
2 tasks done
staticintlucas opened this issue Feb 17, 2024 · 5 comments
Open
2 tasks done

Window background is incorrect using Vulkan on Windows #2258

staticintlucas opened this issue Feb 17, 2024 · 5 comments
Labels
bug Something isn't working rendering

Comments

@staticintlucas
Copy link

Is there an existing issue for this?

  • I have searched the existing issues.

Is this issue related to iced?

  • My hardware is compatible and my graphics drivers are up-to-date.

What happened?

image

image

This issue is most noticeable with dark themes. With every dark theme the background is almost solid black. With light themes there is still a small difference.

All UI elements render as expected, only the window background is affected.

On Linux all backends work as expected.

What is the expected behavior?

Background colours should be the same across all backends

Version

crates.io release

Operating System

Windows

Do you have any log output?

No response

@staticintlucas staticintlucas added the bug Something isn't working label Feb 17, 2024
@hecrj
Copy link
Member

hecrj commented Feb 17, 2024

Strange. May be a driver issue, a wgpu bug, or a surface misconfiguration related to #2231.

Could you post the terminal output when running the tour example both for vulkan and dx12?

@staticintlucas
Copy link
Author

Sure, here are the two logs:

vulkan.log
dx12.log

@hecrj
Copy link
Member

hecrj commented Feb 17, 2024

It seems iced is choosing to use your integrated GPU by default, so I would bet this is most likely a driver issue.

You can force iced to use your discrete GPU by enabling the antialiasing flag in Settings, or you could simply try the game_of_life example which enables that already.

@staticintlucas
Copy link
Author

I get the same result with antialiasing = true.

Here are logs of a modified tour example with antialiasing = true. I can confirm it does use my discrete GPU in this case:

vk_aa.log
dx12_aa.log

@staticintlucas
Copy link
Author

Testing further, if I enable the "web-colors" feature I also don't see this issue.

Could this be related to gfx-rs/wgpu#4842?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working rendering
Projects
None yet
Development

No branches or pull requests

2 participants