Skip to content
This repository has been archived by the owner on Aug 22, 2020. It is now read-only.

All examples fail #29

Closed
mkhan45 opened this issue Apr 26, 2020 · 5 comments
Closed

All examples fail #29

mkhan45 opened this issue Apr 26, 2020 · 5 comments

Comments

@mkhan45
Copy link

mkhan45 commented Apr 26, 2020

On running any example, I get this output:

[2020-04-26T22:22:19Z WARN  wgpu_core::device] Requested size 1024x768 is outside of the supported range: Extent2D { width: 1920, height: 1163 }..=Extent2D { width: 1920, height: 1163 }
[2020-04-26T22:22:19Z ERROR gfx_backend_vulkan]
    VALIDATION [VUID-VkSwapchainCreateInfoKHR-imageExtent-01274 (2094043421)] : Validation Error: [ VUID-VkSwapchainCreateInfoKHR-imageExtent-01274 ] Object 0: handle = 0x563fa61ff030, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0x7cd0911d | vkCreateSwapchainKHR() called with imageExtent = (1024,768), which is outside the bounds returned by vkGetPhysicalDeviceSurfaceCapabilitiesKHR(): currentExtent = (1920,1163), minImageExtent = (1920,1163), maxImageExtent = (1920,1163). The Vulkan spec states: imageExtent must be between minImageExtent and maxImageExtent, inclusive, where minImageExtent and maxImageExtent are members of the VkSurfaceCapabilitiesKHR structure returned by vkGetPhysicalDeviceSurfaceCapabilitiesKHR for the surface (https://www.khronos.org/registry/vulkan/specs/1.1-extensions/html/vkspec.html#VUID-VkSwapchainCreateInfoKHR-imageExtent-01274)
    object info: (type: DEVICE, hndl: 94831370039344)

[2020-04-26T22:22:27Z WARN  gfx_memory::heaps] Unable to allocate 134217728 with Linear: TooManyObjects
[2020-04-26T22:22:28Z WARN  wgpu_core::device] Requested size 1024x768 is outside of the supported range: Extent2D { width: 1920, height: 1163 }..=Extent2D { width: 1920, height: 1163 }
[2020-04-26T22:22:28Z ERROR gfx_backend_vulkan]
    VALIDATION [VUID-VkSwapchainCreateInfoKHR-imageExtent-01274 (2094043421)] : Validation Error: [ VUID-VkSwapchainCreateInfoKHR-imageExtent-01274 ] Object 0: handle = 0x563fa61ff030, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0x7cd0911d | vkCreateSwapchainKHR() called with imageExtent = (1024,768), which is outside the bounds returned by vkGetPhysicalDeviceSurfaceCapabilitiesKHR(): currentExtent = (1920,1163), minImageExtent = (1920,1163), maxImageExtent = (1920,1163). The Vulkan spec states: imageExtent must be between minImageExtent and maxImageExtent, inclusive, where minImageExtent and maxImageExtent are members of the VkSurfaceCapabilitiesKHR structure returned by vkGetPhysicalDeviceSurfaceCapabilitiesKHR for the surface (https://www.khronos.org/registry/vulkan/specs/1.1-extensions/html/vkspec.html#VUID-VkSwapchainCreateInfoKHR-imageExtent-01274)
    object info: (type: DEVICE, hndl: 94831370039344)

thread 'main' panicked at 'assertion failed: `(left == right)`
  left: `Extent { width: 1024, height: 768, depth: 1 }`,
 right: `Extent { width: 1920, height: 1163, depth: 1 }`', <::std::macros::panic macros>:5:6
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I think it has something to do with multi monitor, but I disabled one and got the same error. For reference, one of my monitors is 1024x768 and the other is 1900x1200

OS: Void Linux x86_64, kernel 5.4.35_1
GPU: rx 480
CPU: i5 6500
gpu drivers: amdgpu 19.1.0_2, amdvlk 2020.Q2.1_1, mesa-vulkan-radeon 20.0.5_1

This looks like a promising game engine! I'll try to fix the error myself and possibly make a PR, but I'm short on time so no promises

@mkhan45
Copy link
Author

mkhan45 commented Apr 26, 2020

This might be the same as #28 as the final panic is the same, but there are some additional warnings that I'm not sure are relevant

@StarArawn
Copy link
Owner

Thanks for reporting! looks to be the same as #28 , but were you resizing the window when the crash occurred?

@StarArawn StarArawn added this to To do in Harmony 0.0 to 0.1 Apr 26, 2020
@StarArawn StarArawn moved this from To do to In progress in Harmony 0.0 to 0.1 Apr 26, 2020
@mkhan45
Copy link
Author

mkhan45 commented Apr 26, 2020

yep, I was unintentionally resizing because of my tiling window manager, I guess this is exactly the same as #28 as the warnings disappear in floating mode

@mkhan45 mkhan45 closed this as completed Apr 26, 2020
Harmony 0.0 to 0.1 automation moved this from In progress to Done Apr 26, 2020
@mkhan45
Copy link
Author

mkhan45 commented Apr 26, 2020

Oops I guess closing this messes up the project automation

@StarArawn
Copy link
Owner

@mkhan45 It's good let's leave it closed! I have both in the project. Plus I'm mostly using the project for my own usage.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Development

No branches or pull requests

2 participants