Open r3l0c opened 4 years ago
Proton 6.3-5 30579.865:00fc:0108:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFA, 01EDFEF8 30580.092:00fc:0104:fixme:winsock:server_ioctl_sock Unsupported ioctl 4004747b (device=4004 access=1 func=d1e method=3) 30580.092:00fc:0104:fixme:winsock:WSAIoctl unsupported WS_IOCTL cmd (SIO_IDEAL_SEND_BACKLOG_QUERY) 30610.918:00fc:0100:fixme:font:RemoveFontMemResourceEx (873942E9) stub
It freezes at the end of the loading bar:
My System: Betriebssystem: openSUSE Tumbleweed 20210729 KDE-Plasma-Version: 5.22.4 KDE-Frameworks-Version: 5.84.0 Qt-Version: 5.15.2 Kernel-Version: 5.13.4-1-default (64-bit) Grafik-Plattform: X11 Prozessoren: 12 × AMD Ryzen 5 3600 6-Core Processor Speicher: 15,5 GiB Arbeitsspeicher Grafikprozessor: NVIDIA GeForce GTX 1650/PCIe/SSE2
I'm using the latest driver for my GTX 1650 Downloaded the supported Script from Suse Community: https://www.opensuse-community.org/ https://www.nvidia.com/Download/driverResults.aspx/145182/en-us
Game does not even start anymore Proton 6-3-8 Log:https://gist.github.com/McMarius11/0bbbdb6531f49234c5913f16494a9020
with ProtonGE EAC will pop up and freeze at the end. https://gist.github.com/McMarius11/5cfec24bcd8f3d69196de7d696ffe494
OS: Manjaro Linux KERNEL: 5.10.88-1-MANJARO CPU: Intel Core i5-7600K @ 3.80GHz GPU: NVIDIA GeForce GTX 1070 GPU DRIVER: NVIDIA 495.46 RAM: 24 GB
Any updates on EAC support for this game?
Issue with Easy Anti Cheat, game not work!
the devs add EAC support , it works pretty well, but i notice two issues with game 1) LODs system in game not work correctly 2) changing brightness not working in xorg and wayland
sys info - https://gist.github.com/koloved/e5e9ebde78c84383d87dedee54e4679b logs - steam-594650.log
with RADV_DEBUG=nodcc nothing changes , the bug still there
In my case, game still won't start because of eac.
Tested with Proton GE 49, 42, Experimental 7.0 and 6.3.
Also tested it on the steam deck with same results.
steam-594650.log
Here are the parts which might be interesting: 897.849:0130:0134:trace:module:load_dll looking for L"EasyAntiCheat/easyanticheat_x64.dll" in L"Z:\home\arne\.local\share\Steam\steamapps\common\Hunt Showdown\bin\win_x64;Z:/home/arne/.local/share/Steam/steamapps/common/Hunt Showdown;C:\windows\system32;C:\windows\system;C:\windows;C:\Program Files (x86)\Steam;C:\windows\system32;C:\windows;C:\windows\system32\"... 897.850:0130:0134:trace:module:get_load_order looking for L"Z:\home\arne\.local\share\Steam\steamapps\common\Hunt Showdown\EasyAntiCheat\easyanticheat_x64.dll" 897.850:0130:0134:trace:module:get_load_order got hardcoded b for L"Z:\home\arne\.local\share\Steam\steamapps\common\Hunt Showdown\EasyAntiCheat\easyanticheat_x64.dll", as the eac unix library is present 897.850:0130:0134:warn:module:find_builtin_dll cannot find builtin library for L"\??\Z:\home\arne\.local\share\Steam\steamapps\common\Hunt Showdown\EasyAntiCheat\easyanticheat_x64.dll" 897.850:0130:0134:warn:module:load_dll Failed to load module L"EasyAntiCheat/easyanticheat_x64.dll"; status=c0000135
@arne-fuchs hello! Did you install EAC from your library? EAC should be installed from library like any other games in steam
@koloved Yes I did installed it over steam Edit: no I did not. Though you meant the game.
@koloved Thanks! It workes now. Will post performance results soon
Some areas looks a bit weird but overall it runs great especially with FSR enabled!
Edit: Setting graphics settings higher and vram target higher resolved the problem with the textures. It can be, that textures might still "pop" in. Running on a RX 5700 XTX
@arne-fuchs set Video Memory usage target >90% and the bug fixed , nice! thanks!
I have the issue that I can't connect to any region. Hunt says it blocked some areas because of connection issues. So I can't play any online game Found this in the logs: 1672.418:0130:027c:warn:seh:dispatch_exception Thread 027c renamed to "Network"
@arne-fuchs set Video Memory usage target >90% and the bug fixed , nice! thanks!
This doesn't fix the LOD/Texture loading issue for me. I've tried various combinations of Mem Usage target and graphical settings.
Hunt Showdown (594650)
Issue transferred from https://github.com/ValveSoftware/Proton/issues/6549. @LukeDearden posted on 2023-02-18T07:16:59:
Game starts out looking fine but then textures stop loading and the graphics look blobby. Some kind of LOD issue
Adjusting graphics settings (memory usage target/texture quality) doesn't help
Play a round of Bounty Hunt and traverse the map
@LukeDearden commented on 2023-02-18T07:30:47:
I'm unable to attach files to this issue for some reason
@an9949an commented on 2023-02-18T08:03:03:
The same on my RTX3050 mobile. Issue start happens when vram usage go close to the maximum (2 minutes of gameplay on minimal textures). Also I can see that VRAM usage is much much higher than on windows (~1.4gb more on the same settings).
@kisak-valve Actually this original issue was solved because it was an EAC problem. But EAC support was enabled by Crytek 2 days ago. So, maybe it's better to close this old outdated issue and create a new one? I feel that it's kinda important to focus on fixing it as fast as possible to make this anticheat support as successful as possible.
I only have the issue with connection to regions, otherwise the game seems to mostly run fine: Attaching log for debugging help steam-594650.log
@WebsiteDeveloper You can work around that if you just join a party.
Hunt: Showdown (594650)
Issue transferred from https://github.com/ValveSoftware/Proton/issues/6569. @SamPurple22 posted on 2023-02-25T12:39:37:
Proton log: steam-594650.tar.gz
Game starts and works for offline play, like Tutorial mission or Trial mission. Does not work for online play, Bounty or Quickplay. When trying to play online you always need to choose your network regions, and it does not move forward from there. The choose your network region dialog is also missing the ping, latency indicators on the buttons.
Install the game, start it, try to play online. Cannot see latency indicators on select network region dialog. Cannot start online game.
Additional info found in game.log:
<11:53:34> [Hunt Online] [Account] Initializing. <11:53:34> [Hunt Online] [Online Account] Platform initializing: waiting for authentication token. <11:53:35> [Hunt Online] [Account] Initializing online services for client with 'live' settings <11:53:35> [Hunt Online] CProfileInboxService::Init: successfully initialized <11:53:35> [CryCloud] Trying to establish connection with 'capi1-lv-lw-wc.huntshowdown.com:61088' open <11:53:35> [CryCloud] Connection Succeeded <11:53:41> [CryCloud] Sending request: Invoke (0x01000000) remotely on server with messageId = 1, grainId = 0, bodysize = 528 <11:53:41> [CryCloud] [Warning] Obtaining RTT of TCP connection is not supported <11:53:42> [CryCloud] RECV messageid: 1 <11:53:42> [CryCloud] [Client Session] Authentication succeed [gamelog.tar.gz](https://github.com/ValveSoftware/Proton/files/10831151/gamelog.tar.gz)Hi, Update regarding the online functionality, it seems it's a Debian related issue. Game works online, can start a match, the latency indicators are present on network region dialog, with Fedora 37 and Proton Experimental on the same hardware and internet connection.
Update 2: Solution for Debian found, it's related to ICMP sockets. Specifically for Debian, one needs to configure: net.ipv4.ping_group_range="0 1000", here 1000 is my current user gid.
Steps:
for persistent config, sudo /etc/sysctl.d/local.conf, put the line net.ipv4.ping_group_range="0 1000" there, save the file. After restarting your computer, check with sudo sysctl net.ipv4.ping_group_range, it should show the value configured.
Current Debian discussion about changing this setting: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027773 And Fedora 's default is: "net.ipv4.ping_group_range=0 2147483647"
Voodoo time!
@kisak-valve Maybe Steam could check and issue a console warning message regarding this setting, "your user is not in the net.ipv4.ping_group_range allowed groups, no ICMP functionality" ?
Hunt: Showdown (594650)
Upon launching the game, it immediatly goes to a popup that says: Easy Anti-Cheat Hash Catalogue not found.
Reinstalled the game Installed Proton EAC from steam library Verified Gamefiles
Launch the game
Setting VRamUsage to 100 in steamapps/common/Hunt Showdown/user/profiles/default/attributes.xml seems to solve the LOD issue.
seems to solve the LOD issue.
@grego9 It's just postponed it a bit by adding 10% more VRAM. But generally it fixes nothing. Maybe on some setups with 6+ gb of VRAM it can make the issue not so painful but it is still there.
seems to solve the LOD issue.
@grego9 It's just postponed it a bit by adding 10% more VRAM. But generally it fixes nothing. Maybe on some setups with 6+ gb of VRAM it can make the issue not so painful but it is still there.
This matches up with my findings I'm running a GTX 1660 Super with 6GB VRAM and I've tried all the suggested fixes/tweaks.
Sometimes it takes a while to happen other times it happens as soon as you go into a building or traverse the map to a different compound.
It's a visual nightmare on my 1060 3GB
Can confirm excessive VRAM usage with Nvidia GTX 1660 Ti using driver 525.85.05. Game looks like TF2 running on Pentium 4.
Started happening to me after a system update the other night. https://pastebin.com/q6vJfrtT
Hunt: Showdown stopped properly loading textures on Proton Experimental
Issue transferred from https://github.com/ValveSoftware/Proton/issues/6616. @hatani posted on 2023-03-14T14:56:32:
Since Sunday (12-Mar-2023) game stopped to load textures. Sometimes some, sometimes all, first game usually there were textures upon loading, started to vanish after running through map for a while. I've tried reinstall/files verification/config reset/GFX settings reset ingame /various changes of GFX settings ingame, nothing really helped. After switch from Proton Experimental to Proton 7.x, I see no issues with the textures. The game was running perfectly fine until Sunday about noon for at least a week on Proton Experimental.
Use proton experimental, load the game, run a bit to see if textures go missing.
It's the same issue that was actual from the start. But now it is reproducible on any gpu with any VRAM amount. Here I was add the new info about the possible reasons: https://github.com/doitsujin/dxvk/issues/3265#issuecomment-1468879110
Seems like all LOD problems are fixed by the latest dxvk commits. Probably the only problem it has right now is the gamma slider.
Anyone else seem to have random issues with in game audio chat as well?
Seems like all LOD problems are fixed by the latest dxvk commits. Probably the only problem it has right now is the gamma slider.
Yep tested again last night for a few hours and no texture/LOD problems
Replying to https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-1452452118
It seems to be working for other users, anyone got any pointers what i might have to do?
Hi @larsgrah
Some basic steps:
Probably the only problem it has right now is the gamma slider.
The gamma slider problem is much likely caused by CRYENGINE: https://docs.cryengine.com/display/CRYAUTOGEN/CONSOLEPREFIXR#AnchorRGAMMA
It changes the gamma at hardware-level only, not software-level. The option is called "r_gamma" in the game.cfg file.
Hi @SamPurple22
thanks for those steps. I have tried the following steps:
Made sure EAC runtime is installed. Uninstalled the game using steam closed steam, deleted /home/$USER/.steam/steam/steamapps/compatdata/594650.
Started steam again and downloaded the game. Unfortunately it has the same behaviour as before.
EDIT: It works when running steam through Conty, so i assume its something to do with my linux configuration. Though other than running voidlinux (no systemd) its pretty standart.
3 days ago the game ran like a charm on my Arch manjaro xfce4. Then I think there was an update like 2 days ago, and now it's 100% unplayable, the game opens and runs, no crashes or anything, but the framerate is literally 0.1, about 1 frame every 30 seconds. What happened??? I tried reinstalling, updating everything and nothing works.
fixed by running it in steam runtime instead of snap steam and resetting my user settings
Not sure what changed but since the steam beta UI update the game is crashing constantly regardless of what version of proton I use. I'll try to catch logs at some point but is anyone else experiencing this? System info https://gist.github.com/Nicknakin/abdb32c637900f0618934cf9e7a5cc72
I updated to the beta Steam client and noticed right away hunt was crashing when opening the Steam Overlay with the following error
Wine C++ Runtime Library
(X
Assertion failed!
^ *
Program: Z:\home\luke\STEAM\SteamLibrary
\steamapps\common\Hunt Showdown bin
(win_x64\HuntGame.exe
File: ../src-wine/dls/winevulkan/loader_thunks.c
Line: 5275
Expression: "Istatus"
Press OK to exit the program, or Cancel to start
the Wine debugger.
OK
Cancel
I opened an issue here too https://github.com/ValveSoftware/steam-for-linux/issues/9426
Hello @LukeDearden, please temporarily opt out of Steam's client beta, copy your system information from Steam (Steam
-> Help
-> System Information
) and put it in a gist, then include a link to the gist in this issue report.
Hello @LukeDearden, please temporarily opt out of Steam's client beta, copy your system information from Steam (
Steam
->Help
->System Information
) and put it in a gist, then include a link to the gist in this issue report.
Hi,
I can't get the system info from steam beta or not at the moment. Seems something with the AMD GPU is crashing when I try. very similar to this issue
https://github.com/ValveSoftware/steam-for-linux/issues/9267
EDIT:
Some addition info
OS: Fedora Linux 38 (Workstation Edition) x86_64 Kernel: 6.2.13-300.fc38.x86_64 Resolution: 1920x1080, 1920x1080 DE: GNOME 44.1 CPU: AMD Ryzen 5 5600X (12) @ 3.700GHz GPU: AMD ATI Radeon RX 6600/6600 XT/6600M Memory: 2636MiB / 15889MiB
EDIT:
OK I got sys info from the flatpak version of Steam without the crash
https://gist.github.com/LukeDearden/b704a9ddf729ca78417f7aeb43762448
EDIT:
Just to confirm I tried the beta again using the flatpak version of Steam and still get the same Hunt crash with the overlay
Similar story here, but different game:
System information: https://gist.github.com/zetxx/2dac69e8fa5b04c15a8795a8f64e90f9
Hello @zetxx, please do not cross-post feedback on one game on a compatibility report that is tracking a different game.
Having said that, your system is configured to use AMDVLK with 32 bit Vulkan and mesa/RADV with 64 bit Vulkan. Please reconfigure your system to use either AMDVLK or mesa/RADV for both render paths and test if that has an effect.
i forced usage of RADV as per docs https://wiki.archlinux.org/title/Vulkan and everything is working ... even better :)
I made the same experience as @LukeDearden with the Steam beta client. Opted out immediately. But nevertheless, the game is making constant trouble on my system sadly:
Hunt: Showdown (594650)
steam-594650.log (Gnome on Wayland) steam-594650.log (KDE on Wayland)
Somewhat difficult.
Tried to "debug" it on my own by looking up on the internet for some of the reported errors/warnings/fix me messages. Tried to workaround with using various Proton versions and variables; Protontricks and winecfg options; using gamescope, vkBasalt and ReShade for issue 1 and 4 but that introduces more/other issues. Even been using a custom script for disabling Gnome extensions, animations and notifications.
Next step I will install KDE alongside Gnome and see if that makes a change. Went to Windows yesterday again to be able to play "safely" again but I do not want to do that!!!
Kind regards and many thanks to everyone who is involved in developing this stuff!! =)
The UI redesign seems to have been forced today, which means that I can no longer play the game.
The UI redesign seems to have been forced today, which means that I can no longer play the game.
Hi,
For me I can play but it it crashes as soon as I open the Steam Overlay. Disabling the Overlay is an option but it restricts inviting players to the game.
Is the game not launching now for you now or is it just crashing while trying to use the Steam Overlay?
Looking for some advice from @kisak-valve on how we can help troubleshoot this issue?
Replying to https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-1592415395
Currently I'm only able to launch the game at all using proton GE 7-54, anything newer is launching with a crash reported by another user above. Once the game is open, like you've said, interacting with the overlay in any way causes the game to crash. I've mitigated that since yesterday by just disabling the overlay and accepting party invites externally, but you can't send them with the overlay disabled. Otherwise even just playing the game normally I would experience random crashes without interacting with the overlay, which seems to have been fixed by disabling it.
On a potentially related note, since the UI beta went live a while ago the game has been absolutely destroying my computer on launch, no audio for >30 seconds, other applications become somewhat unresponsive, and I can't do anything about it but wait. This continued even after reverting from the beta back to the stable branch, so it doesn't seem to be tied to the UI rework specifically, but I'm not sure how I could go about figuring out what's wrong.
I also want to confirm crashes while interacting with steam overlay and random crashes well (not sure if it is completely random, for example one time it crashed when I pressed F12 which is the steam screenshot button). Problem with overlay isn't constant on my side. For example once it was reproduced constantly (I launched the game few times) but fixed when I reopened steam. UPD: sometimes it crash purely random.
Steam Runtime System Info: https://gist.github.com/Nicknakin/922a6b0010e1ab50e3a200090272ba9a System Info: https://gist.github.com/Nicknakin/ce0b269882b7fe3c20030ecfa4d7fd04 Game Log: https://gist.github.com/Nicknakin/52542b3185993e368dec1f0a974c522b
Compatibility Report
System Information
I confirm:
PROTON_LOG=1 %command%
steam-594650.loggame.log game.log
Symptoms
If proton version lower 4 then black screen and process info in task manager: kernel wait "pipe_read" if proton version > 4 then Easy Anti Cheat cannot run with message box
ERROR: Failed to create EAC game client interface.
Reproduction
Game not run any times, no need special reproducer