Open h1z1 opened 4 years ago
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.
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.
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.
PROTON_USE_WINED3D=1
-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.
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 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)) 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:
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/2504
The 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.
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.