DayZ
Update: There are still underlying issues with XAudio and ALSA given failure to initialize a sound device should not cause a crash. With that addressed, the unimplemented function error remains and is bizzar. I have no idea why this is not being detected? Dotnet 4 is installed
fwiw to address the audio crash you can set a couple variables before launching proton/wine. I used dummy for testing but SDL supports others (ie alsa). Strangely enough these vars are not passed from steam.
# FAUDIO_LOG_API_CALLS=1 SDL_DRIVER=alsa \
{ PROTON_LOG=1 \
FAUDIO_LOG_ALL=1 \
FAUDIO_LOG_API_CALLS=1 \
SDL_DRIVER=dummy \
SDL_AUDIO_CHANNELS=2 \
AUDIODEV=sysdefault:CARD=Generic \
./run cmd.exe 2> out.$$.lg ; }
this game not work on wine/proton
https://www.protondb.com/app/221100
Indeed, wasn't expecting battleeye to work but at least single player. Shame they wasted a good time to add more users with the free weekend.
With wine-mono upgraded so WPF can at least load, the launcher fails because it can't find steam_api.dll, which is in the game's files. This can be worked around by copying steam_api.dll from DayZ/Launcher to DayZ, but then it fails because wine-mono's WPF doesn't have text layout working.
After trying it with the new BattlEye, it's not working here for me
So it's the launcher being the first problem. Using the second launch option, I still get a black screen:
Similar behaviour here, launcher doesn't launch with the exception above.
Second launch option launches the game and the loading screen appears but it gets stuck during loading.
I was able to get it working by running this command:
sudo sysctl -w vm.max_map_count=1048576
To make it permanent:
echo 'vm.max_map_count=1048576' | sudo tee /etc/sysctl.d/vm.max_map_count.conf
Game now loads and plays fine when started with the second launch option.
I do have that set but it didn't stop the black screens for me.
With proton 5.13 game successfully hits main menu, but can't connect to the servers, but with Experimental version only a black screen appears
I have a similar problem... I have everything on Experimental - I have the new Proton Battleye Runtime downloaded. But when I launch the game it doesn't stop loading - after a while it just crashes.
@DomiStyle Thank you very much. It worked for me!
I have no launcher running, the game starts, and everything works fine. I use Arch, with the last mesa. And without the command proposed above, the game was thrown out after about half an hour. After entering, you can play without problems. But there are a couple of problems, RAM is clogged. Maybe a swap file would help, but I don't use it. And another problem, due to the inability to launch the launcher, you can only play on vanilla servers. We haven't found a way to launch with mods yet. I tried on all the latest protons, everything is great, experimental, 6.3.8 and 6.22. There was an option to run through cmd, prescribing mods and so on, but nothing has turned out yet. Most likely I'm doing something wrong
Game starts, but i have black screen that's all. Tried all protons that i currently have. 6.3.8, Experimental, GE-6.21.
Logs here
https://pastebin.com/u4UPzFae
https://pastebin.com/iC066N1k
I've had some black screens seemingly at random as well. It's always started working again, but with no apparent reason. Once when I managed to make it run again I coincidentally restarted Firefox before it started working again (after about 5 unsuccessful attempts). This would seem like I was out of memory, but I had over 50 GB free and my vm.max_map_count was set to 1Gi (1073741824). I'll post logs if it happens again.
I'm getting some black screens as well. No FF running, but had chromium. Twice was able to close chromium and attempt restart and it worked. Have not been able to repeat since. I do not believe there is a direct correlation.
Here is terminal output of steam when the app fails to render past black screen. I will see if I can capture the successful output in a few minutes.
: LaunchApp changed task to ShowLaunchOption with ""
GameAction [AppID 221100, ActionID 9] : LaunchApp waiting for user response to ShowLaunchOption ""
GameAction [AppID 221100, ActionID 9] : LaunchApp continues with user response "1"
GameAction [AppID 221100, ActionID 9] : LaunchApp changed task to ProcessingInstallScript with ""
esync: up and running.
wine: RLIMIT_NICE is <= 20, unable to use setpriority safely
GameAction [AppID 221100, ActionID 9] : LaunchApp changed task to SynchronizingCloud with ""
GameAction [AppID 221100, ActionID 9] : LaunchApp changed task to SynchronizingControllerConfig with ""
GameAction [AppID 221100, ActionID 9] : LaunchApp changed task to SiteLicenseSeatCheckout with ""
GameAction [AppID 221100, ActionID 9] : LaunchApp changed task to CreatingProcess with ""
GameAction [AppID 221100, ActionID 9] : LaunchApp waiting for user response to CreatingProcess ""
GameAction [AppID 221100, ActionID 9] : LaunchApp continues with user response "CreatingProcess"
/bin/sh\0-c\0/home/techy/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=221100 -- '/home/techy/.local/share/Steam/steamapps/common/SteamLinuxRuntime_soldier'/_v2-entry-point --verb=waitforexitandrun -- '/home/techy/.local/share/Steam/steamapps/common/Proton - Experimental'/proton waitforexitandrun '/mnt/steam/SteamLib/steamapps/common/DayZ/DayZ_BE.exe' -exe DayZ_x64.exe\0
Game process added : AppID 221100 "/home/techy/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=221100 -- '/home/techy/.local/share/Steam/steamapps/common/SteamLinuxRuntime_soldier'/_v2-entry-point --verb=waitforexitandrun -- '/home/techy/.local/share/Steam/steamapps/common/Proton - Experimental'/proton waitforexitandrun '/mnt/steam/SteamLib/steamapps/common/DayZ/DayZ_BE.exe' -exe DayZ_x64.exe", ProcID 914114, IP 0.0.0.0:0
chdir /mnt/steam/SteamLib/steamapps/common/DayZ
ERROR: ld.so: object '/home/techy/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/techy/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/techy/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/techy/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/techy/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
pid 914118 != 914115, skipping destruction (fork without exec?)
GameAction [AppID 221100, ActionID 9] : LaunchApp changed task to WaitingGameWindow with ""
GameAction [AppID 221100, ActionID 9] : LaunchApp changed task to Completed with ""
esync: up and running.
wine: RLIMIT_NICE is <= 20, unable to use setpriority safely
Game process updated : AppID 221100 "/home/techy/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=221100 -- '/home/techy/.local/share/Steam/steamapps/common/SteamLinuxRuntime_soldier'/_v2-entry-point --verb=waitforexitandrun -- '/home/techy/.local/share/Steam/steamapps/common/Proton - Experimental'/proton waitforexitandrun '/mnt/steam/SteamLib/steamapps/common/DayZ/DayZ_BE.exe' -exe DayZ_x64.exe", ProcID 914269, IP 0.0.0.0:0
Setting breakpad minidump AppID = 221100
Steam_SetMinidumpSteamID: Caching Steam ID: 76561197989345857 [API loaded no]
Game process updated : AppID 221100 "/home/techy/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=221100 -- '/home/techy/.local/share/Steam/steamapps/common/SteamLinuxRuntime_soldier'/_v2-entry-point --verb=waitforexitandrun -- '/home/techy/.local/share/Steam/steamapps/common/Proton - Experimental'/proton waitforexitandrun '/mnt/steam/SteamLib/steamapps/common/DayZ/DayZ_BE.exe' -exe DayZ_x64.exe", ProcID 914337, IP 0.0.0.0:0
Setting breakpad minidump AppID = 221100
Steam_SetMinidumpSteamID: Caching Steam ID: 76561197989345857 [API loaded no]
Fossilize INFO: Overriding serialization path: "/mnt/steam/SteamLib/steamapps/shadercache/221100/fozpipelinesv6/steamapprun_pipeline_cache".
corrupted size vs. prev_size
pid 914271 != 914270, skipping destruction (fork without exec?)
Game process removed: AppID 221100 "/home/techy/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=221100 -- '/home/techy/.local/share/Steam/steamapps/common/SteamLinuxRuntime_soldier'/_v2-entry-point --verb=waitforexitandrun -- '/home/techy/.local/share/Steam/steamapps/common/Proton - Experimental'/proton waitforexitandrun '/mnt/steam/SteamLib/steamapps/common/DayZ/DayZ_BE.exe' -exe DayZ_x64.exe", ProcID 914337
Game 221100 created interface STEAMAPPLIST_INTERFACE_VERSION001 / AppList
Game 221100 created interface STEAMAPPS_INTERFACE_VERSION008 / Apps
Game 221100 created interface STEAMHTMLSURFACE_INTERFACE_VERSION_004 / HTMLSurface
Game 221100 created interface STEAMHTTP_INTERFACE_VERSION002 / HTTP
Game 221100 created interface STEAMINVENTORY_INTERFACE_V002 / Inventory
Game 221100 created interface STEAMMUSICREMOTE_INTERFACE_VERSION001 / MusicRemote
Game 221100 created interface STEAMMUSIC_INTERFACE_VERSION001 / Music
Game 221100 created interface STEAMPARENTALSETTINGS_INTERFACE_VERSION001 / ParentalSettings
Game 221100 created interface STEAMREMOTESTORAGE_INTERFACE_VERSION014 / RemoteStorage
Game 221100 created interface STEAMSCREENSHOTS_INTERFACE_VERSION003 / Screenshots
Game 221100 created interface STEAMUGC_INTERFACE_VERSION010 / UGC
Game 221100 created interface STEAMUNIFIEDMESSAGES_INTERFACE_VERSION001 / UnifiedMessages
Game 221100 created interface STEAMUSERSTATS_INTERFACE_VERSION011 / UserStats
Game 221100 created interface STEAMVIDEO_INTERFACE_V002 / Video
Game 221100 created interface SteamController005 / Controller
Game 221100 created interface SteamFriends015 / Friends
Game 221100 created interface SteamMatchMaking009 / Matchmaking
Game 221100 created interface SteamMatchMakingServers002 / MatchmakingServers
Game 221100 created interface SteamNetworking005 / Networking
Game 221100 created interface SteamUser019 / User
Game 221100 created interface SteamUtils009 / Utils
Game 221100 method call count for IClientAppManager::BIsDlcEnabled : 2
Game 221100 method call count for IClientAppManager::IsAppDlcInstalled : 3
Game 221100 method call count for IClientApps::BGetDLCDataByIndex : 2
Game 221100 method call count for IClientApps::GetDLCCount : 1
Game 221100 method call count for IClientUtils::RecordSteamInterfaceCreation : 23
Game 221100 method call count for IClientUtils::GetAppID : 24
Game 221100 method call count for IClientUser::BIsSubscribedApp : 3
Game 221100 method call count for IClientUser::GetSteamID : 3
Game 221100 method call count for IClientUser::BLoggedOn : 1
Uploaded AppInterfaceStats to Steam
No cached sticky mapping in ActivateActionSet.
Game starts, but i have black screen that's all. Tried all protons that i currently have. 6.3.8, Experimental, GE-6.21. Logs here https://pastebin.com/u4UPzFae https://pastebin.com/iC066N1k
FIXED. Disabled Steam shader precaching and dayz starts normally
I've attempted disabling precache and deleting my precache folder for dayz and I am still getting the same black screen. I have looked through proton logs for 6.3-8 and Experimental (6.3-20) and have found one major difference in the file that relates to video, neither loads but I am hoping the additional information from experimental might shed some light on whats going on.
See Partial Log
1221254.231:00fc:0100:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\XAudio2_7.dll" at 00007F9F24560000: builtin
info: Game: DayZ_x64.exe
info: DXVK: v1.9.2
info: Built-in extension providers:
info: Win32 WSI
info: OpenVR
info: OpenXR
1221254.295:00fc:0100:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\wineopenxr.dll" at 00007F9F24060000: builtin
warn: OpenXR: Unable to get required Vulkan instance extensions size
info: Enabled instance extensions:
info: VK_KHR_get_surface_capabilities2
info: VK_KHR_surface
info: VK_KHR_win32_surface
warn: OpenXR: Unable to get required Vulkan Device extensions size
1221255.339:00fc:0100:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\wineopenxr.dll" : builtin
info: NVIDIA GeForce RTX 2080 Ti:
info: Driver: 495.44.0
info: Vulkan: 1.2.186
info: Memory Heap[0]:
info: Size: 11264 MiB
info: Flags: 0x1
info: Memory Type[7]: Property Flags = 0x1
info: Memory Heap[1]:
info: Size: 48183 MiB
info: Flags: 0x0
info: Memory Type[0]: Property Flags = 0x0
info: Memory Type[1]: Property Flags = 0x0
info: Memory Type[2]: Property Flags = 0x0
info: Memory Type[3]: Property Flags = 0x0
info: Memory Type[4]: Property Flags = 0x0
info: Memory Type[5]: Property Flags = 0x0
info: Memory Type[6]: Property Flags = 0x0
info: Memory Type[8]: Property Flags = 0x6
info: Memory Type[9]: Property Flags = 0xe
info: Memory Heap[2]:
info: Size: 246 MiB
info: Flags: 0x1
info: Memory Type[10]: Property Flags = 0x7
info: DXGI: NvAPI workaround enabled, reporting AMD GPU
info: D3D11CoreCreateDevice: Probing D3D_FEATURE_LEVEL_11_1
info: D3D11CoreCreateDevice: Using feature level D3D_FEATURE_LEVEL_11_1
info: Device properties:
info: Device name: : NVIDIA GeForce RTX 2080 Ti
info: Driver version : 495.44.0
info: Enabled device extensions:
info: VK_EXT_4444_formats
info: VK_EXT_conservative_rasterization
info: VK_EXT_custom_border_color
info: VK_EXT_depth_clip_enable
info: VK_EXT_extended_dynamic_state
info: VK_EXT_host_query_reset
info: VK_EXT_robustness2
info: VK_EXT_shader_demote_to_helper_invocation
info: VK_EXT_shader_viewport_index_layer
info: VK_EXT_transform_feedback
info: VK_EXT_vertex_attribute_divisor
info: VK_KHR_buffer_device_address
info: VK_KHR_create_renderpass2
info: VK_KHR_depth_stencil_resolve
info: VK_KHR_draw_indirect_count
info: VK_KHR_driver_properties
info: VK_KHR_image_format_list
info: VK_KHR_sampler_mirror_clamp_to_edge
info: VK_KHR_shader_float_controls
info: VK_KHR_swapchain
info: VK_NVX_binary_import
info: VK_NVX_image_view_handle
info: Device features:
info: robustBufferAccess : 1
info: fullDrawIndexUint32 : 1
info: imageCubeArray : 1
info: independentBlend : 1
info: geometryShader : 1
info: tessellationShader : 1
info: sampleRateShading : 1
info: dualSrcBlend : 1
info: logicOp : 1
info: multiDrawIndirect : 1
info: drawIndirectFirstInstance : 1
info: depthClamp : 1
info: depthBiasClamp : 1
info: fillModeNonSolid : 1
info: depthBounds : 1
info: multiViewport : 1
info: samplerAnisotropy : 1
info: textureCompressionBC : 1
info: occlusionQueryPrecise : 1
info: pipelineStatisticsQuery : 1
info: vertexPipelineStoresAndAtomics : 1
info: fragmentStoresAndAtomics : 1
info: shaderImageGatherExtended : 1
info: shaderStorageImageExtendedFormats : 0
info: shaderStorageImageReadWithoutFormat : 1
info: shaderStorageImageWriteWithoutFormat : 1
info: shaderClipDistance : 1
info: shaderCullDistance : 1
info: shaderFloat64 : 1
info: shaderInt64 : 1
info: variableMultisampleRate : 1
info: VK_EXT_4444_formats
info: formatA4R4G4B4 : 1
info: formatA4B4G4R4 : 1
info: VK_EXT_custom_border_color
info: customBorderColors : 1
info: customBorderColorWithoutFormat : 1
info: VK_EXT_depth_clip_enable
info: depthClipEnable : 1
info: VK_EXT_extended_dynamic_state
info: extendedDynamicState : 1
info: VK_EXT_host_query_reset
info: hostQueryReset : 1
info: VK_EXT_memory_priority
info: memoryPriority : 0
info: VK_EXT_robustness2
info: robustBufferAccess2 : 1
info: robustImageAccess2 : 1
info: nullDescriptor : 1
info: VK_EXT_shader_demote_to_helper_invocation
info: shaderDemoteToHelperInvocation : 1
info: VK_EXT_transform_feedback
info: transformFeedback : 1
info: geometryStreams : 1
info: VK_EXT_vertex_attribute_divisor
info: vertexAttributeInstanceRateDivisor : 1
info: vertexAttributeInstanceRateZeroDivisor : 1
info: VK_KHR_buffer_device_address
info: bufferDeviceAddress : 1
info: Queue families:
info: Graphics : 0
info: Transfer : 1
err: DxvkAdapter: Failed to create device, retrying without CUDA interop extensions
warn: DXVK: No state cache file found
warn: DXVK: Creating new state cache file
info: DXVK: Using 7 compiler threads
1221255.445:00fc:0100:trace:seh:NtSetInformationThread (0x3a4,3,0xd3e2ec,4)
1221255.445:00fc:0100:trace:seh:NtSetInformationThread (0x3a8,3,0xd3e2ec,4)
1221255.445:00fc:0100:trace:seh:NtSetInformationThread (0x3ac,3,0xd3e2ec,4)
1221255.445:00fc:0138:trace:seh:NtSetInformationThread (0xfffffffffffffffe,38,0x24174fcd0,10)
1221255.445:00fc:0100:trace:seh:NtSetInformationThread (0x3b0,3,0xd3e2ec,4)
1221255.445:00fc:013c:trace:seh:NtSetInformationThread (0xfffffffffffffffe,38,0x2495bfcd0,10)
1221255.445:00fc:0100:trace:seh:NtSetInformationThread (0x3b4,3,0xd3e2ec,4)
1221255.445:00fc:0140:trace:seh:NtSetInformationThread (0xfffffffffffffffe,38,0x249acfcd0,10)
1221255.446:00fc:0100:trace:seh:NtSetInformationThread (0x3b8,3,0xd3e2ec,4)
1221255.446:00fc:0100:trace:seh:NtSetInformationThread (0x3bc,3,0xd3e2ec,4)
1221255.446:00fc:0144:trace:seh:NtSetInformationThread (0xfffffffffffffffe,38,0x249fdfcd0,10)
1221255.446:00fc:0148:trace:seh:NtSetInformationThread (0xfffffffffffffffe,38,0x24a4efcd0,10)
1221255.446:00fc:014c:trace:seh:NtSetInformationThread (0xfffffffffffffffe,38,0x24a9ffcd0,10)
1221255.446:00fc:0150:trace:seh:NtSetInformationThread (0xfffffffffffffffe,38,0x24af0fcd0,10)
1221255.446:00fc:0154:trace:seh:NtSetInformationThread (0xfffffffffffffffe,38,0x24b41f5f0,10)
1221255.450:00fc:0158:trace:seh:NtSetInformationThread (0xfffffffffffffffe,38,0x24b92fab0,10)
1221255.450:00fc:015c:trace:seh:NtSetInformationThread (0xfffffffffffffffe,38,0x24be3fab0,10)
1221255.478:00fc:0160:trace:seh:NtSetInformationThread (0xfffffffffffffffe,38,0x24c34fcd0,10)
1221255.478:00fc:0160:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0x24c34fe2c,4,(nil))
1221255.479:00fc:0154:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0x24b41fe2c,4,(nil))
1221255.479:00fc:0150:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0x24af0fe2c,4,(nil))
1221255.479:00fc:0138:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0x24174fe2c,4,(nil))
1221255.480:00fc:0140:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0x249acfe2c,4,(nil))
1221255.480:00fc:0144:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0x249fdfe2c,4,(nil))
1221255.480:00fc:0148:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0x24a4efe2c,4,(nil))
1221255.480:00fc:013c:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0x2495bfe2c,4,(nil))
1221255.480:00fc:014c:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0x24a9ffe2c,4,(nil))
1221255.480:00fc:0158:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0x24b92fe2c,4,(nil))
1221255.480:00fc:015c:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0x24be3fe2c,4,(nil))
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
warn: GetMonitorFormatBpp: Unknown format: 11
info: DXGI: NvAPI workaround enabled, reporting AMD GPU
info: D3D11CoreCreateDevice: Probing D3D_FEATURE_LEVEL_11_0
info: D3D11CoreCreateDevice: Using feature level D3D_FEATURE_LEVEL_11_0
info: Device properties:
info: Device name: : NVIDIA GeForce RTX 2080 Ti
info: Driver version : 495.44.0
info: Enabled device extensions:
info: VK_EXT_4444_formats
info: VK_EXT_conservative_rasterization
info: VK_EXT_custom_border_color
info: VK_EXT_depth_clip_enable
info: VK_EXT_extended_dynamic_state
info: VK_EXT_host_query_reset
info: VK_EXT_robustness2
info: VK_EXT_shader_demote_to_helper_invocation
info: VK_EXT_shader_viewport_index_layer
info: VK_EXT_transform_feedback
info: VK_EXT_vertex_attribute_divisor
info: VK_KHR_buffer_device_address
info: VK_KHR_create_renderpass2
info: VK_KHR_depth_stencil_resolve
info: VK_KHR_draw_indirect_count
info: VK_KHR_driver_properties
info: VK_KHR_image_format_list
info: VK_KHR_sampler_mirror_clamp_to_edge
info: VK_KHR_shader_float_controls
info: VK_KHR_swapchain
info: VK_NVX_binary_import
info: VK_NVX_image_view_handle
info: Device features:
info: robustBufferAccess : 1
info: fullDrawIndexUint32 : 1
info: imageCubeArray : 1
info: independentBlend : 1
info: geometryShader : 1
info: tessellationShader : 1
info: sampleRateShading : 1
info: dualSrcBlend : 1
info: logicOp : 1
info: multiDrawIndirect : 1
info: drawIndirectFirstInstance : 1
info: depthClamp : 1
info: depthBiasClamp : 1
info: fillModeNonSolid : 1
info: depthBounds : 1
info: multiViewport : 1
info: samplerAnisotropy : 1
info: textureCompressionBC : 1
info: occlusionQueryPrecise : 1
info: pipelineStatisticsQuery : 1
info: vertexPipelineStoresAndAtomics : 0
info: fragmentStoresAndAtomics : 1
info: shaderImageGatherExtended : 1
info: shaderStorageImageExtendedFormats : 0
info: shaderStorageImageReadWithoutFormat : 1
info: shaderStorageImageWriteWithoutFormat : 1
info: shaderClipDistance : 1
info: shaderCullDistance : 1
info: shaderFloat64 : 1
info: shaderInt64 : 1
info: variableMultisampleRate : 1
info: VK_EXT_4444_formats
info: formatA4R4G4B4 : 1
info: formatA4B4G4R4 : 1
info: VK_EXT_custom_border_color
info: customBorderColors : 1
info: customBorderColorWithoutFormat : 1
info: VK_EXT_depth_clip_enable
info: depthClipEnable : 1
info: VK_EXT_extended_dynamic_state
info: extendedDynamicState : 1
info: VK_EXT_host_query_reset
info: hostQueryReset : 1
info: VK_EXT_memory_priority
info: memoryPriority : 0
info: VK_EXT_robustness2
info: robustBufferAccess2 : 1
info: robustImageAccess2 : 1
info: nullDescriptor : 1
info: VK_EXT_shader_demote_to_helper_invocation
info: shaderDemoteToHelperInvocation : 1
info: VK_EXT_transform_feedback
info: transformFeedback : 1
info: geometryStreams : 1
info: VK_EXT_vertex_attribute_divisor
info: vertexAttributeInstanceRateDivisor : 1
info: vertexAttributeInstanceRateZeroDivisor : 1
info: VK_KHR_buffer_device_address
info: bufferDeviceAddress : 1
info: Queue families:
info: Graphics : 0
info: Transfer : 1
Black Screen
Proton: 1639575425 experimental-6.3-20211215
https://pastebin.com/NE0E503b
Black Screen
Proton: 1638789187 proton-6.3-8c
https://pastebin.com/9JQ7a4u4
One thing I've noticed so far is all of the graphics cards in the logs I've read here are Nvidia 2080 series, do we have a driver issue here?
Maybe Liam would have better luck but I think it's worth testing again in general given the time this has been open. In my case it was 1080TIs which I don't have access to atm. Can't even login to steam because of their stupid 2fa garbage (hey Valve, people travel, shocking I know).
Edit: No idea what I was thinking, that bug involved optimus.
@h1z1 nope, still a black screen here no matter what launch options people suggest.
Same black screens here. 1/30 start somehow succeeds, then it works like a charm.
3070 with 495.46.0 driver, shader pre-caching is disabled.
Launch options are: -nosplash -skipintro -nolauncher
Proton 6.3-8 dies instantly with the following log: https://pastebin.com/W2wzGnAr
Proton experimental gets to the black screen: https://pastebin.com/UMJZhjez
System info: https://pastebin.com/1X2p5ikk
same issue as xcenter, it works really rarely like 1/20 attempts to start the game.
system info:
OS: Arch Linux
KERNEL: 5.16.0-arch1-1
CPU: Intel Core i7-9750H @ 2.60GHz
GPU: NVIDIA GeForce RTX 2070 with Max-Q Design
GPU DRIVER: NVIDIA 495.46
RAM: 16 GB
full proton logfile: https://pastebin.com/ujtpMfSw
Hi
I have written a script for linux to see if anything useful can be gotten, ( script below )
The results show me that ( this is doing things when the game starts )
futex(0x7ff6c47590a8, FUTEX_WAKE, 2147483647) = 1
futex(0x7ff6c47590a8, FUTEX_WAKE, 2147483647) = 1
futex(0x7ff6c47590a8, FUTEX_WAKE, 2147483647) = 1
AND
This is stuck here when the game starts and the screen go's blank.
futex(0x7f793aa28990, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0x7f793aa28990, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x7f793a911b80, FUTEX_WAIT_PRIVATE, 2, NULL) = ?
I hope this helps the minds that know a lot more than me.
Regards
me:~$ cat test_if_DayZ_is_not_starting_up.bash
#===============================================
while true
do
Day_Val=`date | awk '{print $2}'`
Time_Val=`date | awk '{print $5}'`
S_VALE=0
S_VALE=`ps -U me | grep -i enfMain | grep -v grep | awk '{print $1}'`
if [[ ${S_VALE} -ge 1 ]]
then
echo "strace -p ${S_VALE}"
sudo strace -p ${S_VALE} 2>${Day_Val}_${Time_Val}
fi
sleep 3
echo "cycle"
done
#================================================
Computer:
CPU = AMD 2700x
GPU = Nvidia 3070
RAM: = 32 GB
Proton experimental
Worth noting to anyone adding pastebin links, they expire (as did those above). Probably better to use a gist or attach it here.
With any luck I should be able to recover my steam account in the next few days to test dayz again (exs are evil irl as in dayz!).
What is a pastebin ? is that where I have pasted text and highlighted it with italic ?
@gmcd2200 It's a third party site to Github where some of the logs above are posted.
Not that Github's gist's are perfect but you can at least edit them if needed.
I have an nvidia optimus laptop and using steam flatpak. I was able to get the game to load a few random times after installation, but then never again no matter what different versions of proton I tried.
However, I found that setting the proton env variable PROTON_USE_WINED3D=1 at least got the game running every time, otherwise it was the same blank screen. Haven't tried a modded server yet either.
- Fedora 35 Silverblue
- Steam - flatpak
- Proton - Experimental
PROTON_USE_WINED3D=1
- nvidia quadro T2000 - proprietary drivers 510.47.03
- launch options =
-nosplash -skipintro -nolauncher
still experimenting with different settings and checking logs, will report any other info I find
I've done quite a lot of testing on the black screen issue for the last two months.
- Launch options: PROTON_LOG=1 WINE_FULLSCREEN_FSR=1 WINE_FULLSCREEN_FSR_STRENGTH=2 gamemoderun %command% -nosplash -skipintro
- Ubuntu 20.04
- nVidia RTX 2060 Super Ghost and Intel UHD graphics with I7-10510U.
- Asus XG Station Pro Thunderbolt 3 eGPU.
- Nvidia driver version: 510.54
- Proton version: 7.0-1
The game can work fine for weeks or days. Suddenly I'm unable to start the game. My only choice then is to boot up Windows :-(. I've tried several nVidia driver versions and a lot of different launch options. The thing that is interesting here is that I sometimes get the black screen issue in Windows too.
I was able to solve the issue for the first time yesterday. After trying to start the game for about 15-20 times, validating the game files and rebooting a couple of times in the process, I tried adding PROTON_USE_WINED3D=1. The game started, but with bad performance and glitches in the graphics. I set the graphics options that I wanted, shut down the game, removed PROTON_USE_WINED3D=1 and was able to start the game successfully.
I suspect that the problem is related to something with the graphics settings in the game.
If you got this problem, try the same. Try to validate the game files and reset the settings for DayZ in the process, before adding PROTON_USE_WINED3D=1.
Please tell if this helps you solve your issue too.
Hmm...
/tmp/proton_steam/run
wine: could not load ntdll.so: /home/steam/.local/share/Steam/steamapps/common/Proton 7.0/dist/lib//wine/ntdll.so: cannot open shared object file: No such file or directory
$ find /home/steam/.local/share/Steam/steamapps/common/Proton\ 7.0/ -name ntdll.so
/home/steam/.local/share/Steam/steamapps/common/Proton 7.0/dist/lib/wine/i386-unix/ntdll.so
/home/steam/.local/share/Steam/steamapps/common/Proton 7.0/dist/lib64/wine/x86_64-unix/ntdll.so
Updated path
$ /tmp/proton_steam/run
wine: could not load ntdll.so: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /home/steam/.local/share/Steam/steamapps/common/Proton 7.0/dist/lib64/wine/x86_64-unix/ntdll.so)
Proton 7
objdump -x "/home/steam/.local/share/Steam/steamapps/common/Proton 7.0/dist/lib64/wine/x86_64-unix/ntdll.so" | grep GLIBC_2.25
0x06969185 0x00 15 GLIBC_2.25
0000000000000000 F *UND* 0000000000000000 getrandom@GLIBC_2.25
awk -v FS=\@ '{print $2}' | sort | uniq -c
1892
1 GCC_3.0
1 GLIBC_2.14
1 GLIBC_2.15
1 GLIBC_2.16
1 GLIBC_2.25
174 GLIBC_2.2.5
4 GLIBC_2.3
2 GLIBC_2.3.2
1 GLIBC_2.3.3
2 GLIBC_2.4
1 GLIBC_2.6
1 GLIBC_2.9
<insert clown music>yeah i also am having problems running dayz on steam with proton. I get a popup when using the launcher:
unexpected error occured:
the method of operation is not implemented.
details are stored in a text file on your desktop.
and when i use the client i get a black screen for a second and it dies!
anyways i am running slackware 15 64 bit multilib on an intel system
Manufacturer: ASUSTeK COMPUTER INC. Model: ROG STRIX Z390-E GAMING
CPU Brand: Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz
uname -r = 5.17.3 (so sue me i thought it might help)
16 gig of ram
steam beta with ge-proton7-14 (steam proton experimental does pretty much the same)
also here is the log with it if that can help
steam-221100.log
yes pretty much what everyone else is saying that mostly it will not work and sometimes randomly it will connect
and will work well enough. It seems to run ok with good frame rate but has a lot of problems launching.
even third party launchers like the arma-unix-launcher do not seem to have more any luck either.
Every time I read a log from proton I swear I learn something new... these are quite odd
465.170:0128:014c:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\crypt32.dll" at 6E8C0000: builtin
[0000014c:] EXCEPTION handling: System.Security.Cryptography.CryptographicException: `MonoBtlsPkcs12.Import` failed.
[0000014c:] EXCEPTION handling: System.Security.Cryptography.CryptographicException: `MonoBtlsPkcs12.Import` failed.
[0000014c:] EXCEPTION handling: System.Security.Cryptography.CryptographicException: Missing private key
[0000014c:] EXCEPTION handling: System.Security.Cryptography.CryptographicException: `MonoBtlsPkcs12.Import` failed.
fwiw I believe in your case those are bubbled up errors from mono
[0000012c:] EXCEPTION handling: System.IO.FileNotFoundException: Could not load file or assembly 'Z:\home\dave\.local\share\Steam\compatibilitytools.d\GE-Proton7-14\files\share\wine\mono\wine-mono-7.1.5\lib\mono\gac\PresentationCore\4.0.0.0__31bf3856ad364e35\en-US\PresentationCore.resources.dll' or one of its dependencies.
``Game starts, but i have black screen that's all. Tried all protons that i currently have. 6.3.8, Experimental, GE-6.21. Logs here https://pastebin.com/u4UPzFae https://pastebin.com/iC066N1k
FIXED. Disabled Steam shader precaching and dayz starts normally
No longer works. Black screens all the time. Same pc specs
Steam don't launch the game
Issue transferred from https://github.com/ValveSoftware/steam-for-linux/issues/8557.
@Trasher195 posted on 2022-04-29T14:36:13:
Distribution: ArchLinux
Opted into Steam client beta?: No
Have you checked for system updates?: Yes
When you press the play button, Steam is endlessly preparing to launch. Checking the integrity of files for this particular game does not work. Reinstalling doesn't help.
Here is what is written in the logs:
stats_log.txt
[2022-04-29 18:16:25] [AppID 228980] Schema not found on disk
[2022-04-29 18:16:25] [AppID 228980] CAPIJobRequestUserStats - received error 'Failure' (2) from server
[2022-04-29 18:16:25] [AppID 221100] Schema not found on disk
[2022-04-29 18:16:25] [AppID 221100] CAPIJobRequestUserStats - received error 'Failure' (2) from server
[2022-04-29 18:16:31] [AppID 221100] Schema not found on disk
installscript_log.txt
[2022-04-29 17:08:46] [AppID 221100] Failed to load installscript "/home/artem/.local/share/Steam/steamapps/common/DayZ/installscript.vdf"
black screen with https://github.com/muttleyxd/arma3-unix-launcher as well. Cannot seem to get past the black screen issues stated above.
rm -rf ~/.steam/debian-installation/steamapps/shadercache
got me past the black screen with Proton Experimental, happy dayz! :)
Going to give this a try again tonight. Which version of experimental?
"Proton Experimental" at the top of the list - I'm on Ubuntu 20.04
@kisak-valve updated log in the last issue. Apologies on wrong log file previously. Will add to this issue as previously described in #5914 w/Log attached
steam-221100.log
rm -rf ~/.steam/debian-installation/steamapps/shadercache
got me past the black screen with Proton Experimental, happy dayz! :)
This worked for me at some point, but eventually it stopped working and black screen issues got worse and worse. In the end I gave up as it could take an hour just to start the game. Looks like things are the same now, regardless of wiping shader cache, disabling pre-caching, etc.
I'm starting to believe everything that has worked only worked by chance, since the issues start showing up again sooner or later regardless.
Interestingly wiping the game and/or the compatdata makes no difference either, so I have no idea how it could get worse over time.
Hi! I've also had these intermittent issues after my previous post, but have figured out a way to get this loading up to the client screen;
- I use Proton 7.0-3
- I add the commandline options; "PROTON_USE_WINED3D=1 %command% -nosplash -skipintro"
- The client will now load, but graphics are offloaded to Wine (I think) and can see rendering issues in the client
- I connect to a server (broken graphics)
- I disconnect and close the game
- I change my commandline options back to " %command% -nosplash -skipintro"
- I can now open the client and connect to a server, everything works normally
I think I just found the solution here.
Try GE-Proton 7.29 and set the command line options to the following (and nothing else): %command% -nosplash -skipintro
I'm testing this now.. So far the game has started at every launch without failing even once.
The game launched 1 out of 20 times before trying this.
Ok, followed my own steps this morning, and they failed.
I spun the game up using "PROTON_USE_WINED3D=1 %command% -nosplash -skipintro", then set the graphics to their defaults.
Closed the game, removed the PROTON_USE_WINED3D flag, launched the game, opened fine.
Ok, followed my own steps this morning, and they failed.
I spun the game up using "PROTON_USE_WINED3D=1 %command% -nosplash -skipintro", then set the graphics to their defaults.
Closed the game, removed the PROTON_USE_WINED3D flag, launched the game, opened fine.
Resetting the graphics usually works this way.
But sometimes this doesn't work for me. If this doesn't work, then nothing works except for what I wrote in my previous post.
I just discovered this, so haven't tested this over time.
OK - interesting, I installed GE-Proton 7.29 and the game loaded up first time after a known-working play on Proton 7.0-3.
I tried DayZ Experimental, and got the black screen.
Tried my steps above, but used GE-Proton 7.29, and it worked.
Switched back to regular DayZ and started it - black screen.
Interesting!
OK, so followed the steps back on regular DayZ, with GE 7.29 and couldn't get past the black screen.
Changed back to 7.0.3 and followed the steps (https://github.com/ValveSoftware/Proton/issues/3899#issuecomment-1212687881) and it opened up again.
Closed this, tried Dayz Exp and blank screen. Opened regular DayZ and blank screen.
Something's being set between switching here
OK, so followed the steps back on regular DayZ, with GE 7.29 and couldn't get past the black screen.
Changed back to 7.0.3 and followed the steps ([#3899 (comment)](https://github.com/ValveSoftware/Proton/issues/3899#issuecomment-1212687881)) and it opened up again.
Closed this, tried Dayz Exp and blank screen. Opened regular DayZ and blank screen.
Something's being set between switching here
When I "discovered the solution" above, I'd been trying for almost an hour to get the game working. I'd been switching between different versions of Proton myself.
I experienced the black screen with GE 7.29 after rebooting, but only on the first try. Dayz starts on the second try.
I think that there is more than one problem we are dealing with here. I've experienced booting into Windows struggling with fullscreen issues. It seems like the graphics settings needs to be reset now and then to get Dayz working.
I've just found an error message that I don't get when DayZ is working. Steam output from command line gives me the following:
corrupted size vs. prev_size
I am experiencing a weird memory allocation error on my main desktop when I launch Dayz, and I hope someone here can help me solve this issue.
When launching Dayz I get black screen on launch and these errors in the terminal:
"corrupted size vs. prev_size" & "malloc(): invalid next size" .
This only happens on my desktop with a RTX3060. Dayz will launch on 1 out of 20 try's, and when it runs, it runs fine.
I have two other computers with the same distro, with 1050 TI and 1060 cards where I can run Dayz without any issues at all.
steam-221100.log
I have tried:
- All available launch options in steam
- Changing vm max count to 1048576
- All proton versions with BE support (included Proton GE)
- Different Nvidia GPU drivers (With and without CUDA)
- Reinstall Linux
Specs:
Distro: Debian GNU/Linux 11 (bullseye)
Kernel: 5.10.0-16-amd64
RAM: 16 GB
GPU Driver: NVIDIA 515.65.01
GPU: NVIDIA GeForce RTX 3060
CPU: 11th Gen Intel Core i5-11400F @ 2.60GHz
@BlaqG it looks like it could be a case of https://github.com/doitsujin/dxvk/issues/2504
The dxvk devs aren't entirely sure what's causing it. But supsect a driver issue.
Edit: tho now that i reread what you've tried I'm not sure. Since you've tried different drivers and proton versions
Hello,
Yes, it sure seems like it. I can run the game when using steam command:
"Proton_use_wined3d", which indicates DXVK issues. I get the same error on
all GPU drivers from legacy to the newest one. I dont know if modifying
proton files will count as cheating in BE?
Kind regards
On Wed, Aug 31, 2022, 17:09 Blisto91 @.***> wrote:
@BlaqG https://github.com/BlaqG it looks like it could be a case of
doitsujin/dxvk#2504 https://github.com/doitsujin/dxvk/issues/2504The dxvk devs aren't entirely sure what's causing it. But supsect a driver
issue.—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/3899#issuecomment-1233065445,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AP3UHQIFM62A4OPTTNKFPELV35YQ5ANCNFSM4NHW6WVQ
.
You are receiving this because you were mentioned.Message ID:
@.***>
Replying to https://github.com/ValveSoftware/Proton/issues/3899#issuecomment-1232812836
I just found a workaround for black screen with error: "corrupted size vs. prev_size"!
When this occurs, open terminal and type in free -h. Then look at buff/cache (Most likely very high)
Then type in:
sudo su
sync; echo 3 > /proc/sys/vm/drop_caches
(This command will clear pagecache, dentries, and inodes)
After this I can run the game 9/10 times without the black screen (corrupted size vs. prev_size). When the buff/cache gets too high I just run the command again.
Hope it works for other people as well.
@Blisto91 and @BlaqG, I confirmed the black screen issue is related to https://github.com/doitsujin/dxvk/issues/2504 by compiling the latest release of DXVK with the following patch, as suggested in the other thread. After replacing the DLLs with the patched ones, the game launches and works fine.
diff --git a/src/dxvk/dxvk_adapter.cpp b/src/dxvk/dxvk_adapter.cpp
index 24c7cea7..c099d719 100644
--- a/src/dxvk/dxvk_adapter.cpp
+++ b/src/dxvk/dxvk_adapter.cpp
@@ -311,7 +311,7 @@ namespace dxvk {
m_deviceFeatures.khrBufferDeviceAddress.bufferDeviceAddress;
if (enableCudaInterop) {
- devExtensions.nvxBinaryImport.setMode(DxvkExtMode::Optional);
+ // devExtensions.nvxBinaryImport.setMode(DxvkExtMode::Optional);
devExtensions.nvxImageViewHandle.setMode(DxvkExtMode::Optional);
devExtensions.khrBufferDeviceAddress.setMode(DxvkExtMode::Optional);
Specs:
Distro: Fedora 36
Steam: Flatpak
Proton: Proton-GE 7.31-1
Kernel: 5.19.6-200.fc36.x86_64
GPU: NVIDIA RTX 2070
Driver: 515.65.01
Awesome! That's interesting. Do you want to share the file you compiled?
Kind regards
On Sat, Sep 3, 2022, 01:43 Alice P. Hacker @.***> wrote:
@Blisto91 https://github.com/Blisto91 and @BlaqG
https://github.com/BlaqG, I confirmed the black screen issue is related
to doitsujin/dxvk#2504 https://github.com/doitsujin/dxvk/issues/2504 by
compiling the latest release of DXVK with the following patch, as suggested
in the other thread.diff --git a/src/dxvk/dxvk_adapter.cpp b/src/dxvk/dxvk_adapter.cpp
index 24c7cea7..c099d719 100644
--- a/src/dxvk/dxvk_adapter.cpp
+++ b/src/dxvk/dxvk_adapter.cpp
@@ -311,7 +311,7 @@ namespace dxvk {
m_deviceFeatures.khrBufferDeviceAddress.bufferDeviceAddress;if (enableCudaInterop) {
devExtensions.nvxBinaryImport.setMode(DxvkExtMode::Optional);
// devExtensions.nvxBinaryImport.setMode(DxvkExtMode::Optional); devExtensions.nvxImageViewHandle.setMode(DxvkExtMode::Optional); devExtensions.khrBufferDeviceAddress.setMode(DxvkExtMode::Optional);Specs:
Distro: Fedora 36
Steam: Flatpak
Proton: Proton-GE 7.31-1
Kernel: 5.19.6-200.fc36.x86_64
GPU: NVIDIA RTX 2070
Driver: 515.65.01—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/3899#issuecomment-1235981937,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AP3UHQLUF3OHDTAE4HL75OTV4KGKDANCNFSM4NHW6WVQ
.
You are receiving this because you were mentioned.Message ID:
@.***>
@BlaqG, I published a compiled release. To test, find your Proton directory and replace both the x64 and x32 DXVK DLLs.
Friendly reminder: don't trust random people on the internet and compile it yourself if you can.
Thank you very much! I will try it out tonight.
Kind regards
On Sat, Sep 3, 2022, 18:17 Alice P. Hacker @.***> wrote:
@BlaqG https://github.com/BlaqG, I published a compiled release
https://github.com/awth13/dxvk/releases/tag/1.10.3-439043d. To test,
find your Proton directory and replace both the x64 and x32 DXVK DLLs.Friendly reminder: don't trust random people on the internet and
compile it yourself if you can.—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/3899#issuecomment-1236155648,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AP3UHQJJAWRK7H2YSVBPEQDV4N2YXANCNFSM4NHW6WVQ
.
You are receiving this because you were mentioned.Message ID:
@.***>
@BlaqG, I published a compiled release. To test, find your Proton directory and replace both the x64 and x32 DXVK DLLs.
Friendly reminder: don't trust random people on the internet and compile it yourself if you can.
Thank you for solving this problem!
The game launched 10/10 times after replacing the dll's.
Bye bye dual boot!
Solved by adding the dll's from @awth13 to:
64-bit: steam/steamapps/common/Proton - Experimental/files/lib64/wine/dxvk/
32-bit: steam/steamapps/common/Proton - Experimental/files/lib/wine/dxvk/
@BlaqG, I published a compiled release. To test, find your Proton directory and replace both the x64 and x32 DXVK DLLs.
Friendly reminder: don't trust random people on the internet and compile it yourself if you can.
Thanks for this :) and for the advice, and I had to be strict, but sadly couldn't get far compiling dxvk on ubuntu 20.04
@Blisto91 and @BlaqG, I confirmed the black screen issue is related to doitsujin/dxvk#2504 by compiling the latest release of DXVK with the following patch, as suggested in the other thread. After replacing the DLLs with the patched ones, the game launches and works fine.
Thank you so much!!
Good deal, this looks like progress although i was wondering about installing the dlls
do they have to be installed in the Proton that is being used to run dayz
or can they be installed into the dayz game prefix. Not that i am trying to sound like a noob at this
but could i get a more detailed and concrete installation instructions.
Good deal, this looks like progress although i was wondering about installing the dlls do they have to be installed in the Proton that is being used to run dayz or can they be installed into the dayz game prefix. Not that i am trying to sound like a noob at this but could i get a more detailed and concrete installation instructions.
inside your proton installation, just copy them in the directories like @BlaqG said. I can play on every modded server now without any problems
Replying to https://github.com/ValveSoftware/Proton/issues/3899#issuecomment-1235981937
Can confirm that this absolutely fixed the black loading screen.
For those that are struggling to build the DLL binaries, with broken setups and dependencies for your system - I struggled in Ubuntu.
I ended up using an arch-based Docker container to build these - https://github.com/jp7677/dxvk-docker
- clone the repo above
- clone dxvk repo inside this to ./dxvk (make sure you clone recursively for the git submodules)
- make the change to src/dxvk/dxvk_adapter.cpp
- ./setup-dxvk-docker.sh - builds the docker image to run
- ./make-dxvk.sh - runs the build inside a docker container from image just built
- confirm your steam directory path in the last script "install-dxvk.sh"
- ./install-dxvk.sh (couple of errors, missing DLLs expected - don't worry)
That's it - launched first time, and every time so far. Was able to use dztui to load a modded Iztek map last night
Ok - seems like the 1.19 update reverted this on Experimental, I tried running ./install-dxvk.sh again, but no dice - possibly have to build again, unsure, will check later
Ignore me here, I had to switch Experimental over to 7.0-4 from GE - working fine again
Replying to https://github.com/ValveSoftware/Proton/issues/3899#issuecomment-1236181341
Following this guide got me up and running with Proton Experimental (not 7.0.x) as of this writing.
Game was working just fine like 1-1.5 weeks ago, but today black screen. Copying the pre-compiled binaries (from here : https://github.com/awth13/dxvk/releases/tag/1.10.3-439043d ) is what did the trick.
Naturally, this is a risky business copying files like this, but I'm glad this worked, thanks folks!
ok i tried to install https://github.com/awth13/dxvk/releases/tag/1.10.3-439043d in proton experimental
and it looks like dayz is launching and running but the mods don't look like they are working. Now to verify
i would have to try this on a virtual machine (libvirt) to see if the mods work there.
Could any of you check if the issue is still present with the newly released Nvidia driver and unmodified dxvk?
Hey!
The problem is still present on 520.61.05 and original dxvk.
Card: RTX3060
Kind regards
On Fri, 14 Oct 2022, 13:29 Blisto91, @.***> wrote:
Could any of you check if the issue is still present with the newly
released Nvidia driver and unmodified dxvk?—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/3899#issuecomment-1278881187,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AP3UHQKNTUJ73WZPYWYATD3WDE72DANCNFSM4NHW6WVQ
.
You are receiving this because you were mentioned.Message ID:
@.***>
ok i tried to install https://github.com/awth13/dxvk/releases/tag/1.10.3-439043d in proton experimental and it looks like dayz is launching and running but the mods don't look like they are working. Now to verify i would have to try this on a virtual machine (libvirt) to see if the mods work there.
Mods works fine, but not through the vanilla launcher.
Use this: https://github.com/bastimeyer/dayz-linux-cli-launcher
This has nothing to do with dxvk.
Kind regards
Replying to [#3899 (comment)](https://github.com/ValveSoftware/Proton/issues/3899#issuecomment-1236181341)
Naturally, this is a risky business copying files like this, but I'm glad this worked, thanks folks!
I included the instructions to build your own, dockerized, it's above
yeah i don't doubt that i could build it, i have done it before (Didn't need docker i to do it either i don't think)
however i don't get why i would have to use dayz-linux-cli-launcher shouldn't the vanilla launcher
handle things ok? Whatever i will try it and see. Later
Replying to https://github.com/ValveSoftware/Proton/issues/3899#issuecomment-1239478470
Hey it seems like you have a concrete mindset on this all (My compiling/git skills are abyssmal) would you mind posting exact commands that would allow me to achieve launching the game without black screen?
yeah i don't doubt that i could build it, i have done it before (Didn't need docker i to do it either i don't think) however i don't get why i would have to use dayz-linux-cli-launcher shouldn't the vanilla launcher handle things ok? Whatever i will try it and see. Later
the vanilla launcher has been somewhat unreliable thru proton, but if you can make it download the right mods and run the game with the right parameters it should be fine and your problem lies elsewhere. All the launcher needs to do is tell steam to download the right mods and run DayZ with the right command line options. If it doesn't do that right you're probably better off using a 3rd party launcher.
Wow it has been really hard to find a single docker with everything... so
this has proton etc ?
On Fri, Oct 14, 2022 at 4:00 PM alcob-frost @.***>
wrote:
Replying to #3899 (comment)
https://github.com/ValveSoftware/Proton/issues/3899#issuecomment-1235981937Can confirm that this absolutely fixed the black loading screen.
For those that are struggling to build the DLL binaries, with broken
setups and dependencies for your system - I struggled in Ubuntu.I ended up using an arch-based Docker container to build these -
https://github.com/jp7677/dxvk-docker
clone the repo above
clone dxvk repo inside this to ./dxvk (make sure you clone recursively for the git submodules)
make the change to src/dxvk/dxvk_adapter.cpp
./setup-dxvk-docker.sh - builds the docker image to run
./make-dxvk.sh - runs the build inside a docker container from image just built
confirm your steam directory path in the last script "install-dxvk.sh"
./install-dxvk.sh (couple of errors, missing DLLs expected - don't worry)
That's it - launched first time, and every time so far. Was able to use
dztui to load a modded Iztek map last nightHey it seems like you have a concrete mindset on this all (My
compiling/git skills are abyssmal) would you mind posting exact commands
that would allow me to achieve launching the game without black screen?—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/3899#issuecomment-1279561714,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWOIRPRHO43CNBQ6F7PKBK3WDHQ2RANCNFSM4NHW6WVQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>
Installing the https://github.com/awth13/dxvk/releases/tag/1.10.3-439043d fixes for proton 7.0-4 and experimental did got me further (bypassing the black screen), but now the game crashes half way into the initial loading screen :(
yeah that release from awth13 is a bit old my friend. try the newest with proton experimental.
I had to update to his newest release as well. here: https://github.com/awth13/dxvk/releases.
Not perfect but no blackscreen and no game crashes. Seriously dayz keeps getting patched all the time
it seems, still that means they are maintaining it so that could be a good sign unless they mess up.
So far so good i guess.
@10ked, thanks for the quick response. I tried the release: https://github.com/awth13/dxvk/releases. However the same issue occurs for me. However one thing to note - this release https://github.com/awth13/dxvk/releases/tag/1.10.3-439043d broke Titan Quest Anniversary Edition to have a black screen on the splash screens, at least now it works with https://github.com/awth13/dxvk/releases. I guess it can be something very specific with my hardware and software combination.
@Aberrance Um, maybe this might seem a strange question but this is a dayz github channel isn't it
what does Titan Quest Anniversary Edition have to do with it ?
Still i get if you are having similar issues the same fix may help. Also the newest stable nvidia driver can't hurt
either.
I've only experienced crash halfway into initial loading screen the few
times I forgot to run "sudo sysctl -w vm.max_map_count=1048576".
Anything interesting in the logs?
On Fri, 4 Nov 2022, 22:16 Aberrance, @.***> wrote:
Installing the https://github.com/awth13/dxvk/releases/tag/1.10.3-439043d
fixes for proton 7.0-4 and experimental did got me further (bypassing the
black screen), but now the game crashes half way into the initial loading
screen :(—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/3899#issuecomment-1304267214,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AP3UHQP2BG6HU757AQI22HDWGV4KHANCNFSM4NHW6WVQ
.
You are receiving this because you were mentioned.Message ID:
@.***>
@BlaqG I had the launch option as you suggested:
As for logs - I am not sure where to look for them (I can post them here if I can know where to look, so if can help someone to try figure out what can be the problem).
@10ked I know that this is a dayz github, but I felt like mentioning that this fix can impact other games as well. So far I tested 10-15 games from my library. Apart from the earlier version freezing Titan Quest, the new version seems to improve the delay of the UI appearance after going back from options into game-play while spectating a game in AOE 2 DE (which could not be observed with Proton GE or Experimental before applying the fix).
As for the Nvidia Drivers I have the latest ones pushed trough Manjaro's repositories - NVIDIA Driver Version: 520.56.06
ok fair enough i was mainly interested in dayz but i can see it might affect other games as well. I for one thing will be glad
when this fix is stabilized and included so i don't have to keep patching proton experimental every time there is an
update for it which is unfortunately necessary. Also the vm.max_map_count can be added into /etc/sysctl.conf
as line:
vm.max_map_count=1048576
so this should do the trick without using launch options. Still there is more than one way to do things so that is up to you.
@10ked, apparently this launch options that I showed above does nothing for me. I tried your suggestion of adding the line: vm.max_map_count=1048576 directly into my sysctl.conf file and the result is that DayZ runs with no problem. I tried two different ways so far for that - suggested in protondb comments and apparently they don't work. However now I can confirm that this method works. So for further reference of people having a crash in the loading screen after applying the fix: apply the method described by @10ked in the above comment.
Sometimes going basic is the best way to go.
@Aberrance Um, maybe this might seem a strange question but this is a dayz github channel isn't it what does Titan Quest Anniversary Edition have to do with it ? Still i get if you are having similar issues the same fix may help. Also the newest stable nvidia driver can't hurt either.
I have same with TES Online. So I did put x64 files into ~/.steam/steam/steamapps/common/DayZ so only dayz use it and it worked perfectly. Not sure about BattlEye tho since it dont like modified files.
Edit: After a month i confirm its safe with BattlEye.
I've had no problems since dropping in the binaries from the Docker build instructions I posted earlier
I created a patcher that fixes issues with installing/launching workshop mods and when using the official launcher.
Also tested on steam deck, though entering the directory is not elegant.
- Download release from here https://github.com/valters-tomsons/DayZLauncher-UnixPatcher
- Extract it and
cd unixpatcher/bin/ - Run
./DayZLauncher.UnixPatcher.exeand provide path to your installation: (eg. "/primary/SteamLibrary/steamapps/common/DayZ/") - Enjoy!
I just noticed that the black screen issue suddenly had disappeared.
I thought I was using a patched version of GE-Proton, but have been running DayZ with the latest stable version of the official Proton.
Seems like this might have been fixed in version 1.20 of DayZ.
I now seem to be having an issue launching the launcher client, exits immediately after it opens - anyone else getting this?
I just tested. It runs with no problems for me.
hangs on boot after today's update (1.24)
DayZ: attempting to connect to servers with Proton Experimental/9.0 returns "Connecting failed (0x00020009)"
Issue transferred from https://github.com/ValveSoftware/steam-for-linux/issues/10542.
@aclist posted on 2024-02-28T02:41:21:
- Steam client version (build number or date): 1708985249
- Distribution (e.g. Ubuntu): Arch Linux
- Opted into Steam client beta?: Yes
- Have you checked for system updates?: Yes
- GPU: Nvidia
Steps for reproducing this issue:
This appears to be a regression introduced in the new version of Proton.
- Set DayZ's compatibility tool to Proton Experimental or Proton 9.0 Beta
- Launch DayZ
- Select Play DayZ if prompted in the launch options dialog
- Use the quick server launcher or click Play to boot directly into the main menu
- Select any server (happens on any; for this example, use an Official server as a control)
- Click to connect and wait
- Returns an error dialog:
Connecting failed (0x00020009)
The problem is resolved by rolling back to Proton 8.05.
Hello @aclist, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.)
Same issue as @aclist
I did a bit of digging, here is the log
steam-221100.log.gz
I did do some packet tracing with wireshark, and basically, the client sends packets of only 0 with 256 data length as soon as it's supposed to encrypt traffic (which is the 4rth packet the client sends on UDP p2302), repeats that 9 times, which I assume is it's attempts at trying again, I can provide the packet .pacpng to open with wireshark if you want to see (I also have someone's successful connection to compare with)
Edit: actually, easier to see here: (left is successful connection, right is 0x00020009, red is client sending, blue is server sending)
The big chunk of 0s is where the encryption is supposed to start for the client from my understanding, and in the server log, we get an error message Error decrypting message: error:04099079:rsa routines:RSA_padding_check_PKCS1_OAEP_mgf1:oaep decoding error which basically means it tried to decrypt the packets full of 0 (and failed obviously), that message is repeated 9 times, one for each packet.
note that this issue doesn't seem to happen with proton 8 ~(except that proton 8 crashes somewhere else for me)~ (edit: fixed that part, was a my bad issue)
I built 436634421b0955c8b520d82ee1b1be6f8fadb594 and launched the game with it but it still got 0x00020009, built experimental, same issue. I do have a working build environment tho so if you want me to test another build on my machine I can do it!
hangs on boot after today's update (1.24)
I had to remove my shader cache and upgrade to the latest ProtonGE
i have usually had better luck with ProtonGE.
DayZ connection stopped working in Proton 9 beta 12
Issue transferred from https://github.com/ValveSoftware/Proton/issues/7548.
@roadapathy posted on 2024-03-03T20:32:11:
Compatibility Report
- Name of the game with compatibility issues: DayZ
- Steam AppID of the game: 221100 (223350?)
System Information
- GPU: AMD RX 6700 TX
- Video driver version: OpenGL version string: 4.6 (Compatibility Profile) Mesa 23.2.1-1ubuntu3.1
- Kernel version: Linux version 6.8.0-rc6joel (gcc ( Ubuntu 13.2.0-4ubuntu3 ) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.41 ) SMP PREEMPT_DYNAMIC
- and also Generic Ubuntu stock Kernel 6.5.0-21-generic
- Link to full system information report as Gist: https://github.com/ValveSoftware/Proton/tree/proton_9.0
- Proton version: 9 beta 12
I confirm:
- [x] that I haven't found an existing compatibility report for this game.
steam-221100 - DayZ.log.tar.gz - [x] that I have checked whether there are updates for my system available.
Symptoms
It will not connect to the game but previous versions of Proton do connect. Symptom appears within Proton 9 beta 12 from Steam but also from the version that I compiled myself from the GIT page.
Reproduction
This connection error appears in both the Generic Ubuntu Kernel and my own, which is the latest 6.8 mainline and both the Valve official Proton and the one that compiled from the GIT page.
I would like to also add that DayZ mods from Steam Workshop have never worked. I am forced to use an alternative launcher called DZGUI. The DZGUI launches Steam and somehow renames the mod files to where the game works. Otherwise, the game cannot use mods at all and Steam Workshop is useless- it becomes 100% vanilla DayZ.
I want to add a comment about people say "use proton GE", while GE might come with useful tricks, it's not ProtonGE specifically that works, it's just that proton GE uses proton 8, and proton 8 works, the 0x00020009 error only happens on proton 9.
So use proton 8 if you encounter the 0x00020009 error.
Try this for mods;
Easy mode
Thank you. I'm using DZGUI but I wish there was something like this for servers. I cannot run a server with mods at all.
I still get this error for Beta 15 even though I read in the update "DayZ is able to connect to servers again." I'm not sure if I'm assuming the wrong thing, maybe Proton fixed the community server list? This happens when I try to connect to the game server that I saved on my favorites.
The game closes itself at the very first loading screen. No error message is given.
The game closes itself at the very first loading screen. No error message is given.
Does this happen after running: sudo sysctl -w vm.max_map_count=1048576 in the terminal first? With proton8?
The game closes itself at the very first loading screen. No error message is given.
Does this happen after running: sudo sysctl -w vm.max_map_count=1048576 in the terminal first? With proton8?
TY! This made the game work. I'll test some offical and unofficial server.
The game closes itself at the very first loading screen. No error message is given.
Does this happen after running: sudo sysctl -w vm.max_map_count=1048576 in the terminal first? With proton8?
TY! This made the game work. I'll test some offical and unofficial server.
Good! Now make the map count permanent:
echo 'vm.max_map_count=1048576' | sudo tee /etc/sysctl.d/vm.max_map_count.conf
Mods:
Try this:
https://github.com/ice-HoTF/DayZ_Mod_Launcher
(Still working on it, new release tomorrow)
Replying to https://github.com/ValveSoftware/Proton/issues/3899#issuecomment-2016847299
I have corrupted mods. I'll try your launcher. I'm using linux mint, tho.
Replying to [#3899 (comment)](https://github.com/ValveSoftware/Proton/issues/3899#issuecomment-2016847299)
I have corrupted mods. I'll try your launcher. I'm using linux mint, tho.
It should work with mint.
If my script doesn't work, make sure to unsubscribe from all the mods in steam workshop and try again. (The script is downloading mods locally, not subscribing through steam).
The hardest part for me, because my games are not in the same place as my OS, was making mods work. I think I won't be able to use the launcher.
Anyways, I just downloaded al the mods required by a server through the default launcher. All of them were marked a corrupt. I just took these mods and put them into Days prefix from which I loaded them locally.
The hardest part for me, because my games are not in the same place as my OS, was making mods work. I think I won't be able to use the launcher. Anyways, I just downloaded al the mods required by a server through the default launcher. All of them were marked a corrupt. I just took these mods and put them into Days prefix from which I loaded them locally.
Yeah. Keeping the steam games on separate disk or partition is not really recommended in general.
To use my script you need to change the default steam path to your steam path. You could just search for .steam in the script and replace the path on all of the search results with your path.
The DayZ vanilla launcher is not ready for Linux and downloading mods from there will often cause trouble. How will you keep the mods updated?
You can use this command in the terminal to download the mods directly:
steam steam+workshop_download_item 221100 1559212036
Where the mod id: 1559212036 is found in the workshop URL for the mod.
@ nipnipj if https://github.com/ice-HoTF/DayZ_Mod_Launcher will not work you can try dzgui.sh and that actually worked in linux for me. here: https://github.com/aclist/dztui
It does all the updating and downloading of the mods. I tested it on Slackware 15 and with a bit of work
i managed to get it working and tested it on a modded server with good success. Still choice is good and if you are happy
with what you have i am good with it.
New issue for me here. Same specs as above, but I'm using XFCE instead of IDEA.
Weird problems occurs when i "tab" out of the game and back in.
It juts STARTED HAPPENING after I installed a small dayz update i think.
If anyone could tell us if its still running great for you, i will change a few things on my system.
That feedback would be much loved
system info:
OS: Arch Linux
6.10.8-arch1-1
CPU: AMD Ryzen 9 7950X3D 16-Core Processor
GPU: NVIDIA NVIDIA GeForce RTX 4070 Ti
GPU DRIVER: NVIDIA 560.35.03
RAM: 32 GB
LOGS: https://pastebin.com/ebpKwHAJ
EDIT: crahses happen at random times now, even before the game fully loaded. trying to catch a log of that, would be really usefull
Posting again sorry, but this log is super short and it crashed, any ideas?
just gonna go with debian and see ow it runs
Posting again sorry, but this log is super short and it crashed, any ideas? just gonna go with debian and see ow it runs
I can't spot why it's crashing while taking a quick look at your logs.. But I think you might try some typical troubleshooting steps for DayZ.
This usually works:
- Unsubscribe to all mods.
- Uninstall Dayz.
- Remove the DayZ program folder. This one in your case: \home\max\.local\share\Steam\steamapps\common\DayZ\
- Do a fresh install.
I've experienced DayZ crashing after some of the big updates. Having Steam verifying the install files will usually fix things, but in some cases I've had to do the steps above on my son's PC. He's had the same issues as you and he's running Winblows ;-).
I'm getting a weird crash where its too the tty. I've attached my proton log, and xorg log since it's crashing xorg also.
dayzcrashtotty.tar.gz
I was able to get it working by running this command:
sudo sysctl -w vm.max_map_count=1048576To make it permanent:
echo 'vm.max_map_count=1048576' | sudo tee /etc/sysctl.d/vm.max_map_count.confGame now loads and plays fine when started with the second launch option.
This fixed it for me!
Does anyone get an issue where (after 40~60 minutes) the frames start to stutter, spiking along with mouse movement.
I can't figure out what's caused it - DayZ Experimental seems to work fine, so I clean out DayZ, reinstall, still persists???
@chrisbward Hi there. Yes this issue is tracked at https://github.com/ValveSoftware/steam-for-linux/issues/11446
Wow, thank you for such a quick response - I had no idea this was happening for other games also. I wonder why Experimental could run fine with no issues?
I'm having issues with DayZ after the 1.28 update.
As reported here: https://feedback.bistudio.com/T192498#2819603
The game starts freezing 10-60 seconds after spawning in.
I've tried different launch parameters and different versions of Proton. I see that more people have this issue.
I'm running CachyOS. I've also tested it on Pop_OS 24.04.
Does anyone know about a possible workaround?
Launch steam through konsole/terminal and share the log from it after it crashes. Never had any issues like that on arch, debian or kde neon.
What steps have you done to troubleshoot so far?
-------- Original Message --------
On 6/18/25 20:12, Svampebob1 wrote:
Svampebob1 left a comment (ValveSoftware/Proton#3899)
I'm having issues with DayZ after the 1.28 update.
As reported here: https://feedback.bistudio.com/T192498#2819603The game starts freezing 10-60 seconds after spawning in.
I've tried different launch parameters and different versions of Proton. I see that more people have this issue.
I'm running CachyOS. I've also tested it on Pop_OS 24.04.Does anyone know about a possible workaround?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>
I've done a bit more troubleshooting. Instead of killing the game when it starts to freeze, I've just waited. After about a minute I get kicked back to the login screen with the following error: You were kicked off the game. BattlEye (client not responding).
I've verified game files, reinstalled the game, reinstalled CachyOS, tried latest GE-Proton, Proton Experimental, Proton 10.3, Proton 9.0-4, Proton-hotfix, Proton-cachyos.
I've tried without launch parameters and variations of these parameters: __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 SDL_VIDEODRIVER=wayland ENABLE_HDR_WSI=1 ENABLE_VKBASALT=1 mangohud game-performance %command%
I've also disabled Steam Overlay and HDR.
I've tried a fresh install of Pop_OS 24.04 with a fresh home folder. Same issue there both in Wayland and Xorg.
This is the log after the game freezes (restoring display mode messages is since I'm tabbing out and in of the game):
11302.739:0130:0180:trace:mscoree:DllMain (00006FFFFDE10000, 3, 0000000000000000)
info: Restoring display mode: 2560x1440@144
info: Setting display mode: 2560x1440@144
info: Restoring display mode: 1440x2560@60
info: Setting display mode: 1440x2560@60
11376.620:0128:0144:fixme:oleacc:find_class_data unhandled window class: L"[#32769](/issue/ValveSoftware/Proton/32769)"
11376.633:0128:0144:fixme:uiautomation:msaa_provider_GetPatternProvider Unimplemented patternId 10002
11376.633:0128:0144:fixme:uiautomation:base_hwnd_provider_GetPatternProvider 0000000000834910, 10002, 000000000182F8A0: stub
11376.645:0128:0144:fixme:oleacc:find_class_data unhandled window class: L"[#32769](/issue/ValveSoftware/Proton/32769)"
11376.747:0170:0174:trace:loaddll:free_modref Unloaded module L"C:\\users\\steamuser\\AppData\\Local\\DayZ\\BattlEye\\BEClient_x64.dll" : builtin
11376.889:0170:02d4:warn:threadname:dispatch_exception Thread renamed to "Progressbar async worker"
11376.889:0170:02d4:trace:seh:dispatch_exception code=406d1388 (EXCEPTION_WINE_NAME_THREAD) flags=0 addr=00006FFFFFC0D0C7
11376.889:0170:02d4:trace:seh:dispatch_exception info[0]=0000000000001000
11376.889:0170:02d4:trace:seh:dispatch_exception info[1]=00000009FEEA4BD6
11376.889:0170:02d4:trace:seh:dispatch_exception info[2]=00000000FFFFFFFF
11376.889:0170:02d4:trace:seh:dispatch_exception rip=00006fffffc0d0c7 rsp=00000008b449fd00 rbp=00000008b449ffa0 eflags=00000206
11376.889:0170:02d4:trace:seh:dispatch_exception rax=00000008b449fd50 rbx=00000009feea4bd6 rcx=00000008b449fd20 rdx=0000000000000000
11376.889:0170:02d4:trace:seh:dispatch_exception rsi=0000000000000000 rdi=0000000000000000 r8=00000000ffffffff r9=00000008b449fe00
11376.889:0170:02d4:trace:seh:dispatch_exception r10=0000000000000000 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
11376.889:0170:02d4:trace:seh:dispatch_exception r14=0000000000000000 r15=0000000000000000 mxcsr=00001f80
11376.889:0170:02d4:trace:seh:call_vectored_handlers calling handler at 00006FFFFCDAB1B0 code=406d1388 flags=0
11376.889:0170:02d4:trace:seh:call_vectored_handlers handler at 00006FFFFCDAB1B0 returned ffffffff
11376.889:0170:02d4:warn:threadname:NtSetInformationThread Thread renamed to L"Progressbar async worker"
info: Setting display mode: 2560x1440@144
info: Setting display mode: 2560x1440@144
11399.279:0128:0144:fixme:uiautomation:msaa_provider_GetPatternProvider Unimplemented patternId 10002
11399.279:0128:0144:fixme:uiautomation:base_hwnd_provider_GetPatternProvider 0000000000842BE0, 10002, 000000000182F8A0: stub
info: Presenter: Got VK_SUBOPTIMAL_KHR, recreating swapchain
info: Presenter: Actual swapchain properties:
info: Format: VK_FORMAT_B8G8R8A8_UNORM
info: Color space: VK_COLOR_SPACE_SRGB_NONLINEAR_KHR
info: Present mode: VK_PRESENT_MODE_FIFO_KHR (dynamic: yes)
info: Buffer size: 2560x1440
info: Image count: 5
info: Presenter: Got VK_SUBOPTIMAL_KHR, recreating swapchain
info: Presenter: Actual swapchain properties:
info: Format: VK_FORMAT_B8G8R8A8_UNORM
info: Color space: VK_COLOR_SPACE_SRGB_NONLINEAR_KHR
info: Present mode: VK_PRESENT_MODE_FIFO_KHR (dynamic: yes)
info: Buffer size: 2560x1440
info: Image count: 5
info: Restoring display mode: 2560x1440@144
info: Setting display mode: 2560x1440@144
info: Restoring display mode: 1440x2560@60
info: Setting display mode: 1440x2560@60
11409.628:0128:0144:fixme:oleacc:find_class_data unhandled window class: L"[#32769](/issue/ValveSoftware/Proton/32769)"
11409.642:0128:0144:fixme:uiautomation:msaa_provider_GetPatternProvider Unimplemented patternId 10002
11409.642:0128:0144:fixme:uiautomation:base_hwnd_provider_GetPatternProvider 0000000000844570, 10002, 000000000182F8A0: stub
11409.653:0128:0144:fixme:oleacc:find_class_data unhandled window class: L"[#32769](/issue/ValveSoftware/Proton/32769)"
I see that some people that get this message is using VPN. I don't have a VPN. I've even disabled UFW (default on in CachyOS).
Thanks. I can't see no ovbious reason for a crash in that log. Did you check the .rpt logs for DayZ? Might be something interesting in there. Next would be the Proton logs.
-------- Original Message --------
On 6/18/25 22:18, Svampebob1 wrote:
Svampebob1 left a comment (ValveSoftware/Proton#3899)
I've done a bit more troubleshooting. Instead of killing the game when it starts to freeze, I've just waited. After about a minute I get kicked back to the login screen with the following error: You were kicked off the game (client not responding).
I've verified game files, reinstalled the game, reinstalled CachyOS, tried latest GE-Proton, Proton Experimental, Proton 10.3, Proton 9.0-4, Proton-hotfix, Proton-cachyos.
I've tried without launch parameters and variations of these parameters: __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 SDL_VIDEODRIVER=wayland ENABLE_HDR_WSI=1 ENABLE_VKBASALT=1 mangohud game-performance %command%
I've also disabled Steam Overlay and HDR.
I've tried a fresh install of Pop_OS 24.04 with a fresh home folder. Same issue there both in Wayland and Xorg.
This is the log after the game freezes (restoring display mode messages is since I'm tabbing out and in of the game):
11302.739:0130:0180:trace:mscoree:DllMain (00006FFFFDE10000, 3, 0000000000000000)
info: Restoring display mode: @.***
info: Setting display mode: @.***
info: Restoring display mode: @.***
info: Setting display mode: @.***
11376.620:0128:0144:fixme:oleacc:find_class_data unhandled window class: L"#32769"
11376.633:0128:0144:fixme:uiautomation:msaa_provider_GetPatternProvider Unimplemented patternId 10002
11376.633:0128:0144:fixme:uiautomation:base_hwnd_provider_GetPatternProvider 0000000000834910, 10002, 000000000182F8A0: stub
11376.645:0128:0144:fixme:oleacc:find_class_data unhandled window class: L"#32769"
11376.747:0170:0174:trace:loaddll:free_modref Unloaded module L"C:\users\steamuser\AppData\Local\DayZ\BattlEye\BEClient_x64.dll" : builtin
11376.889:0170:02d4:warn:threadname:dispatch_exception Thread renamed to "Progressbar async worker"
11376.889:0170:02d4:trace:seh:dispatch_exception code=406d1388 (EXCEPTION_WINE_NAME_THREAD) flags=0 addr=00006FFFFFC0D0C7
11376.889:0170:02d4:trace:seh:dispatch_exception info[0]=0000000000001000
11376.889:0170:02d4:trace:seh:dispatch_exception info[1]=00000009FEEA4BD6
11376.889:0170:02d4:trace:seh:dispatch_exception info[2]=00000000FFFFFFFF
11376.889:0170:02d4:trace:seh:dispatch_exception rip=00006fffffc0d0c7 rsp=00000008b449fd00 rbp=00000008b449ffa0 eflags=00000206
11376.889:0170:02d4:trace:seh:dispatch_exception rax=00000008b449fd50 rbx=00000009feea4bd6 rcx=00000008b449fd20 rdx=0000000000000000
11376.889:0170:02d4:trace:seh:dispatch_exception rsi=0000000000000000 rdi=0000000000000000 r8=00000000ffffffff r9=00000008b449fe00
11376.889:0170:02d4:trace:seh:dispatch_exception r10=0000000000000000 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
11376.889:0170:02d4:trace:seh:dispatch_exception r14=0000000000000000 r15=0000000000000000 mxcsr=00001f80
11376.889:0170:02d4:trace:seh:call_vectored_handlers calling handler at 00006FFFFCDAB1B0 code=406d1388 flags=0
11376.889:0170:02d4:trace:seh:call_vectored_handlers handler at 00006FFFFCDAB1B0 returned ffffffff
11376.889:0170:02d4:warn:threadname:NtSetInformationThread Thread renamed to L"Progressbar async worker"
info: Setting display mode: @.***
info: Setting display mode: @.***
11399.279:0128:0144:fixme:uiautomation:msaa_provider_GetPatternProvider Unimplemented patternId 10002
11399.279:0128:0144:fixme:uiautomation:base_hwnd_provider_GetPatternProvider 0000000000842BE0, 10002, 000000000182F8A0: stub
info: Presenter: Got VK_SUBOPTIMAL_KHR, recreating swapchain
info: Presenter: Actual swapchain properties:
info: Format: VK_FORMAT_B8G8R8A8_UNORM
info: Color space: VK_COLOR_SPACE_SRGB_NONLINEAR_KHR
info: Present mode: VK_PRESENT_MODE_FIFO_KHR (dynamic: yes)
info: Buffer size: 2560x1440
info: Image count: 5
info: Presenter: Got VK_SUBOPTIMAL_KHR, recreating swapchain
info: Presenter: Actual swapchain properties:
info: Format: VK_FORMAT_B8G8R8A8_UNORM
info: Color space: VK_COLOR_SPACE_SRGB_NONLINEAR_KHR
info: Present mode: VK_PRESENT_MODE_FIFO_KHR (dynamic: yes)
info: Buffer size: 2560x1440
info: Image count: 5
info: Restoring display mode: @.***
info: Setting display mode: @.***
info: Restoring display mode: @.***
info: Setting display mode: @.***
11409.628:0128:0144:fixme:oleacc:find_class_data unhandled window class: L"#32769"
11409.642:0128:0144:fixme:uiautomation:msaa_provider_GetPatternProvider Unimplemented patternId 10002
11409.642:0128:0144:fixme:uiautomation:base_hwnd_provider_GetPatternProvider 0000000000844570, 10002, 000000000182F8A0: stub
11409.653:0128:0144:fixme:oleacc:find_class_data unhandled window class: L"#32769"—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>
@Svampebob1
I tried the following parameters and was able to load into various servers and run around for 5 minutes waiting for the "freeze within 60 seconds" issue to occur, but could not reproduce it at this time.
- DayZ version:
1.28.160049 - Proton version:
8.0-5(no particular reason for this one, but it was the one I already had set on the DayZ prefix) LD_PRELOADwas not unset in the launch parameters- Steam overlay was disabled
As a control, I used miscellaneous official servers, but I expect the same outcome on modded servers.
In terms of getting some more data points, it would be interesting to know the outcome of your trying Proton 8.0-5.
There are a handful of scattered reports on ProtonDB about your issue, so not sure if there is a common thread between them. It seems to be localized to a subset of users right now, unless users are under-reporting (?).
HTH.
In terms of getting some more data points, it would be interesting to know the outcome of your trying Proton 8.0-5.
There are a handful of scattered reports on ProtonDB about your issue, so not sure if there is a common thread between them. It seems to be localized to a subset of users right now, unless users are under-reporting (?).
We've been moving over the weekend, so I haven't had the time looking further into it.
It is in my interest of getting it working again, so I'll have a look at it as soon as we get our heads above the sea :-)
And thanks for your feedback! I'll try Proton 8.0-5 👍
Tried 8.0-5 with overlay disabled, game would return to homepage part way through the loading (countdown) sequence
Just as a data point for you: the game works out of the box flawlessly on Kubuntu 25.04 with Proton 9.0-4. No issues here at all with a vanilla game on official server.
AMD GPU.
I've tried Proton 8.0-5. No difference.
Just as a data point for you: the game works out of the box flawlessly on Kubuntu 25.04 with Proton 9.0-4. No issues here at all with a vanilla game on official server.
What GPU do you have, Liam? Nvidia or AMD?
script-xxx.log output:
SCRIPT : Registered 302 temporary action enum(s), UAN==302
SCRIPT : ... Backlit Effects Enabled
SCRIPT : Creating Mission: dz\Worlds\ChernarusPlus\data\scenes\intro.ChernarusPlus\mission.c
SCRIPT : AnimSoundObjectBuilderBank: Invalid sound set "scuffErc_sakhal_snow_forest_Char_Soundset".
SCRIPT : AnimSoundObjectBuilderBank: Invalid sound set "walkCro_sakhal_snow_forest_Char_Soundset".
SCRIPT : AnimSoundObjectBuilderBank: Invalid sound set "runCro_sakhal_snow_forest_Char_Soundset".
SCRIPT : AnimSoundObjectBuilderBank: Invalid sound set "jumpErc_sakhal_snow_forest_Char_Soundset".
SCRIPT : AnimSoundObjectBuilderBank: Invalid sound set "jumpErc_en_deforested_Char_Soundset".
SCRIPT : AnimSoundObjectBuilderBank: Invalid sound set "landFootErc_sakhal_snow_forest_Char_Soundset".
SCRIPT : AnimSoundObjectBuilderBank: Invalid sound set "landFootErc_en_deforested_Char_Soundset".
SCRIPT : AnimSoundObjectBuilderBank: Invalid sound set "walkRasErc_sakhal_snow_forest_Char_Soundset".
SCRIPT : AnimSoundObjectBuilderBank: Invalid sound set "walkRasErc_en_deforested_Char_Soundset".
SCRIPT : AnimSoundObjectBuilderBank: Invalid sound set "runRasErc_sakhal_snow_forest_Char_Soundset".
SCRIPT : AnimSoundObjectBuilderBank: Invalid sound set "runRasErc_en_deforested_Char_Soundset".
SCRIPT : AnimSoundObjectBuilderBank: Invalid sound set "landFeetErc_sakhal_snow_forest_Char_Soundset".
SCRIPT : ---- PlayerBase OnStoreLoad SUCCESS ----
SCRIPT : ---- PlayerBase OnStoreLoad SUCCESS ----
SCRIPT : Creating Mission: mpmissions\__cur_mp.sakhal\mission.c
SCRIPT : SyncEvents -> RegisterEvents
SCRIPT : Creating Mission: DZ\worlds\sakhal\data\scenes\intro.Sakhal\mission.c
SCRIPT : ---- PlayerBase OnStoreLoad SUCCESS ----
SCRIPT : ---- PlayerBase OnStoreLoad SUCCESS ----
SCRIPT : ~DayZGame()
.rpt-file output:
=====================================================================
== I:\home\oystein\.steam\debian-installation\steamapps\common\DayZ\DayZ_x64.exe
== I:\home\oystein\.steam\debian-installation\steamapps\common\DayZ\DayZ_x64.exe -exe DayZ_x64.exe
=====================================================================
Exe timestamp: 2025/06/27 20:00:49
Current time: 2025/06/29 10:51:37
Version 1.28.160049
=====================================================================
10:51:37.437 [Inputs] Loading inputs default "bin/constants.xml"
10:51:37.439 [Inputs] Loading inputs default "bin/specific.xml"
10:51:37.440 [Inputs] Loading inputs cfg "C:\users\steamuser\Documents\DayZ\steamuser.core.xml"
10:51:37.442 [Inputs] Exporting inputs cfg "C:\users\steamuser\Documents\DayZ\steamuser.core.xml"
10:53:24.634 [ErrorModuleHandler] :: Error thrown: 0x000400F0 (Client not responding)
10:53:37.77 --- Termination successfully completed ---
Tried 8.0-5 with overlay disabled, game would return to homepage part way through the loading (countdown) sequence
You're talking about the splash screen showing your character, correct? I had this as well, and it seemed out of the ordinary, but after that it returned to the loading screen (effectively showed two loading screens).
@Svampebob1 The error code thrown definitively seems to point to a Battleye-related issue. As an obscure workaround, try using IPv4 if you are on IPv6, as DayZ in conjunction with BE is notoriously problematic with resolving IPv6.
AFAIK, the last update to the Proton Battleye Runtime (appid 1161040) was buildid 12533096 on 2023-11-08, so the BE client itself shouldn't have changed.
Tested on Proton versions from 7 to latest on debian and arch. I am unable to reproduce this error.
- Proton experimental or 8.
- vm.max_map_count set to correct value.
(sudo sysctl -w vm.max_map_count=1048576) - No launch parameters in steam.
Works.
On arch and debian, modded and vanilla plays just fine for me.
Tested on:
GPU: Rtx 3060, Gtx 1660 TI, Gtx 1070, RX 6600, Rtx 3050.
CPU: i5-11400f, i7-7700k, i3-10100, i5-8600k, ryzen 5 1700 and i7-6700.
Seems to me like the 1.28 update did some changes to battlye and borked the game for a few people.
Try a fresh Arch install. I did that last week and have not experienced any problems.
Ice
-------- Original Message --------
On 6/29/25 11:51, aclist wrote:
aclist left a comment (ValveSoftware/Proton#3899)
Tried 8.0-5 with overlay disabled, game would return to homepage part way through the loading (countdown) sequence
You're talking about the splash screen showing your character, correct? I had this as well, and it seemed out of the ordinary, but after that it returned to the loading screen (effectively showed two loading screens).
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>
Replying to https://github.com/ValveSoftware/Proton/issues/3899#issuecomment-3016513059
I'm not using IPv6 in my network.
Replying to https://github.com/ValveSoftware/Proton/issues/3899#issuecomment-3016522462
Wow! Thanks for thorough testing!
The thing is that I'm already on a fresh install. I even tried installing Pop_OS 24.04 and got the same problem.
Since it fails on multiple distributions, I was starting to wonder if it has something to do with my network or hardware in any way. Does any of you use Secure Boot?
At this point the only thing I can think of is installing a new distro. Just to narrow it down. I don't know much about pop os. Secureboot and fast boot= Always disabled.
What kind of CPU and GPU is in this PC?
Ice
-------- Original Message --------
On 6/30/25 08:55, Svampebob1 wrote:
Svampebob1 left a comment (ValveSoftware/Proton#3899)
@.***(https://github.com/Svampebob1) The error code thrown definitively seems to point to a Battleye-related issue. As an obscure workaround, try using IPv4 if you are on IPv6, as DayZ in conjunction with BE is notoriously problematic with resolving IPv6.
AFAIK, the last update to the Proton Battleye Runtime (appid 1161040) was buildid 12533096 on 2023-11-08, so the BE client itself shouldn't have changed.
I'm not using IPv6 in my network.
Tested on Proton versions from 7 to latest on debian and arch. I am unable to reproduce this error.
- Proton experimental or 8.
- vm.max_map_count set to correct value.
(sudo sysctl -w vm.max_map_count=1048576)- No launch parameters in steam.
Works.
On arch and debian, modded and vanilla plays just fine for me.
Tested on:
GPU: Rtx 3060, Gtx 1660 TI, Gtx 1070, RX 6600, Rtx 3050.
CPU: i5-11400f, i7-7700k, i3-10100, i5-8600k, ryzen 5 1700 and i7-6700.
Seems to me like the 1.28 update did some changes to battlye and borked the game for a few people.
Try a fresh Arch install. I did that last week and have not experienced any problems.
Wow! Thanks for thorough testing!
The thing is that I'm already on a fresh install. I even tried installing Pop_OS 24.04 and got the same problem.Since it fails on multiple distributions, I was starting to wonder if it has something to do with my network or hardware in any way. Does any of you use Secure Boot?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>
@Svampebob1 yes, an AMD GPU.
At this point the only thing I can think of is installing a new distro. Just to narrow it down. I don't know much about pop os. Secureboot and fast boot= Always disabled.
What kind of CPU and GPU is in this PC?
Ice
…
RTX 3090 and i5-14600KF.
I'll try to install Nobara or Kubuntu 25.04.
Nice! Let's hope that it will work with one of those distros. If you still experience problems, try Arch. We are both on intel & nvidia and should be able to figure ut out when using the same distro.
Ice
-------- Original Message --------
On 6/30/25 11:20, Svampebob1 wrote:
Svampebob1 left a comment (ValveSoftware/Proton#3899)
At this point the only thing I can think of is installing a new distro. Just to narrow it down. I don't know much about pop os. Secureboot and fast boot= Always disabled.
What kind of CPU and GPU is in this PC?
Ice
…RTX 3090 and i5-14600KF.
I'll try to install Nobara or Kubuntu 25.04.—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>
Seems like it is working again, without trying to install any other distro.
Thanks for your support, guys!
Good to hear! Fred ut✌️
-------- Original Message --------
On 7/10/25 23:40, Svampebob1 wrote:
Svampebob1 left a comment (ValveSoftware/Proton#3899)
Seems like it is working again, without trying to install any other distro.
Thanks for your support, guys!—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>
There is still a problem though. The game starts freezing for about 20 seconds after joining in. This happens the within the first minute after joining in. The difference now is that I'm not kicked out of the game while it freezes. I'm able to play just fine after waiting it out.
Hey! This problem seems like it is CPU-related. I was able to reproduce this "freeze after joining" with a i7-12700H. 11th gen CPUs and older does not seem to have this problem.
I think you'll have to live with this for now until Intel fixes their shit. Disabling hyper threading seems to lower the freeze-time to 5 sec on my end. Before I did that I had to wait 20-30 sec each time I joined.
BTW: I know nothing, this is my assumption based on local testing and AI investigation.
Kind regards / Mvh
ice
-------- Original Message --------
On 7/11/25 10:36, Svampebob1 wrote:
Svampebob1 left a comment (ValveSoftware/Proton#3899)
There is still a problem though. The game starts freezing for about 20 seconds after joining in. This happens the within the first minute after joining in. The difference now is that I'm not kicked out of the game while it freezes. I'm able to play just fine after waiting it out.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>
DayZ 30s freeze after join is confirmed on 12th-gen Intel CPUs, likely due to hybrid-core scheduling or microcode sync issues during world load. Not related to GPU, Proton, or mods. Disabling E-cores or testing different microcode versions may reduce or eliminate the issue. Verified by multiple Linux users.
ice
-------- Original Message --------
On 7/11/25 10:36, Svampebob1 wrote:
Svampebob1 left a comment (ValveSoftware/Proton#3899)
There is still a problem though. The game starts freezing for about 20 seconds after joining in. This happens the within the first minute after joining in. The difference now is that I'm not kicked out of the game while it freezes. I'm able to play just fine after waiting it out.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>
The issue seems to be gone on my end. Logging in normally, no delay or temporary blackscreen.
ice
-------- Original Message --------
On Friday, 07/25/25 at 15:08 ice @.***> wrote:
DayZ 30s freeze after join is confirmed on 12th-gen Intel CPUs, likely due to hybrid-core scheduling or microcode sync issues during world load. Not related to GPU, Proton, or mods. Disabling E-cores or testing different microcode versions may reduce or eliminate the issue. Verified by multiple Linux users.
ice
-------- Original Message --------
On 7/11/25 10:36, Svampebob1 wrote:Svampebob1 left a comment (ValveSoftware/Proton#3899)
There is still a problem though. The game starts freezing for about 20 seconds after joining in. This happens the within the first minute after joining in. The difference now is that I'm not kicked out of the game while it freezes. I'm able to play just fine after waiting it out.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>
I have crazy stuttering in DayZ when using Proton. Is it just me? Game is unplayable
No issues on my end. Tested on 3 PC's. Probably just something on your pc.
List your hardware, distro etc.
ice
No issues on my end. Tested on 3 PC's. Probably just something on your pc.
List your hardware, distro etc.ice
CPU is overclocked, RAM is overclocked, drives are connected as RAID 0, i am sure my PC is fine (i have no issues in other games). Tried proton and proton ge - same stutters
System:
Host: 5700G Kernel: 6.18.6-zen1-1.1-zen arch: x86_64 bits: 64
Desktop: GNOME v: 49.3 Distro: Arch Linux
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: TUF GAMING B550M-PLUS WIFI II v: Rev X.0x
serial: <superuser required> Firmware: UEFI vendor: American Megatrends
v: 3611 date: 09/30/2024
CPU:
Info: 8-core model: AMD Ryzen 7 5700G with Radeon Graphics bits: 64
type: MT MCP cache: L2: 4 MiB
Speed (MHz): avg: 3318 min/max: 409/4854 cores: 1: 3318 2: 3318 3: 3318
4: 3318 5: 3318 6: 3318 7: 3318 8: 3318 9: 3318 10: 3318 11: 3318 12: 3318
13: 3318 14: 3318 15: 3318 16: 3318
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 32 [Radeon RX 7700 XT /
7800 XT] driver: amdgpu v: kernel
Display: wayland server: Xwayland v: 24.1.9 compositor: gnome-shell
driver: gpu: amdgpu resolution: no compositor data resolution: 2560x1080
API: Vulkan v: 1.4.335 drivers: radv,llvmpipe surfaces: N/A
API: EGL Message: EGL data requires eglinfo. Check --recommends.
Info: Tools: api: vulkaninfo gpu: lact x11: xprop
Audio:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 31 HDMI/DP Audio
driver: snd_hda_intel
Device-2: Advanced Micro Devices [AMD/ATI] Renoir/Cezanne HDMI/DP Audio
driver: snd_hda_intel
Device-3: Advanced Micro Devices [AMD] Ryzen HD Audio
driver: snd_hda_intel
Device-4: fifine Microphone driver: hid-generic,snd-usb-audio,usbhid
type: USB
API: ALSA v: k6.18.6-zen1-1.1-zen status: kernel-api
Server-1: PipeWire v: 1.4.10 status: active
Network:
Device-1: MEDIATEK MT7921 802.11ax PCIe Wireless Network Adapter [Filogic
330] driver: mt7921e
IF: wlan0 state: down mac: ea:ca:39:09:56:80
Device-2: Realtek RTL8125 2.5GbE driver: r8169
IF: enp9s0 state: up speed: 1000 Mbps duplex: full mac: 7c:10:c9:c0:9b:9a
IF-ID-1: throne-tun state: unknown speed: 10000 Mbps duplex: full mac: N/A
IF-ID-2: ztwdjpiagx state: unknown speed: 10000 Mbps duplex: full
mac: e2:83:65:a2:08:0b
Bluetooth:
Device-1: IMC Networks Wireless_Device driver: btusb type: USB
Report: rfkill ID: hci0 state: up address: see --recommends
Drives:
Local Storage: total: 694.93 GiB used: 415.9 GiB (59.8%)
ID-1: /dev/nvme0n1 vendor: Toshiba model: N/A size: 238.47 GiB
ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 970 EVO 250GB
size: 232.89 GiB
ID-3: /dev/sda vendor: SanDisk model: SSD PLUS 240GB size: 223.57 GiB
Partition:
ID-1: / size: 470.86 GiB used: 415.57 GiB (88.3%) fs: btrfs
dev: /dev/nvme0n1p2
ID-2: /boot size: 511 MiB used: 333.2 MiB (65.2%) fs: vfat
dev: /dev/nvme0n1p1
ID-3: /home size: 470.86 GiB used: 415.57 GiB (88.3%) fs: btrfs
dev: /dev/nvme0n1p2
ID-4: /var/log size: 470.86 GiB used: 415.57 GiB (88.3%) fs: btrfs
dev: /dev/nvme0n1p2
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: 44.6 C mobo: N/A gpu: amdgpu temp: 48.0 C
Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
Memory: total: 32 GiB note: est. available: 31.13 GiB used: 9.59 GiB (30.8%)
Processes: 1043 Uptime: 4h 13m Shell: Zsh inxi: 3.3.40
Ty! This setup should easily run this game at it's best performance.
What kind of fps numbers do you get while the stuttering occurs? And if you leave it for 1 minute, does the stuttering change?
What does the cpu usage look like while ingame with stuttering?
What have you tried so far to fix it?
ice
-------- Original Message --------
On Wednesday, 01/28/26 at 18:11 KweezyCode @.***> wrote:
KweezyCode left a comment (ValveSoftware/Proton#3899)
No issues on my end. Tested on 3 PC's. Probably just something on your pc.
List your hardware, distro etc.ice
CPU is overclocked, RAM is overclocked, drives are connected as RAID 0, i am sure my PC is fine (i have no issues in other games). Tried proton and proton ge - same stutters
System:
Host: 5700G Kernel: 6.18.6-zen1-1.1-zen arch: x86_64 bits: 64
Desktop: GNOME v: 49.3 Distro: Arch Linux
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial:
Mobo: ASUSTeK model: TUF GAMING B550M-PLUS WIFI II v: Rev X.0x
serial: Firmware: UEFI vendor: American Megatrends
v: 3611 date: 09/30/2024
CPU:
Info: 8-core model: AMD Ryzen 7 5700G with Radeon Graphics bits: 64
type: MT MCP cache: L2: 4 MiB
Speed (MHz): avg: 3318 min/max: 409/4854 cores: 1: 3318 2: 3318 3: 3318
4: 3318 5: 3318 6: 3318 7: 3318 8: 3318 9: 3318 10: 3318 11: 3318 12: 3318
13: 3318 14: 3318 15: 3318 16: 3318
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 32 [Radeon RX 7700 XT /
7800 XT] driver: amdgpu v: kernel
Display: wayland server: Xwayland v: 24.1.9 compositor: gnome-shell
driver: gpu: amdgpu resolution: no compositor data resolution: 2560x1080
API: Vulkan v: 1.4.335 drivers: radv,llvmpipe surfaces: N/A
API: EGL Message: EGL data requires eglinfo. Check --recommends.
Info: Tools: api: vulkaninfo gpu: lact x11: xprop
Audio:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 31 HDMI/DP Audio
driver: snd_hda_intel
Device-2: Advanced Micro Devices [AMD/ATI] Renoir/Cezanne HDMI/DP Audio
driver: snd_hda_intel
Device-3: Advanced Micro Devices [AMD] Ryzen HD Audio
driver: snd_hda_intel
Device-4: fifine Microphone driver: hid-generic,snd-usb-audio,usbhid
type: USB
API: ALSA v: k6.18.6-zen1-1.1-zen status: kernel-api
Server-1: PipeWire v: 1.4.10 status: active
Network:
Device-1: MEDIATEK MT7921 802.11ax PCIe Wireless Network Adapter [Filogic
330] driver: mt7921e
IF: wlan0 state: down mac: ea:ca:39:09:56:80
Device-2: Realtek RTL8125 2.5GbE driver: r8169
IF: enp9s0 state: up speed: 1000 Mbps duplex: full mac: 7c:10:c9:c0:9b:9a
IF-ID-1: throne-tun state: unknown speed: 10000 Mbps duplex: full mac: N/A
IF-ID-2: ztwdjpiagx state: unknown speed: 10000 Mbps duplex: full
mac: e2:83:65:a2:08:0b
Bluetooth:
Device-1: IMC Networks Wireless_Device driver: btusb type: USB
Report: rfkill ID: hci0 state: up address: see --recommends
Drives:
Local Storage: total: 694.93 GiB used: 415.9 GiB (59.8%)
ID-1: /dev/nvme0n1 vendor: Toshiba model: N/A size: 238.47 GiB
ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 970 EVO 250GB
size: 232.89 GiB
ID-3: /dev/sda vendor: SanDisk model: SSD PLUS 240GB size: 223.57 GiB
Partition:
ID-1: / size: 470.86 GiB used: 415.57 GiB (88.3%) fs: btrfs
dev: /dev/nvme0n1p2
ID-2: /boot size: 511 MiB used: 333.2 MiB (65.2%) fs: vfat
dev: /dev/nvme0n1p1
ID-3: /home size: 470.86 GiB used: 415.57 GiB (88.3%) fs: btrfs
dev: /dev/nvme0n1p2
ID-4: /var/log size: 470.86 GiB used: 415.57 GiB (88.3%) fs: btrfs
dev: /dev/nvme0n1p2
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: 44.6 C mobo: N/A gpu: amdgpu temp: 48.0 C
Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
Memory: total: 32 GiB note: est. available: 31.13 GiB used: 9.59 GiB (30.8%)
Processes: 1043 Uptime: 4h 13m Shell: Zsh inxi: 3.3.40—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>
Dayz 1.29 PTT issues
Issue transferred from https://github.com/ValveSoftware/Proton/issues/9707.
@RockyRoadDev posted on 2026-04-23T22:23:14:
Compatibility Report
- Name of the game with compatibility issues: Dayz 1.29
- Steam AppID of the game: 221100
System Information
- GPU: Nvidia RTX 3050
- Video driver version: 4.6.0 NVIDIA 580.126.09
- Kernel version: 6.17.0-20-generic
- Link to full system information report as Gist: https://gist.github.com/RockyRoadDev/7be63a3c8d18eb1fcab8b0c9d2a026fe
- Link to steam runtime diagnostics as Gist: https://gist.github.com/RockyRoadDev/e4397f0d17726d52715f45c809d1a17f
- Proton version: Tried on proton 9, experimental, and hotfix.
I confirm:
- [X] that I haven't found an existing compatibility report for this game.
- [X] that I have checked whether there are updates for my system available.
Symptoms
PTT in Dayz crashes game. No voice chat available since Dayz 1.29 update
Reproduction
- Open game
- Load into server
- Press PTT button (Caps lock by default)
Proton versions
proton experimentalx16 2025-06proton 9.0-4x4 2025-06proton 8.0-5x3 2025-06proton 10.3x2 2025-06proton hotfixx2 2025-06proton 9.0x2 2024-03proton 8.05x1 2024-02proton 7.0-4x2 2022-11proton 7.0-3x2 2022-08proton 7.29x2 2022-08ge-proton7-14x2 2022-04proton 7.0x1 2022-04proton 6.3-8x1 2022-01proton 6.3-8cx1 2021-12proton 5.13x1 2021-12
Launch options
ENABLE_VKBASALT=1x2 2025-06SDL_VIDEODRIVER=waylandx2 2025-06__GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1x2 2025-06PROTON_LOG=1x3 2024-02PROTON_USE_WINED3D=1x4 2022-08PROTON_USE_WINED3Dx2 2022-08PROTON_USE_WINED3D=1.x1 2022-04WINE_FULLSCREEN_FSR=1x1 2022-04WINE_FULLSCREEN_FSR_STRENGTH=2x1 2022-04PROTON_USE_WINED3D=1`x1 2022-03SDL_AUDIO_CHANNELS=2x1 2020-05SDL_DRIVER=alsax1 2020-05SDL_DRIVER=dummyx1 2020-05
Launch lines
PROTON_USE_WINED3D=1 %command% -nosplash -skipintrox3 2022-08%command% -nosplash -skipintrox2 2022-08PROTON_LOG=1 WINE_FULLSCREEN_FSR=1 WINE_FULLSCREEN_FSR_STRENGTH=2 gamemoderun %command% -nosplash -skipintrox1 2022-04
Upstream links
- ValveSoftware/Proton/issues/9707x1 2026-04
- ValveSoftware/steam-for-linux/issues/11446x1 2025-03
- ValveSoftware/Proton/issues/7548x1 2024-03
- ValveSoftware/steam-for-linux/issues/10542x1 2024-02
- doitsujin/dxvk/issues/2504x5 2022-09
- ValveSoftware/steam-for-linux/issues/8557x1 2022-04
DLLs
beclient_x64.dllx2 2025-06crypt32.dllx1 2022-04resources.dllx1 2022-04wineopenxr.dllx1 2021-12xaudio2_7.dllx1 2021-12steam_api.dllx1 2020-06usp10.dllx1 2020-05
Compatibility Report
System Information
I confirm:
No log generated.
Symptoms
Unable to launch DayZ.
Reproduction
Edit:
While the previous errors were indeed errors I don't believe they are related to DayZ rather how proton was being launched. DayZ does start but crashes while loading possibly still related to XAudio and ALSA.
Leaving this open for now.