首页
学习
活动
专区
圈层
工具
发布
社区首页 >问答首页 >阀门游戏,伪错误!创建交换链,无法查询支持格式的大小!

阀门游戏,伪错误!创建交换链,无法查询支持格式的大小!
EN

Ask Ubuntu用户
提问于 2018-12-08 22:37:01
回答 1查看 1.3K关注 0票数 1

我有Geforce 660米,试着安装台面驱动,但我认为我做了比好更糟糕的事情。如果我在安装台面驱动程序和vulkan月球sdk之前从Nvidia启动英特尔,游戏就开始了(启动它,但是图形很低,没有字体,无法阅读),现在它启动了,但我能听到游戏的声音,我只能看到光标,剩下的是一个黑色的屏幕。同样的情况是,如果我使用Nvidia作为质数,并将-gl设置在水蒸气中的启动设置。

我使用Ubuntu18.04.1。

代码语言:javascript
复制
glxinfo | grep "OpenGL version"
OpenGL version string: 4.6.0 NVIDIA 410.78

也许这会有帮助,当我使用vulkaninfo时,我得到了以下信息:

代码语言:javascript
复制
$ 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)
EN

回答 1

Ask Ubuntu用户

回答已采纳

发布于 2018-12-15 15:47:36

我通过在终端中使用sudo vulkaninfo来解决这个问题,而不仅仅是vulkaninfo,它没有错误地显示所有信息。我不知道为什么我甚至需要使用这个命令,但是在我使用它之后,Artifact就会毫无问题地启动。

票数 2
EN
页面原文内容由Ask Ubuntu提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接:

https://askubuntu.com/questions/1099455

复制
相关文章

相似问题

领券
问题归档专栏文章快讯文章归档关键词归档开发者手册归档开发者手册 Section 归档