search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
23.86k stars 1.04k forks source link

Titanfall 2 (1237970) #4001

Open serebit opened 4 years ago

serebit commented 4 years ago

Compatibility Report

System Information

I confirm:

Symptoms

Additional Comments

I am so happy that I can even make this issue. Titanfall 2 is one of my favorite games of all time, and to see it on Steam and running near flawlessly through Proton is a dream come true.

gardotd426 commented 4 years ago

@serebit the game has run flawlessly through Wine with Lutris for a year at this point. But still, I'm also ecstatic, though... I can't get the game to run. I already have the Origin version, and it has run flawlessly from the moment I got it. I play it every day, I have about 1000 hours so far (all on Linux).

But I just installed the Steam version, and once I get to the Origin sign in, I enter my user ID and password, and then the Origin window pops up but it's completely blank, and nothing happens. I had to kill -9 ... every process to even get it to stop. I have no idea what the problem is.

Arch Linux 5.7.4-8-tkg-pds Proton 5.0-9

It's not letting me connect to Origin, that's the issue. The "Connecting to Origin" window just stays up indefinitely. When running standalone Origin through Wine, that window is present for like, 2.5 seconds and then it connects and Origin pops up. But on Steam, it's just indefinite.

gardotd426 commented 4 years ago

So, I deleted the prefix, and tried again. And it worked. But I'd also changed desktop environments.

For some reason, this implementation WILL NOT work in i3wm. I've confirmed this at this point. I deleted the prefix, logged out and logged back into two other DEs (Deepin first, then GNOME) on the same installation. When I tried to relaunch the game (and since I deleted the prefix, redo the installation/Origin setup), it worked perfectly fine. After that, I logged back out, went to i3, tried again, and same problem as before. And again, All my actual Origin games (including Titanfall 2) work perfectly in i3. It's just the Steam+Origin games that won't. I tried GNOME, it worked there too.

That said, there is a terrible Mesa bug with Titanfall 2 that will cause ring gfx_0.0.0 timeouts and crash the GPU with (at least) Navi GPUs. You can't finish a full match. I've confirmed it with the Origin version as well. It used to not do that, either. But I've been using vulkan-amdgpu-pro and AMDVLK back and forth for Titanfall 2 the last few months, because they perform better than RADV. But RADV will cause GPU crashes on Titanfall 2 with both Steam and Origin versions. It wasn't present on 20.0 (or 19.3). With AMDVLK or vulkan-amdgpu-pro, the game runs perfectly fine, no crashes or anything. But that's a mesa bug, I suppose, so I'll take that up with them. But if anyone sees this and you have a Navi (or potentially other AMD) GPU then just use AMDVLK and you won't get crashes.

kisak-valve commented 4 years ago

Hello @gardotd426, please 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. Also, please clarify if you were using RADV/LLVM or RADV/ACO with the game.

gardotd426 commented 4 years ago

https://gist.github.com/gardotd426/dda2458f42227c97cd4ebc886923bc4b

hakzsam commented 4 years ago

Can you reproduce with RADV_PERFTEST=aco?

gardotd426 commented 4 years ago

Hey @hakzsam how's it going, Yes, ACO crashes. Menus are fine, but in 6 different tries, 3 on the Steam version and 3 on the long-installed Origin version, I couldn't complete a full match (matches are about 12-15 minutes). I reliably would get a ring gfx_0.0.0 timeout and driver crash.

This is not the infamous ring gfx Navi issue, as I actually have that issue with my other Navi card (5600 XT), that issue is generally not reliably reproducible, happens on the regular desktop, etc. This ONLY happens on Titanfall 2, ONLY with RADV, didn't used to happen with RADV, and is reliably reproduced.

As I said, I've had Titanfall 2 installed in Origin for almost a year now, and play literally every day. But about 2 months ago I started using AMDVLK and vulkan-amdgpu-pro because I got a bit better performance at the time, but before that I'd used RADV for months.

At first I thought the Steam version was just borked, since I'd been playing for hours on the Origin version literally right before my first attempt with the Steam version. But when I went back and tried the Origin version, making sure to change over to RADV, the same thing happened. Three times in a row. I went back to the AMD vulkan driver, and played another 4 hours.

I suppose I can try forcing LLVM (I always usually force ACO whenever I use RADV, and did in this case as well), but I don't know how hopeful I am. I mean at least I can play with AMDVLK/vulkan-amdgpu-pro, but most people don't know that's even an option, let alone how to switch back and forth, so hopefully we can get this sorted so no one else has this issue.

Obviously a renderdoc capture isn't a possibility here, so I'm unsure what I can try to gather for you all, aside from journald logs and proton logs. Oh wait, what about umr?

On Fri, Jun 19, 2020 at 8:53 AM Samuel Pitoiset notifications@github.com wrote:

Can you reproduce with RADV_PERFTEST=aco?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/4001#issuecomment-646619325, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM5Y335XYB6CMCUYEINH5ADRXNNUVANCNFSM4OCFH2AA .

gardotd426 commented 4 years ago

@hakzsam I just realized you may have been asking about it not working in i3, but since you're a mesa dev I assume you're asking about the driver crashes, lol.

hakzsam commented 4 years ago

Try to record an apitrace maybe?

gardotd426 commented 4 years ago

I didn't know I could do that when the whole system crashes.

On Fri, Jun 19, 2020 at 9:28 AM Samuel Pitoiset notifications@github.com wrote:

Try to record an apitrace maybe?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/4001#issuecomment-646635655, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM5Y33YGAYYLYJXBTDDVFJDRXNRXJANCNFSM4OCFH2AA .

alosarjos commented 4 years ago

EDIT: For those like me, where Mesa RADV es making the game crash. Install AMDVLK drivers and add this as launch options:

VK_ICD_FILENAMES="/usr/share/vulkan/icd.d/amd_icd64.json:/usr/share/vulkan/icd.d/radeon_icd.i686.json" %command%

By some reason this only works on Xorg session and not Wayland

ghost commented 4 years ago

I'm playing the game on a GTX1050ti with 440.64 drivers on Kubuntu 20.04.

I had some issues with installing Origin initially, but I deleted the prefix and started over. The game now appears to run fine, but performance starts to drop over time, as well as audio channels , until barely any sounds are played at all. Also the game is likely to freeze when loading in that state. Entering a Titan appears to accelerate the problem? Need to investigate a bit more.

gardotd426 commented 4 years ago

EDIT: Since he's now deleted his original, this was what I was replying to:

How do you do this? If I try using the amdvlk drivers with VK_ICD_FILENAMES="/usr/share/vulkan/icd.d/amd_icd64.json" %command%, even origin won't boot...

@alosarjos yeah, and that's not going to work. Because Origin is 32-bit. You're only giving it a 64-bit driver to use.

VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_icd32.json:/usr/share/vulkan/icd.d/amd_icd64.json.

gardotd426 commented 4 years ago

@RalfVB how much VRAM do you have? You might need to go into the settings and lower the VRAM allocation. I've never seen this happen in 7-8 hour long play sessions on AMD cards either, so it could be an Nvidia driver problem.

gardotd426 commented 4 years ago

@alosarjos for future reference, please don't delete your original post when you edit it. Leave the original, and add the edit at the end.

Anyway, using 32-bit RADV with 64-bit AMDVLK has caused numerous problems for me in the past. Just use 32-bit and 64-bit AMDVLK. VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_icd32.json:/usr/share/vulkan/icd.d/amd_icd64.json.

serebit commented 4 years ago

Amendment to my original post (and I'll edit it after posting this): the game has a problem getting into fullscreen. I don't know why, it's a bizarre behavior, but every time I click on the icon after alt-tabbing there's about a 10% chance it'll actually go into fullscreen. Most of the time it'll almost get there and then re-minimize.

gardotd426 commented 4 years ago

Yeah, this is only present on the Steam version, the Origin version can alt-tab fine. But I've noticed the same behavior on the Steam version. It might be because you're supposed to add -noborder to the launch options and use borderless windowed mode, I'm not sure.

On Fri, Jun 19, 2020 at 10:46 PM Campbell Jones notifications@github.com wrote:

Amendment to my original post (and I'll edit it after posting this): the game has a problem getting into fullscreen. I don't know why, it's a bizarre behavior, but every time I click on the icon after alt-tabbing there's about a 10% chance it'll actually go into fullscreen. Most of the time it'll almost get there and then re-minimize.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/4001#issuecomment-646925518, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM5Y33ZX23UVKCFU6JTT5ODRXQPILANCNFSM4OCFH2AA .

serebit commented 4 years ago

@gardotd426 This'll be interesting to check out. Borderless windowed mode did not work correctly on Windows for me; it introduced a ton of framedrops. We'll see if Linux handles this any better.

gardotd426 commented 4 years ago

I ran borderless windowed mode on the Origin version for months and it ran at the full 144 fps at all times. You might have to disable vsync if you have it enabled.

On Fri, Jun 19, 2020 at 10:56 PM Campbell Jones notifications@github.com wrote:

@gardotd426 https://github.com/gardotd426 This'll be interesting to check out. Borderless windowed mode did not work correctly on Windows for me; it introduced a ton of framedrops. We'll see if Linux handles this any better. It seems like alt-tab works correctly, at least.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/4001#issuecomment-646926713, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM5Y33Z72W5XBCN5536DQILRXQQPNANCNFSM4OCFH2AA .

serebit commented 4 years ago

Yep, borderless windowed works. I had to start the Origin client via the command line to change the game's launch options, but once I did? Flawless.

gardotd426 commented 4 years ago

Ayyeee, I did a halp

On Fri, Jun 19, 2020 at 11:15 PM Campbell Jones notifications@github.com wrote:

Yep, borderless windowed works. I had to start the Origin client via the command line to change the game's launch options, but once I did? Flawless.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/4001#issuecomment-646929579, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM5Y33YZPWIOUHCNYQ6EYVLRXQSWXANCNFSM4OCFH2AA .

serebit commented 4 years ago

There is actually one issue that I've found with borderless though-- occasionally the game will forget to render a certain area on the screen in the bottom right corner for about a second. Less annoying than being unable to alt-tab, though.

gardotd426 commented 4 years ago

Are you sure that's not the Steam overlay trying to give you a notification and bugging out? I've never experienced this on Origin.

On Fri, Jun 19, 2020 at 11:24 PM Campbell Jones notifications@github.com wrote:

There is actually one issue that I've found with borderless though-- occasionally the game will forget to render a certain area on the screen in the bottom right corner for about a second. Less annoying than being unable to alt-tab, though.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/4001#issuecomment-646930748, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM5Y33Z2YNQWBDZJHLIVVYTRXQTXTANCNFSM4OCFH2AA .

serebit commented 4 years ago

You'd think, but:

gardotd426 commented 4 years ago

It doesn't work for you? I got steam overlay notifications in the short time I tried to play it on Steam (before the crashing started). I just went back to Origin because it's what I always play on, and I have all my launch options and stuff already set up with Origin. I mainly wanted to buy it on Steam just in case Origin ever borks itself on Linux, and to help contribute to Valve and also help incentivize the whole EA always releasing their games on Steam from now on thing.

On Fri, Jun 19, 2020 at 11:28 PM Campbell Jones notifications@github.com wrote:

You'd think, but:

  • It's not shaped like the Steam overlay indicator, it's above the bottom of the screen and about three times as wide as the indicator would be
  • The Steam overlay doesn't work! :p

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/4001#issuecomment-646931215, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM5Y334QLGCKJZGIAYRKIC3RXQUGNANCNFSM4OCFH2AA .

serebit commented 4 years ago

Yeah, but this just happens with some games. I don't think it's specific to this game, it might just be my distribution.

alosarjos commented 4 years ago

@alosarjos for future reference, please don't delete your original post when you edit it. Leave the original, and add the edit at the end.

Anyway, using 32-bit RADV with 64-bit AMDVLK has caused numerous problems for me in the past. Just use 32-bit and 64-bit AMDVLK. VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_icd32.json:/usr/share/vulkan/icd.d/amd_icd64.json.

Oh, sorry. Anyways, with amdvlk origin just crashes.

screwylightbulb commented 4 years ago

Can confirm I also have the stuttering problem as mentioned in the OP. Basically a sort of stop-go stop-go stop-go stop-go, thing, where the "go" bits are really smooth, but it briefly pauses every second. This happens in the menus as well as in the game. Leaving it in the menus for 30 minutes to see if it was shader related did not improve it.

Manjaro, kernel 5.4.44 NVidia RTX 2060, driver 440.82 GNOME desktop (not sure if relevant)

gardotd426 commented 4 years ago

@alosarjos It works perfectly fine for me. Been using it for months. Copy and paste your launch options here. Actually copy and paste, too.

@screwylightbulb try it with a different DE. GNOME has severe trouble with Titanfall 2 in my experience. I had to legitimately quit using GNOME because Titanfall 2 is my most-played game and it was unplayable with GNOME (and only GNOME).

If switching to another DE (make sure to list which DE it is) doesn't help, make sure Vsync is disabled.

I stay pegged at the 144 at 1440p with a 5700 XT. No stuttering whatsoever.

alosarjos commented 4 years ago

@alosarjos It works perfectly fine for me. Been using it for months. Copy and paste your launch options here. Actually copy and paste, too.

@screwylightbulb try it with a different DE. GNOME has severe trouble with Titanfall 2 in my experience. I had to legitimately quit using GNOME because Titanfall 2 is my most-played game and it was unplayable with GNOME (and only GNOME).

If switching to another DE (make sure to list which DE it is) doesn't help, make sure Vsync is disabled.

I stay pegged at the 144 at 1440p with a 5700 XT. No stuttering whatsoever.

I've tried the different 32 and 64 bit version of Mesa RADV and AMDVLK. Now, I'm on Gnome... So maybe there is something there... Thing is. Going full mesa, game will just crash, I'm unable to finish a single match without crashing (AMD 5700). Using AMDVLK for the game and mesa for Origin will boot, but only on Xorg session, on Wayland the game tries to launch, showing a window in black, and then crashes and everything closes. Tried AMDVLK for both game and origin, origin will become a black window and crash.

Right now the only way to play this on my PC is going into Xorg session, using Mesa RADV 32bits for Origin and AMDVLK 64 bits for the game.

All this on an updated Arch, BTW

screwylightbulb commented 4 years ago

@gardotd426 I tried a plasma session as well as a bare bones openbox session, and I even tried to swap out the login manager from lightdm to sddm. Same behaviour in all cases.

I can run other heavy-ish games like Batman: Arkham Knight without any issue.

gardotd426 commented 4 years ago

@alosarjos Yeah, Wayland isn't remotely ready for prime-time, especially when it comes to gaming. Using Xorg is going to just be taken as a given, for most things. Maybe you haven't encountered this yet, but yeah Wayland isn't ready.

I've never even tried to run this game in Wayland, Origin version or Steam version, because Wayland won't even run some games at all (including this one, apparently). That's a wayland bug, not anything to do with this game, or proton, or amdvlk, or mesa.

The RADV crash, however, is a mesa bug. And needs to be reported.

@hakzsam there's your reproduction fyi. Another Navi user, can't get through a single match without crashing on RADV. But can with AMDVLK. Confirmed Mesa bug?

@screwylightbulb Like I said, make sure Vsync is disabled. Otherwise I don't know, I don't use Nvidia and I never see a single stutter (except sometimes on GNOME, and that's it).

screwylightbulb commented 4 years ago

Oh yeah, forgot to mention, yes - vsync disabled.

gardotd426 commented 4 years ago

Yeah that's unfortunate, are you using Wayland? I guess you're using Xorg for the Plasma and Openbox sessions though so that wouldn't matter.

Like I said, I've only ever used AMD GPUs, though I have used three separate ones with Titanfall 2 at this point. An RX 580 at 1080p, a 5600 XT at 1080p and later 1440, and now a 5700 XT at 1440p. With the 5700 XT as I said I stay pegged at 144fps (I've got benchmarks up at flightlessmango for the origin version). I know of numerous people that play the Origin version on Linux with Nvidia cards.

It honestly might just be the shader thing. The Origin version came with a state cache for DXVK. And with ACO, that really eliminates any stutters for AMD users. But using both Nvidia and no state cache (which there wasn't one for the Steam version because the game was so new on Steam), that just might be it. I would try playing a match and see if it stops over time. Like I said, that's about all I can give you unless I randomly think of something else.

serebit commented 4 years ago

Like I said in the OP, when I run the game off my SSD the spikes are only noticeable in the DXVK frametime graph and barely affect the displayed framerate. It's only when running from a hard drive that the spikes become unbearable. And I don't think this is an Nvidia issue either—I'm using an RX 480. The DXVK HUD doesn't show shaders compiling for any of the stutters, and their duration doesn't change whether I'm using ACO or not. I don't think this is shader-related.

gardotd426 commented 4 years ago

@serebit yeah I wasn't talking to you.

There are like 5 known issues that I'm aware of with this game that can cause stuttering. Yours was already solved, I was speaking to @screwylightbulb.

They didn't say anything about running off an SSD, or HDD. They'd already seen your OP, so either they can't run off an SSD, or they already are, is my assumption.

Also, I ran this game for months off an HDD (a 5400 RPM one at that) with an RX 580 and always stayed around 90-100 fps at 1080p high with zero stuttering. Just goes to show how varied the possible reasons for stuttering are.

EDIT: That's zero stuttering outside of the other issues I've mentioned which I solved at the time by turning off Vsync.

serebit commented 4 years ago

I wouldn't have commented on the issue screwy was having if not for the nature of the stutters—stop, go, stop, go, with the stops being every second almost on a timer. That's identical to what I was seeing.

gardotd426 commented 4 years ago

Here's a benchmark with a 5600 XT I did months ago showing RADV+ACO vs AMDVLK: https://flightlessmango.com/games/23514/logs/112

@hakzsam that also goes to show that the RADV crashing issue wasn't present before. I forgot I had done these comparative benchmarks which is documented proof that the issue wasn't present on previous mesa versions. I guess either myself or @alosarjos should file an official bug report over at Mesa, a RADV bug (at least with Navi) is essentially confirmed at this point.

@serebit well yeah, if they're using an HDD, that's probably the issue. But they'd said they'd tried everything, which I would've assumed included one of the first mentioned solutions. But yeah, @screwylightbulb if you're running off an HDD move it to an SSD if possible.

As I mentioned over to someone on Reddit about this subject, Origin games are actually known to have this issue (at least on Linux). The Lutris installer for Battlefield 1 actually even specifically says to run it off an SSD to reduce/eliminate stutters.

That said, it's odd to me that @serebit would experience stutters on an (essentially) identical GPU to one that I never experienced a single stutter with, both running off an HDD. I didn't move Titanfall 2 to an SSD until quite recently, actually when I went full NVME/SSD for all my storage except backups. Which is the only reason I moved it, like I said I never experienced this issue, and the RX 480 and RX 580 are essentially identical GPUs.

But if it solves the problem, who cares. And @screwylightbulb, if you're on an HDD, go ahead and move it, if you can.

serebit commented 4 years ago

Yeah, come to think of it I only started having this problem when playing the Steam version. Before, I had Origin running through Steam, and running Titanfall 2 through there didn't have any stutters even though it was on my hard drive.

LiamDawe commented 4 years ago

Can confirm on both a HDD and SSD that micro-stutter is there. You can visibly see it in the main menu, as the background video jitters when it happens and the MangoHud frame timings go up each time like clockwork.

Have checked and it happens exactly the same with WineD3D, so it's not specific to DXVK either. This is with NVIDIA.

alosarjos commented 4 years ago

Will try to report the bug to Mesa

gardotd426 commented 4 years ago

Liam, are you using AMD or Nvidia? If you're using AMD, try AMDVLK. You have to use both 32-bit and 64-bit because Origin is 32-bit.

Have you tried/are you able to try the Origin version?

On Sat, Jun 20, 2020 at 11:07 AM Liam Dawe notifications@github.com wrote:

Can confirm on both a HDD and SSD that micro-stutter is there. You can visibly see it in the main menu, as the background video jitters when it happens and the MangoHud frame timings go up each time like clockwork.

Have checked and it happens exactly the same with WineD3D, so it's not specific to DXVK either.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/4001#issuecomment-647007357, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM5Y33235EXGGQV6VGCYPWLRXTGC5ANCNFSM4OCFH2AA .

LiamDawe commented 4 years ago

NVIDIA and don't own it on origin directly.

gardotd426 commented 4 years ago

@LiamDawe after you link your Origin account, if you open up Origin on Lutris then it shows up in your library with a download button, I already have the Origin version so I haven't tried to install it or anything, but I did notice it there.

Seems there might be an issue with the Steam version and/or Proton with Nvidia cards.

Liam if you're willing to download the Origin version (the Lutris install script for Titanfall 2 itself is best, it includes TF2-specific workarounds and at least used to include a cache), let me know. I can buy you a copy and send you a message on Reddit or something. Mainly because I think it would be important to discover whether this is limited to the Steam version or not, as other issues do seem to be only on the Steam version. I only have a 5600 XT and 5700 XT so I can't test it.

LiamDawe commented 4 years ago

I've struggled for the last 15 minutes to even get it to open, now it's refusing so I'm just going to refund and leave it up to someone else. Too much time for me wasted on something like this sorry.

alosarjos commented 4 years ago

@gardotd426 I created a bug report on the Mesa GitLa. Since you know more than me about the game and it's problems it would be amazing if you could keep an eye on it in case the developers need some info you may have.

https://gitlab.freedesktop.org/mesa/mesa/-/issues/3151

gardotd426 commented 4 years ago

Yeah I'm happy to help, I've filed plenty of bug reports with those guys and the AMD guys in the past, I just don't really have it in me right now to actually file the report itself. I'm happy to help track and debug it.

On Sat, Jun 20, 2020 at 11:24 AM José Miguel Sarasola < notifications@github.com> wrote:

@gardotd426 https://github.com/gardotd426 I created a bug report on the Mesa GitLa. Since you know more than me about the game and it's problems it would be amazing if you could keep an eye on it in case the developers need some info you may have.

https://gitlab.freedesktop.org/mesa/mesa/-/issues/3151

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/4001#issuecomment-647009302, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM5Y334VPMIGSACNEVIWDJTRXTIDBANCNFSM4OCFH2AA .

Tk-Glitch commented 4 years ago

So, someone asked me to share a slice of information regarding one of Origin's behaviors leading to a regular stuttering. It's not directly linked to TF2, but can/will affect gameplay. Origin is continuously writing files (local_xxxxxxx.xml.xxxx format) in pfx/drive_c/users/steamuser/Application Data/Origin and this leads to stuttering. Preventing writes to that directory (for example with tighter permissions) fixes the issue with so far no known ill side effect. I won't take responsibility if you try it and something breaks, but at least you got some data 🐸

gardotd426 commented 4 years ago

^That's a legend, right there, ladies and gentleman. @LiamDawe maybe try that at least before refunding.

On Sat, Jun 20, 2020 at 12:07 PM Etienne Juvigny notifications@github.com wrote:

So, someone asked me to share a slice of information regarding one of Origin's behaviors leading to a regular stuttering. It's not directly linked to TF2, but can/will affect gameplay. Origin is continuously writing files (local_xxxxxxx.xml.xxxx format) in pfx/drive_c/users/steamuser/Application Data/Origin and this leads to stuttering. Preventing writes to that directory (for example with tighter permissions) fixes the issue with so far no known ill side effect. I won't take responsibility if you try it and something breaks, but at least you got some data 🐸

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/4001#issuecomment-647014231, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM5Y337SYZ4OR4JSW4KWIGLRXTNCNANCNFSM4OCFH2AA .

gardotd426 commented 4 years ago

@Tk-Glitch just for future reference, would chmod 555 /path/to/directory take care of that? I've very little experience with any chmodding outside of chmod 777, and I'm not experiencing this issue with TF2 but I've had other Origin games stutter more than they should.

serebit commented 4 years ago

Just tested on my own computer, I set the owner of pfx/drive_c/users/steamuser/Application Data/Origin to root and changed the permissions to 755. I don't think I needed to set the owner for this to work, but regardless, it fixed the issue. I do still get the occasional tiny framespike--but these aren't clockwork, are much less frequent and shorter in duration, and seem to be unrelated.