DayZ (221100) #3899
Comments
kisak-valve
added
.NET
|
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. |
|
this game not work on wine/proton |
|
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: To make it permanent: 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. |
|
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. |
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 LogBlack Screen Black Screen 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. Proton 6.3-8 dies instantly with the following log: https://pastebin.com/W2wzGnAr System info: https://pastebin.com/1X2p5ikk |
|
same issue as xcenter, it works really rarely like 1/20 attempts to start the game. system info: full proton logfile: https://pastebin.com/ujtpMfSw |
|
Hi The results show me that ( this is doing things when the game starts ) AND I hope this helps the minds that know a lot more than me. Computer: |
|
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
still experimenting with different settings and checking logs, will report any other info I find |
I have same with TES Online. So I did put x64 files into 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.
|
|
I just noticed that the black screen issue suddenly had disappeared. |
|
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 ValveSoftware/steam-for-linux#10542.
Steps for reproducing this issue:This appears to be a regression introduced in the new version of Proton.
The problem is resolved by rolling back to Proton 8.05. |
|
Hello @aclist, please add |
|
Same issue as @aclist 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 note that this issue doesn't seem to happen with proton 8 |
|
I built 4366344 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! |
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 #7548. Compatibility Report
System Information
I confirm:
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. ReproductionThis 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. |
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: Mods: |
I have corrupted mods. I'll try your launcher. I'm using linux mint, tho. |
It should work with mint. |
|
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. |
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: |
|
@ 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 |
and others
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.
The text was updated successfully, but these errors were encountered: