#linux-🐧

1 messages · Page 15 of 1

hollow oar
#

.steam/root/

#

domething

#

compatdata pfx 23**** idk

warped dune
#

Oh, my screenshots aren't embedding

edgy sierra
#

Full path of production_config is going to be ~/.local/share/Steam/steamapps/compatdata/238960/pfx/drive_c/users/steamuser/Documents/My Games/Path of Exile/, unless you've put your steam library on another drive, in which case it'll be that location under /compatdata/238960/pfx/drive_c/users/steamuser/Documents/My Games/Path of Exile/

#

Unless something is crashing before PoE even gets that far, which it looks like that may be the case.

warped dune
#

~/.local/share/Steam/steamapps/compatdata/238960
does not exist, the only file inside
/raspberry/SteamLibrary/steamapps/compatdata/238960/pfx/drive_c/users/steamuser/Documents/My\ Games/Path\ of\ Exile/ is steam_autocloud.vdf

warped dune
#

I removed the logs because I realized they include env vars, gimme a second to redact

edgy sierra
#

Only thing I've been able to find that presented a similar crash was in this thread https://bbs.archlinux.org/viewtopic.php?id=271931 where the person had amdvlk and lib32-amdvlk installed, but that would've shown up in your amd|mesa query so I am doubtful that is the problem. It's certainly a explosive failure rather than a graceful one which makes it much harder to track down.

warped dune
#

Yeah. The log stops at

588614.614:0100:0108:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\uxtheme.dll" : builtin

for several minutes, and all the output into the log up till that point happens in the first few seconds after launching.
A few minutes later, it throws out the dmp and segfault

src/common/pipes.cpp (883) : fatal stalled cross-thread pipe.
src/common/pipes.cpp (883) : fatal stalled cross-thread pipe.
src/common/pipes.cpp (883) : Fatal assert; application exiting
src/common/pipes.cpp (883) : Fatal assert; application exiting
assert_20220530160855_3.dmp[548336]: Uploading dump (out-of-process)
/tmp/dumps/assert_20220530160855_3.dmp
_ExitOnFatalAssert
assert_20220530160855_3.dmp[548336]: Finished uploading minidump (out-of-process): success = yes
assert_20220530160855_3.dmp[548336]: response: Discarded=1
assert_20220530160855_3.dmp[548336]: file ''/tmp/dumps/assert_20220530160855_3.dmp'', upload yes: ''Discarded=1''
pid 548336 != 548335, skipping destruction (fork without exec?)
pid 547920 != 547919, skipping destruction (fork without exec?)
#

No idea what it's doing in that time

#

I found this issue which suggests it could be a pulseaudio issue, but I've already tried starting PoE with -noaudio and PULSE_SERVER=/dev/null, with no change

#

Do note, this is my first time ever trying to play PoE, so I might be looking over something obvious here

edgy sierra
#

Have you tried playing anything else via proton or is this strictly PoE specific?

warped dune
#

This is strictly PoE specific, other games work fine

#

Metro 2033 needed me to disable "Force use of compatibility tool" to get audio working (as apparently it has a native version that steam ignored), and DRG works perfectly fine under Proton as it's only Windows native

#

I've tried running PoE both with and without that option

edgy sierra
#

I guess my next idea would be rebuilding the wineprefix by deleting ~/.local/share/Steam/steamapps/compatdata/238960/ and switching to Proton 7.0-2, then starting PoE again. I tried playing PoE with experimental just now and it started just fine but maybe there's a bug in Proton-experimental that's generating a broken prefix when it needs to build one from scratch.

warped dune
#

Ahhh

edgy sierra
#

Kind of grasping at straws and ways it could only be affecting PoE, and that's one way.

warped dune
#

Okay, I can try that

#

I'm also doing a full system upgrade right now and I'll reboot afterwards to rule out glibc weirdness

warped dune
#

OH okay. I didn't do anything at all, minus the full system upgrade + rebooting and it's fixed itself

#

No idea what was wrong there

#

I appreciate the help / trying to troubleshoot, thanks y'all <3

flat lichen
#

Anyone getting horrible stutters/rubber banding/freezes?

undone stone
#

None of that as it just doesn't open for me lol

#

Worked fine a week or two ago

#

Tried both Proton Experimental and 7.0-2, all game files verified through Steam

#

I see, I had ultramodern %command% in the launch options for GameMode(?), and it launches if I remove it

edgy sierra
#

I don't experience any stutters no. If you're getting rubber-banding you should probably hit F1 and bring up the latency graph because that sounds like an unstable internet connection.

hollow oar
#

How come I never get anything broken except if its the devs end doing it. I use Arch BTW.

fading topaz
#

Is the game crashing with the latest patch? I've crashed like 5 times today

outer pagoda
#

its been crashing a bit with the stash since league started

manic blade
#

Hrm, has anyone figured out how to stop the stutters whenever the game loads in things for the first time, like effects and enemies?

#

I think it has something to do with baking/caching shaders

#

game runs flawlessly unless I run into something new, then it is slideshow time

#

already tried adding --nologo --noasync --waitforpreload --g 2 to the arguments which doesn't do anything

#

(using the lutris-GE-proton7-1 runner)

edgy sierra
#

Standalone has always stuttered much worse than the steam client on linux in my experience. The difference between the steam client and standalone is steam comes with a couple thousand much smaller archive files instead of the one huge content.ggpk, and something in Wine really chugs when the game hits content.ggpk in combat.

I did A/B (Standalone+proton/Standalone+wine/Steam+Proton) testing in Ultimatum and steam client was always the smoothest.

manic blade
#

I've been messing around a bit and it seems like setting the game to dx12 fixed all my stuttering issues

fading topaz
#

I just tested out running it in dx12. While I did find it stuttered less, the beta status is clear. I noticed quite a few weird texture issues. Wouldn't say it impacted gameplay though

vestal pier
#

any idea which setting might reduce system memory utilization a tad? sometimes i need to run vms at the same time and end up oom-img one thing or another. thanks!

fading topaz
#

IMO you'd be better off setting up swap/zswap or configuring VMs to use less ram, instead of tweaking settings in PoE to attempt for that to use less

nocturne void
#

Anyone notice really bad stuttering when in any area for too long? Typically my frames will chug every time I go afk and come back, and I have to leave the area and re-enter to fix it. Seems like a memory leak though I haven’t looked at resource utilization when this happens (will do next time)

outer pagoda
#

Haven't seen it related to staying in area, it'll just start stuttering for a bit every now and then in any instance

fading topaz
#

Well I have had 0 crashes since the 3.18.1 patch, running on Vulkan. Still the occasional stutter, but solid overall

flint laurel
# nocturne void Anyone notice really bad stuttering when in any area for too long? Typically my ...

I have an odd feeling this may be related to the async code. Could me that some internal game threads are put on sleep after some time of not being used. Then when you come back lots of them wake up at once and it's a bit of a struggle that happens. Just a guess though. And if this is the issue there's probably not much you can do about it. Disabling multithreading would likely make performance worse and wouldn't even fix the issue because then every game thread would be on one cpu thread so it would take even longer for them to wake up.

digital drum
digital drum
#

Keep those threads on boi!

unique pewter
#

#!/usr/bin/env bash

_alarm() {
( \speaker-test --frequency "$1" --test sine )&
pid=$!
\sleep 0."${2}"s
\kill -9 $pid
}

getnproc="$(nproc)"
getpoepid="$(pidof 'PathOfExile.exe')"

if pgrep "PathOfExile" > /dev/null 2>&1; then
case "$getnproc" in
4) echo 4 threads found
sleep 1
taskset -pac 1,2,3 "${getpoepid}" &&
_alarm 400 200
echo 'waiting 8 seconds'
sleep 1
echo -e '\e[1A\e[Kwaiting 7 seconds'
sleep 1
echo -e '\e[1A\e[Kwaiting 6 seconds'
sleep 1
echo -e '\e[1A\e[Kwaiting 5 seconds'
sleep 1
echo -e '\e[1A\e[Kwaiting 4 seconds'
sleep 1
echo -e '\e[1A\e[Kwaiting 3 seconds'
sleep 1
echo -e '\e[1A\e[Kwaiting 2 seconds'
sleep 1
echo -e '\e[1A\e[Kwaiting 1 seconds'

        taskset -pac 0,1,2,3 "${getpoepid}" &&
        _alarm 400 200
        echo "core affinity set!";;
    6)  echo 6 threads found
        sleep 1
        taskset -pac 1,2,3,4,5 "${getpoepid}" &&
        _alarm 400 200
        echo 'waiting 8 seconds'
        sleep 1
        echo -e '\e[1A\e[Kwaiting 7 seconds'
        sleep 1
        echo -e '\e[1A\e[Kwaiting 6 seconds'
        sleep 1
        echo -e '\e[1A\e[Kwaiting 5 seconds'
        sleep 1
        echo -e '\e[1A\e[Kwaiting 4 seconds'
        sleep 1
        echo -e '\e[1A\e[Kwaiting 3 seconds'
        sleep 1
        echo -e '\e[1A\e[Kwaiting 2 seconds'
        sleep 1
        echo -e '\e[1A\e[Kwaiting 1 seconds'
        sleep 1
        taskset -pac 1,2,3,4,5 "${getpoepid}" &&
        _alarm 400 200
        echo "core affinity set!";;
    8)  echo 8 threads found
#

sleep 1
taskset -pac 1,2,3,4,5,6,7 "${getpoepid}" &&
_alarm 400 200
echo 'waiting 8 seconds'
sleep 1
echo -e '\e[1A\e[Kwaiting 7 seconds'
sleep 1
echo -e '\e[1A\e[Kwaiting 6 seconds'
sleep 1
echo -e '\e[1A\e[Kwaiting 5 seconds'
sleep 1
echo -e '\e[1A\e[Kwaiting 4 seconds'
sleep 1
echo -e '\e[1A\e[Kwaiting 3 seconds'
sleep 1
echo -e '\e[1A\e[Kwaiting 2 seconds'
sleep 1
echo -e '\e[1A\e[Kwaiting 1 seconds'
sleep 1
taskset -pac 1,2,3,4,5,6,7 "${getpoepid}" &&
_alarm 400 200
echo "core affinity set!";;
12) echo 12 threads found
sleep 1
taskset -pac 2,3,4,5,6,7,8,9,10,11 "${getpoepid}" &&
_alarm 400 200
echo 'waiting 8 seconds'
sleep 1
echo -e '\e[1A\e[Kwaiting 7 seconds'
sleep 1
echo -e '\e[1A\e[Kwaiting 6 seconds'
sleep 1
echo -e '\e[1A\e[Kwaiting 5 seconds'
sleep 1
echo -e '\e[1A\e[Kwaiting 4 seconds'
sleep 1
echo -e '\e[1A\e[Kwaiting 3 seconds'
sleep 1
echo -e '\e[1A\e[Kwaiting 2 seconds'
sleep 1
echo -e '\e[1A\e[Kwaiting 1 seconds'
sleep 1
taskset -pac 2,3,4,5,6,7,8,9,10,11 "${getpoepid}" &&
_alarm 400 200
echo "core affinity set!";;
16) echo 16 threads found
sleep 1
taskset -pac 2,3,4,5,6,7,8,9,10,11,12,13,14,15 "${getpoepid}" &&
_alarm 400 200
echo 'waiting 8 seconds'
sleep 1

#

echo -e '\e[1A\e[Kwaiting 7 seconds'
sleep 1
echo -e '\e[1A\e[Kwaiting 6 seconds'
sleep 1
echo -e '\e[1A\e[Kwaiting 5 seconds'
sleep 1
echo -e '\e[1A\e[Kwaiting 4 seconds'
sleep 1
echo -e '\e[1A\e[Kwaiting 3 seconds'
sleep 1
echo -e '\e[1A\e[Kwaiting 2 seconds'
sleep 1
echo -e '\e[1A\e[Kwaiting 1 seconds'
sleep 1
taskset -pac 2,3,4,5,6,7,8,9,10,11,12,13,14,15 "${getpoepid}" &&
_alarm 400 200
echo "core affinity set!";;
*) echo "Your amount of cpu-threads isn't compatible with this script";;
esac
fi

woeful mango
#

guys i m considering using linux for my poe needs--- can someone please share their experience compared to windows? how much trouble am i gonna have

nocturne void
#

Compared to windows, I've had no trouble at all

#

granted, I have never played poe on windows

#

More serious answer, I've noticed that some 3rd party overlays people use like that trade thing don't work for me, but I think that's because they don't play nice with my window manager

crisp thicket
#

anyone have any idea why the game wont start? im using ubuntu

edgy sierra
#

There are a lot of possible reasons. Using Steam or Lutris/Standalone? Video card?

stiff pumice
#

game runs fine for me on steam using proton @crisp thicket

hollow oar
fading topaz
#

Man I don't know what they did with the latest patch, but my game is now crashing constantly

wet wadi
#

recommending gentoo for a new linux user is like recommending astronaut as a first job for someone out of basic 😂

wet wadi
fading topaz
#

I do, but it turns out the crashing happens with 1st Gen Ryzen CPUs when using SMT. With the reversal of the patch, the issue is (currently) not present

wet wadi
#

Could you describe the crash(es) in detail(how/if they had a beginning/middle/end, BSOD/black/white screen/CTD/instant freeze/slow freeze/etc)?

fading topaz
#

The game would briefly hang, before terminating. Nothing much to it. And as I said, it doesn't happen anymore as they have reverted the patch changes

grizzled harness
#

On standalone or on Steam?

#

Because I've also been getting repeated crashes on standalone so I'm currently in the process of downloading on Steam

#

Idk about the patch thing though because the last time I played this game was in 2015 or smth

obtuse harbor
#

I have been banned for "Third Party Software" while playing on Linux. Have anyone experienced similar issue?

mild urchin
#

message support

obtuse harbor
wet wadi
fading topaz
#

No. It would freeze for a moment, before quitting out. I don't know why you're so interested though seeing as it doesn't happen anymore

fading topaz
obtuse harbor
obtuse harbor
#

Also i wanted to mention that the ban happened when i was trading. I can only assume it counted Firefox as third party software

wet wadi
wide cipher
#

mine froze today once for a little bit and then exited

#

also just got back after 3 weeks summer break and noticed its stuttering alot when before it ran smoothly? updated drivers and proton-ge to newest

#

stays around 55fps but stutters like crazy

wide cipher
#

swapped from 7-24 to 7-18 of ge proton and works smooth again

wide cipher
#

oh wait no, it was just twitch in the background causing stuttering