web-dev-qa-db-fra.com

Le jeu de la valve, erreur d'artefact! Créer une chaîne d'échange Taille de requête impossible pour les formats pris en charge!

J'ai Geforce 660M, j'ai essayé d'installer des pilotes Mesa, mais je pense avoir fait quelque chose de pire que de bon. Si je mettais Intel de Nvidia sous Intel avec prime-select, le jeu commençait (lancé, mais le graphisme était bas et ne contenait aucune police, il ne lisait rien) avant l’installation des pilotes mesa et du sdk lunaire vulkan, maintenant il est lancé mais je peut entendre le son du jeu et je ne vois que le curseur, le reste est un écran noir. La même chose se produit si j'utilise Nvidia en tant que premier et mets -gl dans les paramètres de lancement définis dans Steam.

J'utilise Ubuntu 18.04.1.

glxinfo | grep "OpenGL version"
OpenGL version string: 4.6.0 NVIDIA 410.78

peut-être que ça aide, quand j’utilise vulkaninfo j’obtiens ceci:

$ 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 = 17VK_EXT_acquire_xlib_display : extension revision 1VK_EXT_debug_report : extension revision 8VK_EXT_debug_utils : extension revision 1VK_EXT_direct_mode_display : extension revision 1VK_EXT_display_surface_counter : extension revision 1VK_KHR_device_group_creation : extension revision 1VK_KHR_display : extension revision 23VK_KHR_external_fence_capabilities : extension revision 1VK_KHR_external_memory_capabilities : extension revision 1VK_KHR_external_semaphore_capabilities: extension revision 1VK_KHR_get_display_properties2 : extension revision 1VK_KHR_get_physical_device_properties2: extension revision 1VK_KHR_get_surface_capabilities2 : extension revision 1VK_KHR_surface : extension revision 25VK_KHR_wayland_surface : extension revision 6VK_KHR_xcb_surface : extension revision 6VK_KHR_xlib_surface : extension revision 6Layers: 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)
driversnvidiagraphicssteamopengl
1
VNM

Je l'ai résolu en utilisant Sudo vulkaninfo dans le terminal au lieu de simplement vulkaninfo et il affiche toutes les informations sans erreur. Je ne sais pas pourquoi j'ai même besoin d'utiliser cette commande, mais après l'avoir utilisée, l'artefact se lance sans problèmes.

2
VNM