Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

159 Excellent


About mojical

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I have edited the original post with a config to reduce stutters (the dxvk.conf part), would be nice if you can try it out and see if it makes a difference for you.
  2. In my experience to keep your CPU at its maximum frequency it is sufficient to set the "performance" cpu governor, which will still allow for acceptable idle power consumption. Disabling C-states causes a 10-fold increase in idle power usage (10W to 100W) on my CPU, so I would not enforce it via GRUB at least. If changing the governor is still not enough, you can disable C-states temporarily with this command: sudo cpupower idle-set --disable-by-latency 0 And to reenable them: sudo cpupower idle-set -E With some scripting this can be used to disable C-states before launching the game and reenable them when you're finished playing. That way you will not encounter high power draw and temperatures when using the same PC for web browsing and other light tasks.
  3. Have you monitored your GPU core and memory clocks with and without upscaling using a tool like RTSS? I would blame some power saving feature rather than the GPU utilization in itself, because it is indeed paradoxical that using a higher resolution would improve performance.
  4. I would try Nobara, specifically the KDE Nvidia version. If you are using Nvidia, desktops like Gnome or Cinnamon won't be the best option because you can't fully disable the compositor on them, so KDE is preferable. If your poor performance persists, you can use the builtin tool GOverlay to enable a HUD that will tell you about CPU/GPU usage and frequency, as does RTSS on Windows. Be aware that GPU usage will be significantly higher under Linux with DXVK so maybe your 1080 is hitting its limit, odd as it sounds for APB.
  5. Are you on Wayland or X11? Have you tried running X11 with the compositor turned off? You could also try updating to the latest GE-Proton release (23 as of this post), there is no need to run 8-5 specifically but it was the first version that could launch the game without manual tweaking. Since downgrading your drivers helped I suspect the newer drivers may not be playing nice with the somewhat older DXVK in Proton 8-5. Regarding the stutters, putting the command line option DXVK_HUD="compiler" %command% in Steam's launch options will make the game notify you when a shader compilation occurs. If your stutters are due to shader compilation they will go away as you play the game and build up a disk cache of shaders. Overall though unfortunately the experience with Nvidia is not going to be as smooth as with Radeon cards, and I lack any modern Nvidia cards to be able to test.
  6. I've updated the instructions to include Visual C++ runtimes. This is a bit complicated to achieve with the current build but it's a step closer to getting full support, as automatic Steam login is now working. EDIT: Proton-GE now automatically installs the needed VC++ runtimes thanks to my pull request, so I've updated the guide to make use of this development.
  7. Really liking this patch so far, especially the fact that the ACT doesn't lose accuracy from strafing anymore. While I'd rather have the high FPS sliding bug solved completely at least this makes it have no effect on ACT marksmanship accuracy. I also like that the RFP Talon is finally decent without being overshadowed by the Fang or just bad all around. Hopefully for the next patch some of the less used primaries will get buffs too. I think the Curse and Tommygun (M-1922) deserve a look. The Curse is overshadowed by the also underused ACES rifle in both range and TTK so I believe they should be at least equal on range, and the Tommygun could get a fire rate increase to get its TTK in line with the VAS-C2/Trouble Maker. The Trouble Maker is much easier to handle than the Tommygun so it makes no sense for it to have more killing power, yet I don't feel like a nerf to the Trouble Maker is justified with the PMG in its current state.
  8. Proton Experimental just got updated with the fix, so I also updated the guide to make use of it. Crashes and mail breakages should be gone with this new method. Also expect Proton-GE to have this sorted out in the next build.
  9. I am, but unfortunately I must have been wrong about GE's patches because 8.0 GE still does not work.
  10. Seems like you did not set the launch options in the game's properties correctly. Alternatively you can run this terminal command which will fix the login screen and allow you to launch the game without any options: echo -e '[LoginSettings]\nbUseSteamLogin=False' >> "$HOME/.steam/steam/steamapps/common/APB Reloaded/APBGame/Config/APBMachineOptions.ini" You only have to run it once and it will work until you reinstall the game.
  11. Which proton version and GPU brand are you using? Did you encounter any crashes?
  12. Long story short only GE's versions can be used, since the game needs GE's recent EAC patches to work. Install Proton GE 7-55, and while you'll have a broken mailbox and occasional crashes, it's the only way the game will start and actually stay in a district. I'll upgrade the guide as soon as I'm done experimenting with this.
  13. Good point, I decided against writing anything about recommending proprietary drivers for Nvidia users since I assumed it was an obvious step to take. However, for people who are trying Linux out for the first time now that this game is playable this is valuable information. The only caveat is that GPU driver installation varies from distro to distro, so it would not make sense to be too specific about instructions. The new Proton Experimental update available from within Steam is now based on 8.0 and has even fixed the launcher, unlike official 8.0. Unfortunately, it's too early to update the guide and get rid of the launch commands, as the official launcher will run the game with Steam integration and that still crashes to desktop on the login screen. In any case, it's a step in the right direction.
  14. The way I see it, the main reason why the .45 is so centralizing in today's meta is how lackluster all high caliber pistols (and the RFP) are in comparison to it. It makes no sense that the "optimal" secondary pick is the exact same for an OCA primary as it is for an OBIR. I don't think a 5m range reduction will be quite enough if certain competing weapons are not buffed simultaneously, and the optics of further nerfs will be bad for a supposedly high skill ceiling weapon. One such buff would be to the RFP for example, increasing damage so it can barely 3 burst kill with 3 perfect bursts, which is still far weaker than the RFP's original form. Then its effective range could be increased and the Fang's IR3 downgraded to IR1, so the Fang keeps its current range while the Talon and F2P variants get a bit more, but still slightly less than the Fang.
  15. I have updated the guide to use official Proton 8.0 which was released yesterday. This fixes the mail glitch without needing to download an external tool.
  • Create New...