Jump to content
Forum rules

mojical

Members
 View Profile  See their activity

  • Content Count

    263

  • Joined

  • Last visited

Posts posted by mojical

  1. Posted

    On 12/13/2023 at 1:11 AM, BlatMan said:

    Most of the stuttering is gone, and I think there's less stuttering overall than on Windows, but I need a US East district to be fully populated to test that. A full EU district doesn't stutter as bad as it does on Windows 10. Low pop areas of the districts have slightly higher fps as well. Now I see why so many people claim some games run better under Linux. Honestly, I thought they were all crazy.

     

    Standing next to the car spawn area under the Plantagent building, looking at central park, I get about 120fps to 160fps in Windows. On Debian, I get about 160fps to 210fps standing in that same spot. It varies based on how many players are nearby, so it's hard to get an accurate comparison.

    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. Posted · Edited by mojical

    On 12/10/2023 at 5:47 AM, BlatMan said:

    EDIT:

     

    The stuttering issue is due to cstates. Linux ignores your bios settings and enables cstates by default. My CPU was downclocking to 1.5Ghz while APB was running. Apparently this is normal behavior and there's tons of clowns who think it's a bad idea to run your CPU at it's advertised speed.

     

    To disable cstates, edit the file /etc/default/grub and add "intel_idle.max_cstate=0" to the "RUB_CMDLINE_LINUX_DEFAULT=" line. Mine looks like this after adding it: 

    
GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_idle.max_cstate=0"

     

    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. 

  4. Posted

    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.

    • Like 1

  5. Posted · Edited by mojical

    20 hours ago, BlatMan said:

    EDIT:

     

    Fixed the flickering by installing Nvidia driver version 525. Still have the fps stutters. The game randomly goes from 128 solid to 80fps or lower. It drops lower when moving the mouse, but I don't think the mouse movement is the cause.

     

    The fps drops when I move my mouse. Stays steady at 128fps if I don't provide any input.

     

    The screen constantly flickers. Other guides say to enable "Force Full Composition Pipeline" in Nvidia settings. This causes the audio and video to freeze when the game is in focus.

     

    Kubuntu 23.10

    GE-Proton8-5 and Proton 8.0 (steam)

    Nvidia Driver 535.129.03

     

    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. Posted · Edited by mojical

    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.

    • Like 2

  7. Posted · Edited by mojical

    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.

  10. Posted · Edited by mojical

    On 5/1/2023 at 2:13 AM, gogeo said:

    When it gets to the login screen I get this crash everytime.

    Steam with Proton GE 55, tried 49 as well, same crash.

     

    Specs:

    OS: (Nobara) Fedora 37

    CPU: Ryzen 7 5800X3D.

    GPU: RTX 3060 Ti

    RAM: 32GB DDR4

    DRIVE: Crucial P1 NVMe 1TB

    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.

     

    Merged.

     

    On 5/1/2023 at 1:46 AM, Spillra said:

    Nvidia (2070 super), Proton GE 7-55. I crash at least once every time i launch the game but it runs fine after that.

    I ran it again without most of the config and then i get a solid 300 in a low pop asylum, so there is something in my config that fucks with the FPS
     

    The improvement could also be due to shader compilation delays, it takes time to build a full DXVK shader cache. The cache is stored on disk so it will persist after several starts of the game.

  12. Posted · Edited by mojical

    3 hours ago, NOiR said:

    After the latest update (with new EAC) it doesn't work for me anymore. The launcher starts and game was successfully updated but then, during loading process, everything halts.

    Tested with both Proton versions (8.0 and Experimantal, with and without additional startup command string).

    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. Posted

    On 4/19/2023 at 7:25 PM, your-username-is-not-suitable said:

    Can confirm this guide will work for an Arch minimal install using LXQT + Openbox desktop environment on the Linux kernel (Not hardened lts or zen. Haven't tried those)

     

    A couple of things to note is before installing the drivers as per the section in the ProtonGE tutorial, install the linux-headers package first

     

    If you're on an nvidia card and you've followed the OPs directions etc and the game launches and the splash screen appears, then closes after a few seconds, try uninstalling the amdvlk package. For some reason it shows up after going through this tutorial at least it did for me.

     

    Everything else should be identical to the tutorial posted here at least at the time of making this post.

    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. Posted · Edited by mojical

    1 hour ago, CookiePuss said:

    Suggestions are always welcome.

     

    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.

     

    • Like 1

  16. Posted · Edited by mojical

    31 minutes ago, Ketog said:

    Running like a breeze on the deck using Proton GE 7-53 , surprisingly not pushing it too hard, here's the analytics while my friend medek was with me on a deck as well!

    Looks good! I'm a bit surprised the CPU isn't clocking higher. On the other hand, there's no real reason to target over 60 fps with the Deck.

    Have you gotten any crashes, issues with the launch command or corrupted mail messages with 7-53?

  17. Posted · Edited by mojical

    On 3/22/2023 at 8:06 PM, BlatMan said:

    On Windows, changing m_bUseDiskCache from True to False did stop APB from using the disk, but it didn't have any affect on stuttering. It still freezes during garbage collection, and it often stutters when an opposing player and I shoot at the same time.

     

    Turning off texture streaming seemed to help the most with stuttering, but it causes general protection fault crashes. Maybe it will be different in Linux.

    Unfortunately GC is still a major cause of stutters even after the 64 bit upgrade. Increasing the GC purge interval (TimeBetweenPurgingPendingKillObjects in Engine/BaseEngine.ini) to 90 seconds or even 75 causes horrible stutters of >100ms no matter how powerful the PC, so the stock 60 second interval is pretty much the sweet spot. The only somewhat viable alternative is to set a ridiculously large interval to bypass GC altogether, which will lead to performance degradation and eventually the game eating up all the RAM. This applies to both Linux and Windows.

     

    In my experience and with a high performance SSD (Plextor M10P) the effect of disabling disk cache is barely noticeable after the framerate has settled when all custom characters and cars are loaded. Nevertheless, I have been playing for 3+ weeks with disk cache enabled on Nobara (a Fedora 37 derivative) and didn't notice any negative impact from turning off disk cache.

     

    I also use a config with texture streaming disabled and I haven't noticed any crashes since I switched to Wine 8 (currently Wine 8.4 from Wine-tkg). Wine 7 and its derivatives like Proton-GE caused random crashes for me, which were more frequent in fullscreen mode as opposed to borderless.

     

    Here is a short video of how Asylum runs on my PC with my custom config, including disk cache disabled, texture streaming disabled and GC fully disabled:

    Note that I am using UI scaling because even though it's 1080p borderless, my monitor is rather small. I would also not recommend disabling GC completely, it can lead to the game freezing when exiting or changing districts.

    • Like 2

  18. Posted

    10 hours ago, Rade said:

    And if you really like messing about, create a ram disk for the AssetCache folder before you play the game. The example below links the AssetCache folder to RAM, essentially your AssetCache folder is a RAM drive and files are being written directly to your RAM, it has a size limit of 8GB, and will delete upon a system reboot or if you unmount it.

    Storing assets in RAM is a great idea, but now that the game has been upgraded to 64 bits I'd suggest using APB's built in RAM cache feature instead. That way Wine/Proton doesn't need to wrap any filesystem accesses.


    This is done via a config file edit, you can go to APBGame/Config/DefaultEngine.ini and change the line 

    m_bUseDiskCache=True

    by replacing "True" with "False". If you launch the game like this (and don't let the launcher overwrite this config), the AssetCache folder will be empty while playing.

    • Like 1

  19. Posted

    On 3/9/2023 at 10:16 PM, Sergsininia said:

    I've had to change the specific command to be 

    
~/.steam/steam/steamapps/common/Proton\ 7.0/Proton waitforexitandrun '/home/deck/.local/share/Steam/steam apps/common/APB Reloaded/Launcher/APBLauncher.exe' && ~/.steam/steam/steamapps/common/Proton\ 7.0/Proton waitforexitandrun '/home/deck/.local/share/Steam/steamapps/common/APB Reloaded/Binaries/APB.exe' -nosteam # %command%

    Using GE-Proton 49 I've had no issues in game.

    I'll have to do more testing because it shouldn't be necessary to manually specify Proton paths, let alone home folder paths like /home/deck.  When you use the command from my post, with or without configs, does nothing happen or do you get an error screen?

     

    Also, does "no issues in game" mean it's possible to have working in-game mail in Proton-GE? Do system mails lose their title and content when you select them?

    On 3/13/2023 at 6:12 PM, Rade said:

    This is very interesting. I'm running with an Intel Arc A770 LE and in Windows 11 APB runs very poor, one big stutter mess. Its almost impossible at times to kill anyone and thats with the current latest Arc drivers.

     

    I've just installed Ubuntu 22.04 LTS and compiled a 6.2 Linux Kernel (native Intel Arc support), will see how APB runs.

    I thought Intel implemented DXVK in their D3D9 performance upgrade for Windows, which is the same library used by Proton and Wine to translate DirectX9 to Vulkan. Given your experience with APB it's likely they did so on a per game basis and just forgot about poor old APB...

     

    Nice that you are seeing improved performance on Linux, after all modern GPUs are designed with Vulkan or DX12 in mind and not an old API like DX9. I was looking forward to someone testing this on Arc as I had already heard of its very poor native DirectX9 performance on Windows. 

     

    On another note I'm surprised you didn't run into issues due to old Mesa versions shipped by Ubuntu, their Arc support is not that great. I think it would make sense for you to either switch to a distribution that comes with gaming focused tweaks (and newer Mesa) out of the box such as PikaOS, or if you don't want to wipe your current install, upgrade your Mesa as shown in this guide.

  21. Posted · Edited by mojical

    2 hours ago, xHenryman90x said:

    What's the performance difference between Windows and Linux?

     

    Considering what I see what other people getting on streams, I'd say performance on Linux is at least as good as Windows. On my PC (i7 13700KF @ 5.5Ghz and AMD RX 6800) it stays on the 200fps cap I've set for the game, even in a full Asylum with shadows enabled. The reason why I've decided to cap it under my monitor's refresh rate is so that FreeSync works properly even when there are small stutters.

     

    1 hour ago, Frosi said:

    Very nice guide, I hope this helps people that use Linux / Steam deck and want to play, consider publishing it on steam too if you haven't.

     

    Also smh my head not using a steam skin

     

    I have uploaded the guide to Steam, although I think the steps described here are no rocket science and the game is really close to one-click compatibility as it is. Others have posted instructions on ProtonDB (the game's now Bronze rating instead of Borked!) and while they can help people who have tinkered with Proton for a while, some of the launch option commands need to be edited for different usernames or game install directories which isn't ideal.

     

    I don't use Steam to launch this game personally, or much at all lately, which is why I have not bothered to skin it. There is an Adwaita skin that makes it look like a native Linux app but it feels buggy and sluggish to use on my machine for some reason.

     

    Also, thanks for helping me forward crash logs to the devs, I played for a bit after the patch (2-3 hours, mostly FC) and it hasn't crashed since the patch, even on fullscreen mode instead of fullscreen window. I believe it was indeed related to the memory leak in 1.30's initial live build.

     

    1 hour ago, Sergsininia said:

    On Steam Deck, game still does not launch... I did use the GE Proton 49 instead of the linked custom GE Proton, are there any notable differences between the two?

     

    I believe I should change the guide to select Proton versions in the game's properties rather than altering global settings, as these can sometimes get overridden by default. Any Proton by GE should be fine, I don't think you need the custom version at all. Does the launcher not start or does the game not show after pressing start? If it's the latter, have you tried launching the game by pressing the X icon on the launcher to close it? It may be counter intuitive, but the launcher freezing when pressing Start is nothing new to me.

     

    42 minutes ago, NotZombieBiscuit said:

    What if I use mac tho

     

    You'd need to use a method different from Steam and find a Mac that has a GPU that is not too old, too weak or too restricted to Apple's proprietary APIs to run this game, which is a very difficult task if not impossible.

     

    37 minutes ago, Yeedman said:

    little orbit themselves have it available on https://gamersfirst.com/download so i'd think you're safe linking there

     

    Good point, I will edit that section to link to the official G1 site. I was convinced anything that couldn't be done in a text editor was in the grey area camp. However, there is still the issue of the launcher overwriting this file, so the %command%; at the beginning of the launch options would need to be deleted to bypass the launcher.

  22. Posted · Edited by mojical
    Added tweaks regarding FSR and anti stutter configs

    As a few of us Linux users have discovered in the 1.30 Open Beta thread, since APB’s 1.30 update it has been possible to successfully run APB:Reloaded on the Linux operating system, thanks to Little Orbit cleaning up old code that was causing crashes with previous versions.  This also applies to the Steam Deck.

     

    This is accomplished with a tool like Valve’s Proton that, to put it simply, translates APB’s DirectX9 API calls to Vulkan and Windows system calls to Linux equivalents in real time. The following guide shows how to accomplish this with a few minor tweaks, all within the Steam client.

     

    UPDATE 2023/12/17: Added some useful tweaks at the end of the guide to reduce stutters and improve visuals with FSR.

     

    How to play APB 1.30+ on Linux

     

    This guide was tested on CachyOS Linux with KDE 5.27 on both Wayland and X11, and an AMD RX 6800 GPU. 

     

    I have also tested it on a Steam Deck running latest stable SteamOS. It is necessary to do the following steps in desktop mode, however once you successfully run the game it will also work in gaming mode.

     

    For NVIDIA users: Make sure you are using proprietary drivers from this point on. If you need to install them, use your distribution's install method and do not use drivers downloaded from Nvidia's site.

     

    Step 1: Getting Proton-GE

     

    To proceed with the guide, Steam must be installed and started for the first time.

     

    Proton-GE is a community version of Valve's Proton containing up to date code and a collection of game specific fixes.  Proton-GE 8-5 supports APB Reloaded (including Steam login) without any additional tweaks.

     

    To install Proton-GE, the most user friendly option is to download ProtonUp-Qt from your distribution's Flatpak based app store, such as Discover in the Steam Deck's desktop mode. Then, from this tool, select "Add new version" and choose Proton-GE 8-5 or newer. This is not specific to APB so there are many guides on the Internet that help accomplish this task, such as this one. 

     

    Personally, my preferred way to install Proton-GE is to download the latest release and untar the folder within to  $HOME/.local/share/Steam/compatibilitytools.d/ ($HOME being a placeholder for your home directory).

     

    After Proton-GE is installed, Steam should be restarted to recognize it as a compatibility tool.

     

    Step 2: Setting up Steam

     

    Open Steam, log into your account, and open Steam's settings from the Steam menu. Navigate to "Compatibility" and check "Enable Steam Play for all other titles."

     

    jiCn2hz.png

     

    Go to your Library and make sure "Tools" or "All" is shown in the dropdown.  Use the search box to find the "Proton Easy AntiCheat Runtime". Install it if not already present.

     

    2SFcqOZ.png

     

     

    Step 3: Setting up APB

     

    Install APB Reloaded from Steam's store as usual. Be sure to not run the game yet until everything is set up.

     

    Once APB is installed, right click it from your library view and select "Properties" in the menu. Go to the "Compatibility" tab and select GE-Proton 8-5 or a later version of Proton GE, as shown below. If it does not show, verify that it is installed correctly and that you restarted Steam after installing it.

     

    fs2jlqR.png

     

    You can close the window or press Escape and your settings will be saved. The game is ready to be played at this point.

     

    Optional tweaks and improvements

     

    Using configs

     

    If you wish to use configs such as removing the login scene, you can create a directory called "apbconfig" in your home folder and inside it, paste your configs as you would in the game's install directory. For example, if you are using a graphics config, the path "/home/(your user)/apbconfig/APBGame/Config/APBCompat.ini" would be a valid path.  You can also insert command line arguments at the end such as -nomovies in the example.

     

    Then, paste the following script in the game's "Launch options". Do not use the APB Launcher's start button to start the game when using configs, start by closing the launcher instead. 

    %command%; yes | cp -rf "$HOME/apbconfig"/* "$STEAM_COMPAT_INSTALL_PATH"/; $HOME/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=113400 -- $HOME/.local/share/Steam/ubuntu12_32/steam-launch-wrapper -- $HOME/.local/share/Steam/steamapps/common/SteamLinuxRuntime_sniper/_v2-entry-point --verb=waitforexitandrun -- "${STEAM_COMPAT_TOOL_PATHS%%:*}"/proton waitforexitandrun "$STEAM_COMPAT_INSTALL_PATH/Binaries/APB.exe" -nomovies -nosteam

     

    All in all, as a now single-boot Linux user I consider the release of 1.30 a great step forward to APB since compatibility went from zero to essentially fully playable just by cleaning up APB’s aged codebase. Hopefully, this compatibility will be preserved or even improved upon in future releases of this game. Also, looking forward to hear from more players who attempted this or a similar method to run APB on their Linux machine!

     

    Reducing DXVK stutters

     

    DXVK (the translation layer used to "translate" APB from DX9 to Vulkan in real time) has configurable options that are well suited to APB's odd way of managing memory. 

     

    https://drive.google.com/file/d/1RTNG4MVHirz6fbFBusurOGDJyD_pqm2M/view?usp=sharing

     

    By copying this dxvk.conf file into your Binaries folder within the game's install directory you can enable these and a few other performance enhancing options that don't have an impact on graphics or stabilty according to my tests. This is especially true for nVidia users. The file has to be in the same folder as the APB.exe binary!

     

    For those already versed in editing dxvk.conf the options in question are:

    d3d9.apitraceMode = True

    d3d9.cachedDynamicBuffers = True

     

    Note that the ApiTrace option isn't used for api tracing in this case, we are just interested in cached and coherent buffers.

     

    You can test the impact of these options by shooting a vehicle with a fast-firing weapon. This should cause noticeable frametime spikes without the config which are much less noticeable after applying it.

     

    Using AMD FSR

     

    As with many recent games, we can use AMD FSR to upscale the game from a lower internal resolution, resulting in much higher visual quality than regular display or GPU scaling. This is especially useful if you need a larger UI and don't want to deal with the visual corruption that's caused by the "User interface size" in the game's options.

     

    This requires a recent Proton-GE version (I recommend Proton-GE 8-25, the latest as of this edit)

     

    Add the following variable to your launch options (either alone or before whatever options you were already using, don't forget the space after though):

      

    WINE_FULLSCREEN_FSR=1

    Then start the game, select "Fullscreen" in the graphics options and choose the internal resolution you prefer. FSR will add some oddball resolutions that function especially well with this scaling method. If it is done properly the UI text should be rendering with native-like quality. This works for both AMD and nVidia GPUs. 

    • Like 10
    • Thanks 8

  23. Posted · Edited by mojical
    wording

    2 hours ago, gogeo said:

    Now that 1.3 is Live, are you able to play it through steam on linux? I can't get it to work right now, launcher opens, updates and installs directx etc but when I click play it just closes and steam reports it closed as well.

    That's an issue with APBLauncher on Linux, the solution is usually to set separate entries for the launcher and game until a root cause for this is found.

     

    If you want to modify APB on Steam so that it starts the game directly bypassing the launcher (and the bug I mentioned), type this into your launch options on "Properties": 

    $(echo %command% | sed -r "s/proton waitforexitandrun .*/proton waitforexitandrun/") "$STEAM_COMPAT_INSTALL_PATH/Binaries/APB.exe"  -nosteam

    I still recommend using Bottles or SteamTinkerLaunch instead, since Steam integration is still broken (hence -nosteam above).

    • Like 1

  24. Posted

    1 hour ago, Tajmoti said:

    I was pleasantly surprised by the ability to run APB on Linux (including the Steam Deck), but my joy seems to have been premature. After downloading the new OTW - Valentine's update, I am now getting kicked by BattleEye immediately after entering a district with the message "Unsupported platform". I hope disabling this restriction is a simple change, and you guys are going to do it. Pretty please!

    https://store.steampowered.com/news/group/4145017/view/3104663180636096966

     

    I cannot reproduce this problem, it seems to be an issue with BE compatibility on your end. For me the combination of Bottles and Proton-GE still works on the current patch.

    • Like 1

  25. Posted

    2 hours ago, gogeo said:

    I installed it today on Nobara, rtx 3060 ti. Ran the setup through lutris, installed no issues and was able to run APB.exe with Wine GE 36. Didn't have to install anything else, it worked, played smoothly for an hour. Didn't see any issues other than all mail showing as "system mail"

    System mail issue happens too, will have to see if there are some more missing dependencies that could be causing it. Weirdly enough the title shows up correctly for a second then changes to "system mail", but the items can be redeemed correctly. It's just difficult to know which mail is which.

     

    I'm glad it worked fine on Nvidia as well. How was your performance in terms of FPS?

×
×
  • Create New...