#452 Version 4.2.0 status tracker

Lezárt
megnyitva ekkor: 6 hónapja Krock által · 2 hozzászólás
Krock hozzászólt 6 hónapja

Official release: 8 Nov (pre-download 6 Nov)

Same as in 4.1, I will again provide a script with the updated logging servers. Aside from that I assume that the game stays playable out of the box using Wine.

Please only leave a comment if you have questions or helpful inputs. In case you run into issues, feel free to open a new ticket so that we can have a look at it and work on a solution. The TROUBLESHOOTING.md and TWEAKS.md documents might still be imperfect or incomplete, thus your input is highly welcomed to improve the gameplay experience.

kitten

Official release: 8 Nov (pre-download 6 Nov) Same as in 4.1, I will again provide a script with the updated logging servers. Aside from that I assume that the game stays playable out of the box using Wine. Please only leave a comment if you have questions or helpful inputs. In case you run into issues, feel free to open a new ticket so that we can have a look at it and work on a solution. The TROUBLESHOOTING.md and TWEAKS.md documents might still be imperfect or incomplete, thus your input is highly welcomed to improve the gameplay experience. ![kitten](http://www.randomkittengenerator.com/cats/rotator.php)
jajedi hozzászólt 6 hónapja

Not related to the patch but I have a problem, when I try to launch the game inside gamescope but as soon as it tries to jump into 3D loading screen it immediately crashes. The game worked fine outside it but it's unbearably laggy. I can't capture the log because of official Proton. I'm trying to investigate of what could go wrong.

This is so far of what it told me in the console

Started initial process 88092 from gamescope -w 1280 -h 720 -W 1280 -H 720 -r 38 -f -F fsr --fsr-sharpness 20 -- gamemoderun /usr/bin/wine /hdd/nate/Games/Genshin Impact/Genshin Impact game/GenshinImpact.exe
Start monitoring process.
No CAP_SYS_NICE, falling back to regular-priority compute and threads.
Performance will be affected.
Your Wayland compositor does NOT support wp_presentation/presentation-time which is required for VK_KHR_present_wait and VK_KHR_present_id.
Please complain to your compositor vendor for support. Falling back to X11 window with less accurate present wait.
wlserver: [backend/headless/backend.c:68] Creating headless backend
vulkan: selecting physical device 'AMD Radeon Vega 8 Graphics (RADV RAVEN)': queue family 1 (general queue family 0)
vulkan: physical device supports DRM format modifiers
vulkan: supported DRM formats for sampling usage:
vulkan:   AR24 (0x34325241)
vulkan:   XR24 (0x34325258)
vulkan:   AB24 (0x34324241)
vulkan:   XB24 (0x34324258)
vulkan:   RG16 (0x36314752)
vulkan:   NV12 (0x3231564E)
vulkan:   AB4H (0x48344241)
vulkan:   XB4H (0x48344258)
vulkan:   AB48 (0x38344241)
vulkan:   XB48 (0x38344258)
vulkan:   AB30 (0x30334241)
vulkan:   XB30 (0x30334258)
vulkan:   AR30 (0x30335241)
vulkan:   XR30 (0x30335258)
wlserver: Running compositor on wayland display 'gamescope-0'
wlserver: [backend/headless/backend.c:16] Starting headless backend
wlserver: [xwayland/sockets.c:63] Failed to bind socket @/tmp/.X11-unix/X0: Address already in use
wlserver: [xwayland/server.c:108] Starting Xwayland on :2
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Could not resolve keysym XF86CameraAccessEnable
> Warning:          Could not resolve keysym XF86CameraAccessDisable
> Warning:          Could not resolve keysym XF86CameraAccessToggle
> Warning:          Could not resolve keysym XF86NextElement
> Warning:          Could not resolve keysym XF86PreviousElement
> Warning:          Could not resolve keysym XF86AutopilotEngageToggle
> Warning:          Could not resolve keysym XF86MarkWaypoint
> Warning:          Could not resolve keysym XF86Sos
> Warning:          Could not resolve keysym XF86NavChart
> Warning:          Could not resolve keysym XF86FishingChart
> Warning:          Could not resolve keysym XF86SingleRangeRadar
> Warning:          Could not resolve keysym XF86DualRangeRadar
> Warning:          Could not resolve keysym XF86RadarOverlay
> Warning:          Could not resolve keysym XF86TraditionalSonar
> Warning:          Could not resolve keysym XF86ClearvuSonar
> Warning:          Could not resolve keysym XF86SidevuSonar
> Warning:          Could not resolve keysym XF86NavInfo
Errors from xkbcomp are not fatal to the X server
wlserver: [types/wlr_compositor.c:673] New wlr_surface 0x5580b4e6c0e0 (res 0x5580b4d7dcb0)
wlserver: [xwayland/server.c:273] Xserver is ready
pipewire: stream state changed: connecting
pipewire: stream state changed: paused
pipewire: stream available on node ID: 39
gamemodeauto: 
[2023-11-10 21:12:12.087] MultiThreadStackTrace init success!
Set new unhandled exception filter 00006FFFFD028000 to replace 00006FFFFD16E7A0
[2023-11-10 21:12:13.557] Read and enabled 0 persistent code switches
GCGMAH active
url fetch responce: {"code":0}
url fetch responce: {"retcode":0,"message":"success","data":null}
url fetch responce: {"code":0,"message":"app running","milliTs":"1699621938502"}
ATTENTION: default value of option vk_khr_present_wait overridden by environment.
ATTENTION: default value of option vk_khr_present_wait overridden by environment.
wlserver: [types/wlr_compositor.c:673] New wlr_surface 0x5580b4f59860 (res 0x5580b4e67fe0)
xwm: Unhandled initial NET_WM_STATE property: _NET_WM_STATE_ABOVE
wlserver: [types/wlr_compositor.c:673] New wlr_surface 0x5580b4f59cc0 (res 0x5580b4e68220)
[Gamescope WSI] Creating Gamescope surface: xid: 0xa00035
[Gamescope WSI] Atom of T was wrong type. Expected XCB_ATOM_CARDINAL.
[Gamescope WSI] Atom of T was wrong type. Expected XCB_ATOM_CARDINAL.
[Gamescope WSI] Made gamescope surface for xid: 0xa00035
[Gamescope WSI] Surface state:
  steam app id:                  0
wlserver:   window xid:                    0xa00035
  wayland surface res id:        5
[types/wlr_compositor.c:673] New wlr_surface 0x5580b4f5a0d0 (res 0x5580b4e686d0)  layer client flags:            0x0

  server hdr output enabled:     false
  hdr formats exposed to client: false
[Gamescope WSI] Creating swapchain for xid: 0xa00035 - minImageCount: 4 - format: VK_FORMAT_R8G8B8A8_SRGB - colorspace: VK_COLOR_SPACE_SRGB_NONLINEAR_KHR - flip: true
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported maximum keycode 708, clipping.
>                   X11 cannot support keycodes above 255.
> Warning:          Could not resolve keysym XF86CameraAccessEnable
> Warning:          Could not resolve keysym XF86CameraAccessDisable
> Warning:          Could not resolve keysym XF86CameraAccessToggle
> Warning:          Could not resolve keysym XF86NextElement
> Warning:          Could not resolve keysym XF86PreviousElement
> Warning:          Could not resolve keysym XF86AutopilotEngageToggle
> Warning:          Could not resolve keysym XF86MarkWaypoint
> Warning:          Could not resolve keysym XF86Sos
> Warning:          Could not resolve keysym XF86NavChart
> Warning:          Could not resolve keysym XF86FishingChart
> Warning:          Could not resolve keysym XF86SingleRangeRadar
> Warning:          Could not resolve keysym XF86DualRangeRadar
> Warning:          Could not resolve keysym XF86RadarOverlay
> Warning:          Could not resolve keysym XF86TraditionalSonar
> Warning:          Could not resolve keysym XF86ClearvuSonar
> Warning:          Could not resolve keysym XF86SidevuSonar
> Warning:          Could not resolve keysym XF86NavInfo
Errors from xkbcomp are not fatal to the X server
[Gamescope WSI] Created swapchain for xid: 0xa00035 - imageCount: 4
xwm: Unhandled NET_WM_STATE property change: _KDE_NET_WM_STATE_SKIP_SWITCHER
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_ABOVE
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_VERT
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_HORZ
xwm: Unhandled NET_WM_STATE property change: _KDE_NET_WM_STATE_SKIP_SWITCHER
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_ABOVE
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_VERT
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_HORZ
[Gamescope WSI] Creating swapchain for xid: 0xa00035 - minImageCount: 4 - format: VK_FORMAT_R8G8B8A8_SRGB - colorspace: VK_COLOR_SPACE_SRGB_NONLINEAR_KHR - flip: true
[Gamescope WSI] Created swapchain for xid: 0xa00035 - imageCount: 4
[Gamescope WSI] Swapchain recieved new refresh cycle: 26.32ms
pipewire: renegotiating stream params (size: 1920x1080)
pipewire: renegotiating stream params (size: 1280x720)
[Gamescope WSI] Swapchain recieved new refresh cycle: 16.67ms
xwm: Unhandled NET_WM_STATE property change: _KDE_NET_WM_STATE_SKIP_SWITCHER
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_ABOVE
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_VERT
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_HORZ
xwm: Unhandled NET_WM_STATE property change: _KDE_NET_WM_STATE_SKIP_SWITCHER
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_ABOVE
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_VERT
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_HORZ
xwm: Unhandled NET_WM_STATE property change: _KDE_NET_WM_STATE_SKIP_SWITCHER
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_ABOVE
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_VERT
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_HORZ
xwm: Unhandled NET_WM_STATE property change: _KDE_NET_WM_STATE_SKIP_SWITCHER
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_ABOVE
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_VERT
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_HORZ
# Where it freezes for less than a second and crashes.
xwm: error 3: BadWindow (invalid Window parameter) request 18 minor 0 serial 23604
xwm: error 3: BadWindow (invalid Window parameter) request 42 minor 0 serial 23605
xwm: error 3: BadWindow (invalid Window parameter) request 41 minor 0 serial 23616
xwm: error 3: BadWindow (invalid Window parameter) request 12 minor 0 serial 23617
xwm: error 3: BadWindow (invalid Window parameter) request 12 minor 0 serial 23618
xwm: error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 23619
gamemodeauto: 
gamescope: children shut down!
(EE) failed to read Wayland events: Broken pipe
Monitored process exited.
Initial process has exited (return code: 0)
All processes have quit
Exit with return code 0
Not related to the patch but I have a problem, when I try to launch the game inside `gamescope` but as soon as it tries to jump into 3D loading screen it immediately crashes. The game worked fine outside it but it's unbearably laggy. I can't capture the log because of official Proton. I'm trying to investigate of what could go wrong. This is so far of what it told me in the console ```sh Started initial process 88092 from gamescope -w 1280 -h 720 -W 1280 -H 720 -r 38 -f -F fsr --fsr-sharpness 20 -- gamemoderun /usr/bin/wine /hdd/nate/Games/Genshin Impact/Genshin Impact game/GenshinImpact.exe Start monitoring process. No CAP_SYS_NICE, falling back to regular-priority compute and threads. Performance will be affected. Your Wayland compositor does NOT support wp_presentation/presentation-time which is required for VK_KHR_present_wait and VK_KHR_present_id. Please complain to your compositor vendor for support. Falling back to X11 window with less accurate present wait. wlserver: [backend/headless/backend.c:68] Creating headless backend vulkan: selecting physical device 'AMD Radeon Vega 8 Graphics (RADV RAVEN)': queue family 1 (general queue family 0) vulkan: physical device supports DRM format modifiers vulkan: supported DRM formats for sampling usage: vulkan: AR24 (0x34325241) vulkan: XR24 (0x34325258) vulkan: AB24 (0x34324241) vulkan: XB24 (0x34324258) vulkan: RG16 (0x36314752) vulkan: NV12 (0x3231564E) vulkan: AB4H (0x48344241) vulkan: XB4H (0x48344258) vulkan: AB48 (0x38344241) vulkan: XB48 (0x38344258) vulkan: AB30 (0x30334241) vulkan: XB30 (0x30334258) vulkan: AR30 (0x30335241) vulkan: XR30 (0x30335258) wlserver: Running compositor on wayland display 'gamescope-0' wlserver: [backend/headless/backend.c:16] Starting headless backend wlserver: [xwayland/sockets.c:63] Failed to bind socket @/tmp/.X11-unix/X0: Address already in use wlserver: [xwayland/server.c:108] Starting Xwayland on :2 The XKEYBOARD keymap compiler (xkbcomp) reports: > Warning: Could not resolve keysym XF86CameraAccessEnable > Warning: Could not resolve keysym XF86CameraAccessDisable > Warning: Could not resolve keysym XF86CameraAccessToggle > Warning: Could not resolve keysym XF86NextElement > Warning: Could not resolve keysym XF86PreviousElement > Warning: Could not resolve keysym XF86AutopilotEngageToggle > Warning: Could not resolve keysym XF86MarkWaypoint > Warning: Could not resolve keysym XF86Sos > Warning: Could not resolve keysym XF86NavChart > Warning: Could not resolve keysym XF86FishingChart > Warning: Could not resolve keysym XF86SingleRangeRadar > Warning: Could not resolve keysym XF86DualRangeRadar > Warning: Could not resolve keysym XF86RadarOverlay > Warning: Could not resolve keysym XF86TraditionalSonar > Warning: Could not resolve keysym XF86ClearvuSonar > Warning: Could not resolve keysym XF86SidevuSonar > Warning: Could not resolve keysym XF86NavInfo Errors from xkbcomp are not fatal to the X server wlserver: [types/wlr_compositor.c:673] New wlr_surface 0x5580b4e6c0e0 (res 0x5580b4d7dcb0) wlserver: [xwayland/server.c:273] Xserver is ready pipewire: stream state changed: connecting pipewire: stream state changed: paused pipewire: stream available on node ID: 39 gamemodeauto: [2023-11-10 21:12:12.087] MultiThreadStackTrace init success! Set new unhandled exception filter 00006FFFFD028000 to replace 00006FFFFD16E7A0 [2023-11-10 21:12:13.557] Read and enabled 0 persistent code switches GCGMAH active url fetch responce: {"code":0} url fetch responce: {"retcode":0,"message":"success","data":null} url fetch responce: {"code":0,"message":"app running","milliTs":"1699621938502"} ATTENTION: default value of option vk_khr_present_wait overridden by environment. ATTENTION: default value of option vk_khr_present_wait overridden by environment. wlserver: [types/wlr_compositor.c:673] New wlr_surface 0x5580b4f59860 (res 0x5580b4e67fe0) xwm: Unhandled initial NET_WM_STATE property: _NET_WM_STATE_ABOVE wlserver: [types/wlr_compositor.c:673] New wlr_surface 0x5580b4f59cc0 (res 0x5580b4e68220) [Gamescope WSI] Creating Gamescope surface: xid: 0xa00035 [Gamescope WSI] Atom of T was wrong type. Expected XCB_ATOM_CARDINAL. [Gamescope WSI] Atom of T was wrong type. Expected XCB_ATOM_CARDINAL. [Gamescope WSI] Made gamescope surface for xid: 0xa00035 [Gamescope WSI] Surface state: steam app id: 0 wlserver: window xid: 0xa00035 wayland surface res id: 5 [types/wlr_compositor.c:673] New wlr_surface 0x5580b4f5a0d0 (res 0x5580b4e686d0) layer client flags: 0x0 server hdr output enabled: false hdr formats exposed to client: false [Gamescope WSI] Creating swapchain for xid: 0xa00035 - minImageCount: 4 - format: VK_FORMAT_R8G8B8A8_SRGB - colorspace: VK_COLOR_SPACE_SRGB_NONLINEAR_KHR - flip: true The XKEYBOARD keymap compiler (xkbcomp) reports: > Warning: Unsupported maximum keycode 708, clipping. > X11 cannot support keycodes above 255. > Warning: Could not resolve keysym XF86CameraAccessEnable > Warning: Could not resolve keysym XF86CameraAccessDisable > Warning: Could not resolve keysym XF86CameraAccessToggle > Warning: Could not resolve keysym XF86NextElement > Warning: Could not resolve keysym XF86PreviousElement > Warning: Could not resolve keysym XF86AutopilotEngageToggle > Warning: Could not resolve keysym XF86MarkWaypoint > Warning: Could not resolve keysym XF86Sos > Warning: Could not resolve keysym XF86NavChart > Warning: Could not resolve keysym XF86FishingChart > Warning: Could not resolve keysym XF86SingleRangeRadar > Warning: Could not resolve keysym XF86DualRangeRadar > Warning: Could not resolve keysym XF86RadarOverlay > Warning: Could not resolve keysym XF86TraditionalSonar > Warning: Could not resolve keysym XF86ClearvuSonar > Warning: Could not resolve keysym XF86SidevuSonar > Warning: Could not resolve keysym XF86NavInfo Errors from xkbcomp are not fatal to the X server [Gamescope WSI] Created swapchain for xid: 0xa00035 - imageCount: 4 xwm: Unhandled NET_WM_STATE property change: _KDE_NET_WM_STATE_SKIP_SWITCHER xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_ABOVE xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_VERT xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_HORZ xwm: Unhandled NET_WM_STATE property change: _KDE_NET_WM_STATE_SKIP_SWITCHER xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_ABOVE xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_VERT xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_HORZ [Gamescope WSI] Creating swapchain for xid: 0xa00035 - minImageCount: 4 - format: VK_FORMAT_R8G8B8A8_SRGB - colorspace: VK_COLOR_SPACE_SRGB_NONLINEAR_KHR - flip: true [Gamescope WSI] Created swapchain for xid: 0xa00035 - imageCount: 4 [Gamescope WSI] Swapchain recieved new refresh cycle: 26.32ms pipewire: renegotiating stream params (size: 1920x1080) pipewire: renegotiating stream params (size: 1280x720) [Gamescope WSI] Swapchain recieved new refresh cycle: 16.67ms xwm: Unhandled NET_WM_STATE property change: _KDE_NET_WM_STATE_SKIP_SWITCHER xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_ABOVE xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_VERT xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_HORZ xwm: Unhandled NET_WM_STATE property change: _KDE_NET_WM_STATE_SKIP_SWITCHER xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_ABOVE xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_VERT xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_HORZ xwm: Unhandled NET_WM_STATE property change: _KDE_NET_WM_STATE_SKIP_SWITCHER xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_ABOVE xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_VERT xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_HORZ xwm: Unhandled NET_WM_STATE property change: _KDE_NET_WM_STATE_SKIP_SWITCHER xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_ABOVE xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_VERT xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_HORZ # Where it freezes for less than a second and crashes. xwm: error 3: BadWindow (invalid Window parameter) request 18 minor 0 serial 23604 xwm: error 3: BadWindow (invalid Window parameter) request 42 minor 0 serial 23605 xwm: error 3: BadWindow (invalid Window parameter) request 41 minor 0 serial 23616 xwm: error 3: BadWindow (invalid Window parameter) request 12 minor 0 serial 23617 xwm: error 3: BadWindow (invalid Window parameter) request 12 minor 0 serial 23618 xwm: error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 23619 gamemodeauto: gamescope: children shut down! (EE) failed to read Wayland events: Broken pipe Monitored process exited. Initial process has exited (return code: 0) All processes have quit Exit with return code 0 ```
jajedi hozzászólt 6 hónapja

Alright, I found the problem. Looks like the version 3.12.7 has a lot of issues and downgrading it to previous version fixed it.

https://github.com/ValveSoftware/gamescope/issues/984

Alright, I found the problem. Looks like the version 3.12.7 has a lot of issues and downgrading it to previous version fixed it. [https://github.com/ValveSoftware/gamescope/issues/984](https://github.com/ValveSoftware/gamescope/issues/984)
Krock lezárta ekkor: 5 hónapja
Jelentkezzen be hogy csatlakozhasson a beszélgetéshez.
Nincs mérföldkő
Nincs megbízott
2 Résztvevő
Töltés...
Mégse
Mentés
Még nincs tartalom.