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

[Bug] Image count not supported with Vulkan backend on Wayland #1846

Open
jakbyte opened this issue Aug 2, 2019 · 19 comments
Open

[Bug] Image count not supported with Vulkan backend on Wayland #1846

jakbyte opened this issue Aug 2, 2019 · 19 comments

Comments

@jakbyte
Copy link

@jakbyte jakbyte commented Aug 2, 2019

Description

I use an Intel Ivybridge Desktop GPU, which has a minImageCount of 2 (see here). Ever since updating to 0.12, I've been getting the same error every time I try to run my project.

[WARN][rendy_wsi] Image count not supported. Supported: 4..4294967295, requested: 3

Is this why Amethyst warns about Ivybridge Vulkan support?

INTEL-MESA: warning: Ivy Bridge Vulkan support is incomplete

EDIT: This also doesn't work on master and/or with nightly.
EDIT 2: See amethyst/rendy#182

Reproduction Steps

  1. Run the sphere example with Vulkan (the same thing happens)
cargo run --example sphere --features vulkan

What You Expected to Happen

I expected the example to run and display a sphere.

What Actually Happened

I got an error

Screenshots and Logs

Your Environment

  1. Operating System: Arch Linux
  2. Operating System Version: rolling
  3. Version of Amethyst: 0.12

Additional Context

@ishitatsuyuki

This comment has been minimized.

Copy link
Contributor

@ishitatsuyuki ishitatsuyuki commented Aug 4, 2019

AFAIK Mesa is known to have a bug where it has a large minImageCount than what is necessary.

@valkum

This comment has been minimized.

Copy link
Contributor

@valkum valkum commented Aug 5, 2019

But I think we checked with the Vulkan Hardware Capability Viewer as well. Why would Mesa return something different to the Capability Viewer than to us?

@jakbyte

This comment has been minimized.

Copy link
Author

@jakbyte jakbyte commented Aug 6, 2019

Correct me if I'm wrong because I don't really know much about this, but I was thinking that the error was happening because:

  • My GPU's minImageCount is 2
  • Rendy's (specifically rendy-wsi's) minimum is 4
  • The supplied image count is 3

So I'm thinking my GPU would accept the image count, but Rendy's minimum causes a panic.

@valkum

This comment has been minimized.

Copy link
Contributor

@valkum valkum commented Aug 6, 2019

Its I think:

  • GPU's minImageCount really is 2
  • Rendy (specifically rendy-wsi's) wants to setup a surface with (thus supplied) 3 backing images
  • Somehow the GPU or the driver reported to rendy-wsi the minImageCount is 4 thus rendy-wsi returns the error

The question here is: Does Mesa report the wrong image count or is it a problem within rendy-wsi or any dep. For this I asked you (in chat) to run the Vulkan Hardware Capability Viewer to see if the driver really reports the surface capability minImageCount that rendy is getting.

You said yes IIRC. I hope there was no misunderstanding. I meant the value from the program not the value on the website.

I'm not sure if the Vulkan Hardware Capability Viewer does something different than rendy-wsi to get the surface capabilities.

@jakbyte

This comment has been minimized.

Copy link
Author

@jakbyte jakbyte commented Aug 6, 2019

From the Vulkan Hardware Capability Viewer:
image

@lykhouzov

This comment has been minimized.

Copy link

@lykhouzov lykhouzov commented Aug 20, 2019

From the Vulkan Hardware Capability Viewer:
image

Hi, I have the same issue and the same output of Vulkan Hardware Capability Viewer.
Does some one know how to fix the issue?
PS: in my case the difference of TS is only that i have openSuse. and running an app just after a project was created by amethysts new project_name

@navaati

This comment has been minimized.

Copy link

@navaati navaati commented Aug 26, 2019

If like me you just wanted to get your feet wet and get a taste of amethyst, you can do that by following the book for version 0.11, which does not have the bug.

Still hope that one gets fixed soon, version 0.12 looks way easier to use !

@ishitatsuyuki

This comment has been minimized.

Copy link
Contributor

@ishitatsuyuki ishitatsuyuki commented Aug 27, 2019

Please change the issue title/description so it reflects that this is a rendy bug with Wayland.

amethyst/rendy#182

@jakbyte jakbyte changed the title [BUG] Intel Ivybridge Desktop Vulkan support Image count not supported with vulkan backend on wayland. Aug 27, 2019
@jakbyte jakbyte changed the title Image count not supported with vulkan backend on wayland. [Bug] Image count not supported with Vulkan backend on Wayland Aug 27, 2019
@ishitatsuyuki

This comment has been minimized.

Copy link
Contributor

@ishitatsuyuki ishitatsuyuki commented Sep 1, 2019

The upstream issue is resolved. After rendy gets an upgrade, we can close this issue.

@jakbyte

This comment has been minimized.

Copy link
Author

@jakbyte jakbyte commented Sep 8, 2019

I was able to temp fix this by prefixing the command with WINIT_UNIX_BACKEND=x11.

@stale

This comment has been minimized.

Copy link

@stale stale bot commented Nov 7, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Feel free to comment if this ticket is still relevant.

@stale stale bot added the stale label Nov 7, 2019
@ishitatsuyuki

This comment has been minimized.

Copy link
Contributor

@ishitatsuyuki ishitatsuyuki commented Nov 7, 2019

rendy is updated, probably can close this.

@stale stale bot removed the stale label Nov 7, 2019
@navaati

This comment has been minimized.

Copy link

@navaati navaati commented Nov 7, 2019

Hi.

Is the relevant version of rendy used in the last stable/recommended version of amethyst ? Because if not the version needs to be bumped in amethyst’s Cargo.toml…

@ishitatsuyuki

This comment has been minimized.

Copy link
Contributor

@ishitatsuyuki ishitatsuyuki commented Nov 7, 2019

It’s in master, might be unreleased but we close issues right after the fix is merged.

@navaati

This comment has been minimized.

Copy link

@navaati navaati commented Nov 8, 2019

Ok, I’ll keep an eye on releases then, thank you :)

@0x6273

This comment has been minimized.

Copy link
Contributor

@0x6273 0x6273 commented Nov 12, 2019

It's not in amethyst master, since we still depend on rendy 0.4.1. That version still has the image count hard-coded to 3.

@ishitatsuyuki

This comment has been minimized.

Copy link
Contributor

@ishitatsuyuki ishitatsuyuki commented Nov 13, 2019

Sorry that's my mistake. Rendy 0.5 port will probably take a while, so a good way might be to backport the imageCount patch to 0.4 branch.

@distransient distransient reopened this Nov 13, 2019
@Barugon

This comment has been minimized.

Copy link

@Barugon Barugon commented Dec 2, 2019

This is blocking me.

@ishitatsuyuki

This comment has been minimized.

Copy link
Contributor

@ishitatsuyuki ishitatsuyuki commented Dec 2, 2019

why? you could trivially workaround by running with X11.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
8 participants
You can’t perform that action at this time.