Steam for Linux

Steam for Linux

[SOLVED] Artifact Error! Create swap chain Unable query size of supported formats
Originally posted by LT | Joe:
i got it fixed atm by using the vulkaninfo command, but with root.
So you enter
$ sudo vulkaninfo

a hell of informations are coming, but they don't really matter
after that vulkaninfo without root also displays the many informations and not the important ones like it normally does

if i run the game now it just works
i also don't know why, but i won't question it for now

---------------------------------------------------------------------------------------------------------------------------------

I have Geforce 660M, tried to install mesa drivers, but I think I did something worst than good. If I switched on Intel from Nvidia with prime-select intel, the game started(launched it, but graphic was low and had no fonts, couldn't read anythink) before installation of mesa drivers and vulkan lunar sdk, now it launches but I can hear the game sound and I can only see the cursor, the rest is a black screen. The same happens if I use Nvidia as prime and put -gl in set launch settings in steam.

edit: my error is: Create swap chain Unable query size of supported formats


I use Ubuntu 18.04.1.
glxinfo | grep "OpenGL version"
OpenGL version string: 4.6.0 NVIDIA 410.78

If anyone have some ideas...Thanks.
Last edited by Silly Goose; Dec 14, 2018 @ 6:05am
< >
Showing 1-10 of 10 comments
Silly Goose Dec 8, 2018 @ 1:47pm 
maybe it helps, when I use vulkaninfo I get this:
$ vulkaninfo
==========
VULKANINFO
==========

Vulkan Instance Version: 1.1.92

ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_intel.so: wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so: wrong ELF class: ELFCLASS32
INTEL-MESA: warning: Ivy Bridge Vulkan support is incomplete


INTEL-MESA: warning: ../src/intel/vulkan/anv_device.c:1204: FINISHME: Implement pop-free point clipping


Instance Extensions:
====================
Instance Extensions count = 17
VK_EXT_acquire_xlib_display : extension revision 1
VK_EXT_debug_report : extension revision 8
VK_EXT_debug_utils : extension revision 1
VK_EXT_direct_mode_display : extension revision 1
VK_EXT_display_surface_counter : extension revision 1
VK_KHR_device_group_creation : extension revision 1
VK_KHR_display : extension revision 23
VK_KHR_external_fence_capabilities : extension revision 1
VK_KHR_external_memory_capabilities : extension revision 1
VK_KHR_external_semaphore_capabilities: extension revision 1
VK_KHR_get_display_properties2 : extension revision 1
VK_KHR_get_physical_device_properties2: extension revision 1
VK_KHR_get_surface_capabilities2 : extension revision 1
VK_KHR_surface : extension revision 25
VK_KHR_wayland_surface : extension revision 6
VK_KHR_xcb_surface : extension revision 6
VK_KHR_xlib_surface : extension revision 6
Layers: count = 16
=======
VK_LAYER_GOOGLE_threading (Google Validation Layer) Vulkan version 1.1.92, layer version 1
Layer Extensions count = 1
VK_EXT_debug_report : extension revision 6
Devices count = 2
GPU id : 0 (GeForce GTX 660M)
Layer-Device Extensions count = 0
GPU id : 1 (Intel(R) Ivybridge Mobile)
Layer-Device Extensions count = 0

VK_LAYER_GOOGLE_unique_objects (Google Validation Layer) Vulkan version 1.1.92, layer version 1
Layer Extensions count = 0
Devices count = 2
GPU id : 0 (GeForce GTX 660M)
Layer-Device Extensions count = 0
GPU id : 1 (Intel(R) Ivybridge Mobile)
Layer-Device Extensions count = 0

VK_LAYER_LUNARG_api_dump (LunarG debug layer) Vulkan version 1.1.92, layer version 2
Layer Extensions count = 0
Devices count = 2
GPU id : 0 (GeForce GTX 660M)
Layer-Device Extensions count = 0
GPU id : 1 (Intel(R) Ivybridge Mobile)
Layer-Device Extensions count = 0

VK_LAYER_LUNARG_assistant_layer (LunarG Validation Layer Factory Layer) Vulkan version 1.1.92, layer version 1
Layer Extensions count = 1
VK_EXT_debug_report : extension revision 6
Devices count = 2
GPU id : 0 (GeForce GTX 660M)
Layer-Device Extensions count = 1
VK_EXT_debug_marker : extension revision 4
GPU id : 1 (Intel(R) Ivybridge Mobile)
Layer-Device Extensions count = 1
VK_EXT_debug_marker : extension revision 4

VK_LAYER_LUNARG_core_validation (LunarG Validation Layer) Vulkan version 1.1.92, layer version 1
Layer Extensions count = 1
VK_EXT_debug_report : extension revision 6
Devices count = 2
GPU id : 0 (GeForce GTX 660M)
Layer-Device Extensions count = 2
VK_EXT_debug_marker : extension revision 4
VK_EXT_validation_cache : extension revision 1
GPU id : 1 (Intel(R) Ivybridge Mobile)
Layer-Device Extensions count = 2
VK_EXT_debug_marker : extension revision 4
VK_EXT_validation_cache : extension revision 1

VK_LAYER_LUNARG_demo_layer (LunarG Validation Layer Factory Layer) Vulkan version 1.1.92, layer version 1
Layer Extensions count = 1
VK_EXT_debug_report : extension revision 6
Devices count = 2
GPU id : 0 (GeForce GTX 660M)
Layer-Device Extensions count = 1
VK_EXT_debug_marker : extension revision 4
GPU id : 1 (Intel(R) Ivybridge Mobile)
Layer-Device Extensions count = 1
VK_EXT_debug_marker : extension revision 4

VK_LAYER_LUNARG_device_simulation (LunarG device simulation layer) Vulkan version 1.1.92, layer version 1
Layer Extensions count = 0
Devices count = 2
GPU id : 0 (GeForce GTX 660M)
Layer-Device Extensions count = 0
GPU id : 1 (Intel(R) Ivybridge Mobile)
Layer-Device Extensions count = 0

VK_LAYER_LUNARG_monitor (Execution Monitoring Layer) Vulkan version 1.1.92, layer version 1
Layer Extensions count = 0
Devices count = 2
GPU id : 0 (GeForce GTX 660M)
Layer-Device Extensions count = 0
GPU id : 1 (Intel(R) Ivybridge Mobile)
Layer-Device Extensions count = 0

VK_LAYER_LUNARG_object_tracker (LunarG Validation Layer) Vulkan version 1.1.92, layer version 1
Layer Extensions count = 1
VK_EXT_debug_report : extension revision 6
Devices count = 2
GPU id : 0 (GeForce GTX 660M)
Layer-Device Extensions count = 1
VK_EXT_debug_marker : extension revision 4
GPU id : 1 (Intel(R) Ivybridge Mobile)
Layer-Device Extensions count = 1
VK_EXT_debug_marker : extension revision 4

VK_LAYER_LUNARG_parameter_validation (LunarG Validation Layer) Vulkan version 1.1.92, layer version 1
Layer Extensions count = 1
VK_EXT_debug_report : extension revision 6
Devices count = 2
GPU id : 0 (GeForce GTX 660M)
Layer-Device Extensions count = 1
VK_EXT_debug_marker : extension revision 4
GPU id : 1 (Intel(R) Ivybridge Mobile)
Layer-Device Extensions count = 1
VK_EXT_debug_marker : extension revision 4

VK_LAYER_LUNARG_screenshot (LunarG image capture layer) Vulkan version 1.1.92, layer version 1
Layer Extensions count = 0
Devices count = 2
GPU id : 0 (GeForce GTX 660M)
Layer-Device Extensions count = 0
GPU id : 1 (Intel(R) Ivybridge Mobile)
Layer-Device Extensions count = 0

VK_LAYER_LUNARG_standard_validation (LunarG Standard Validation) Vulkan version 1.1.92, layer version 1
Layer Extensions count = 1
VK_EXT_debug_report : extension revision 6
Devices count = 2
GPU id : 0 (GeForce GTX 660M)
Layer-Device Extensions count = 2
VK_EXT_debug_marker : extension revision 4
VK_EXT_validation_cache : extension revision 1
GPU id : 1 (Intel(R) Ivybridge Mobile)
Layer-Device Extensions count = 2
VK_EXT_debug_marker : extension revision 4
VK_EXT_validation_cache : extension revision 1

VK_LAYER_LUNARG_starter_layer (LunarG Validation Layer Factory Layer) Vulkan version 1.1.92, layer version 1
Layer Extensions count = 1
VK_EXT_debug_report : extension revision 6
Devices count = 2
GPU id : 0 (GeForce GTX 660M)
Layer-Device Extensions count = 1
VK_EXT_debug_marker : extension revision 4
GPU id : 1 (Intel(R) Ivybridge Mobile)
Layer-Device Extensions count = 1
VK_EXT_debug_marker : extension revision 4

VK_LAYER_LUNARG_vktrace (Vktrace tracing library) Vulkan version 1.1.92, layer version 1
Layer Extensions count = 0
Devices count = 2
GPU id : 0 (GeForce GTX 660M)
Layer-Device Extensions count = 0
GPU id : 1 (Intel(R) Ivybridge Mobile)
Layer-Device Extensions count = 0

VK_LAYER_VALVE_steam_overlay_32 (Steam Overlay Layer) Vulkan version 1.1.73, layer version 1
Layer Extensions count = 0
Devices count = 2
GPU id : 0 (GeForce GTX 660M)
Layer-Device Extensions count = 0
GPU id : 1 (Intel(R) Ivybridge Mobile)
Layer-Device Extensions count = 0

VK_LAYER_VALVE_steam_overlay_64 (Steam Overlay Layer) Vulkan version 1.1.73, layer version 1
Layer Extensions count = 0
Devices count = 2
GPU id : 0 (GeForce GTX 660M)
Layer-Device Extensions count = 0
GPU id : 1 (Intel(R) Ivybridge Mobile)
Layer-Device Extensions count = 0

Presentable Surfaces:
=====================
GPU id : 0 (GeForce GTX 660M)
Surface type : VK_KHR_xcb_surface
vulkaninfo: /build/vulkan-tools-1.1.92.0~rc3/vulkaninfo/vulkaninfo.c:1309: AppDumpSurfaceFormats: Assertion `!err' failed.
Aborted (core dumped)
Silly Goose Dec 8, 2018 @ 2:08pm 
This might mean you can't use your Intel GPU for Vulkan games.

I don't really want to do that, I hope I can play it with Nvidia GPU, eventually...
Silly Goose Dec 8, 2018 @ 2:28pm 
Originally posted by Rogue:
Originally posted by formidabilis_VNM:
This might mean you can't use your Intel GPU for Vulkan games.

I don't really want to do that, I hope I can play it with Nvidia GPU, eventually...

Have you tried running the game on your Nvidia GPU without the "-gl" launch option?


Yes, that's the situation from where the error is. Using -vulkan or not using any launch options give me this error.
LT | Joe Dec 12, 2018 @ 10:50am 
i got it fixed atm by using the vulkaninfo command, but with root.
So you enter
$ sudo vulkaninfo

a hell of informations are coming, but they don't really matter
after that vulkaninfo without root also displays the many informations and not the important ones like it normally does

if i run the game now it just works
i also don't know why, but i won't question it for now
Silly Goose Dec 13, 2018 @ 3:17pm 
Originally posted by LT | Joe:
i got it fixed atm by using the vulkaninfo command, but with root.
So you enter
$ sudo vulkaninfo

a hell of informations are coming, but they don't really matter
after that vulkaninfo without root also displays the many informations and not the important ones like it normally does

if i run the game now it just works
i also don't know why, but i won't question it for now


Sir, I love you! It works after I use "sudo vulkaninfo" command. This is very strange. Thank you so much! :D
Aoi Blue Dec 13, 2018 @ 6:09pm 
Info on your vulkan driver is now in glxinfo as well.
Silly Goose Dec 14, 2018 @ 4:19am 
that's for mesa(amd, intel), I use nvidia and it doesn't if I don't use the "sudo vulkaninfo" command, if I use just "vulkaninfo" without the "sudo" it doesn't work and it's strange in first place that we need to use this command and in the 2nd place that we need to use sudo.
Aoi Blue Dec 14, 2018 @ 4:59am 
Originally posted by formidabilis_VNM:
that's for mesa(amd, intel), I use nvidia and it doesn't if I don't use the "sudo vulkaninfo" command, if I use just "vulkaninfo" without the "sudo" it doesn't work and it's strange in first place that we need to use this command and in the 2nd place that we need to use sudo.
I believe it reports any Vulkan socketed through GLX. I'm not sure if nVidia's Vulkan driver has a GLX interface, though.


Just because a utility is released by Mesa, doesn't mean it's only for use with Mesa drivers.
Last edited by Aoi Blue; Dec 14, 2018 @ 4:59am
Silly Goose Dec 14, 2018 @ 6:03am 
Originally posted by Aoi Blue:
Originally posted by formidabilis_VNM:
that's for mesa(amd, intel), I use nvidia and it doesn't if I don't use the "sudo vulkaninfo" command, if I use just "vulkaninfo" without the "sudo" it doesn't work and it's strange in first place that we need to use this command and in the 2nd place that we need to use sudo.
I believe it reports any Vulkan socketed through GLX. I'm not sure if nVidia's Vulkan driver has a GLX interface, though.


Just because a utility is released by Mesa, doesn't mean it's only for use with Mesa drivers.


Yes, but for that you need to install mesa-utils or something wich I don't have now using a fresh install with just nvidia-415 driver installed.
Aoi Blue Dec 14, 2018 @ 1:20pm 
Originally posted by formidabilis_VNM:
Originally posted by Aoi Blue:
I believe it reports any Vulkan socketed through GLX. I'm not sure if nVidia's Vulkan driver has a GLX interface, though.


Just because a utility is released by Mesa, doesn't mean it's only for use with Mesa drivers.


Yes, but for that you need to install mesa-utils or something wich I don't have now using a fresh install with just nvidia-415 driver installed.
Yeah, the package won't be installed by default if you are running a strip install.

As of the sudo on vulkaninfo, I don't see why it's necessary either. It's not necessary on my system. (BTW, the output is insanely long.)
< >
Showing 1-10 of 10 comments
Per page: 1530 50

Date Posted: Dec 8, 2018 @ 1:35pm
Posts: 10