Skip Navigation

User banner
Posts
5
Comments
619
Joined
2 yr. ago

  • Must be difficult since they don't have telemetry to work with.

  • This video is so fucking funny I didn't care that it's almost four hours long lmao

  • Perhaps they were looking at people using SnapTap and similar technologies, which were recently banned in CS2.

    I feel like analogue / hall effect switches can lend a player a substantial advantage in apex when it comes to strafing. I wonder if they've tried to mitigate that.

  • Glad to hear it!

  • small update - there's been a minor (17.4 MiB) patch to Apex since. Could be worth checking in with it to see if it has resolved linux compat,

    Edit - it's working for me on Fedora 40 Workstation. NB that I've never hit the original anticheat issue to begin with, and I use the following launch command to run the game under VKD3D (mostly AoT shader compilation) along with suppressing launch splash screens / videos and presenting Mangohud

    mangohud %command% -novid -anticheat_settings=SettingsDX12.json

    Edit 2 - tested again this morning and still working fine. I think you folks are good to go.

  • A week ago they made an announcement referring to anti cheat improvements. Today, a couple of friends on Windows noted that the game no longer launched with AutoHotKey enabled (no malicious use cases, just using 60% keyboards) as of last night's minor update.

    Since the game is deck verified, I'd expect respawn will resolve this soon enough.

  • What I was alluding to with regards to idle mclk behaviour is that there are two factors at play: vertical balanking interval (intrinsic to available display modes for each physical monitor) and combined display bandwidth (cumulative of all connected displays to the adapter).

    Your mclk will idle high with 'incompatible' VBIs, and it'll also idle high to sustain a lot of display throughput.

    This can be observed regardless of GFX vendor, though symptoms may vary somewhat between them. I suppose it could be considered a limitation of GDDR (the same behaviour was never really observed on HBM GPUs like the Vega 64 or Radeon VII)

    That said, friends of mine with nvidia gpus have fixed various multi-display specific issues using nvidia profile inspector

  • Yikes I wasn't aware of the second part

  • I was about to ask, isn't this guy a prolific dickhead?

  • I don't know if it was a bug so much as a deficiency. OS Improvements to branch prediction will most likely not be backported to Win10

  • I don't think this is related to the OS. What displays do you have connected?

  • It's like that episode of futurama - the mirror wernstrom put in space to reflect sunlight, which gets tapped by a little space rock, and tilts into a solar powered death beam

  • I gather that the nt kernel isn't inherently bad, rather that the aging win32 subsystem is the problem.

  • You're not wrong. I have no idea about the call of duty one either. I'm guessing it similarly doesn't work.

    It sort of highlights another issue; even though a game technically leverages an AC system that can work in Steam, individual developers may not bother getting it running on Linux.

    I'm no fan of Fortnite, but you can't deny it's massively popular. I hope the steam deck sees continued success in order to sway developers. Broadening SteamOS to other HW platforms may also help to an extent.

  • Oh right, neat!

    I guess I'm just thinking of a couple games with BE who have not bothered to reach out for this.

    I think EA and Activision also have newish, bespoke anti-cheat for Battlefield and call of duty respectively. I don't believe either of those work on Linux but I could be mistaken.