Arma Reforger (1874880)

[IcedEagle]

Compatibility Report

• Name of the game with compatibility issues: Arma Reforger
• Steam AppID of the game: 1874880/

System Information

• GPU: Nvidia GeForce RTX 3080 Ti
• Driver/LLVM version: Nvidia 510.68.02
• Kernel version: 5.17.7
• Link to full system information report as Gist: https://gist.github.com/IcedEagle/e455885ba62ca3af39c1454a2067f37c
• Proton version: Experimental, Experimental [bleeding-edge], and Proton 7.0

I confirm:

• [x] that I haven't found an existing compatibility report for this game.
• [x] that I have checked whether there are updates for my system available.

steam-1874880.log steam-1874880.log

(Also as a gist) https://gist.github.com/IcedEagle/e389408b526e543b42d4ddd955f0d86c

Symptoms

Game fails to launch. You click Play, and a few seconds later it acts like it wasn't launched. Presumably BattleEye related. I do have Proton BattleEye Runtime installed.

Reproduction

Launch game.

[DomiStyle]

Another bug (if you can join a server) is that the map is transparent/invisible for some reason. Haven't seen anybody else mention this issue yet so probably Proton only.

[Blisto91]

Do you experience that issue @DomiStyle ?

Can you post a proton log.

[DomiStyle]

@Blisto91 Yes, map was invisible except the icons. Unfortunately I already refunded so I can't post the Proton logs anymore.

[Baguettedood]

To open the game: The launch command echo "%command%" | sed 's/ArmaReforger_BE.exe/ArmaReforgerSteam.exe/' | sh will open the game, or you can rename ArmaReforgerSteam.exe to ArmaReforger_BE.exe, backing up the original.

Make sure the Proton BattlEye Runtime is installed in the Tools section of Steam, in order to join servers.

More info: According to Dedmen on the Arma Discord, they have enabled Proton support for BattlEye. You may need to ensure you have installed the Proton BattlEye Runtime, because as of writing, it is not listed as an additional dependency for Reforger like it is for other titles using BattlEye, such as Arma 3. I'm not sure who's responsible for actually setting the additional dependencies. With the Proton BattlEye Runtime installed, you should be able to join servers.

As for why launching the game normally (using ArmaReforger_BE.exe) causes crashes, I'd guess it's doing something that Proton doesn't like. A Proton log might provide insight but I don't actually own the game to check.

[SOlsson91]

Here is a log from just now, Cleaned out pfx and verified the files before i ran. I do have Proton BE installed Also have not changed ArmaReforger_BE.exe to ArmaReforgerSteam.exe

Game just sits for a few seconds then turns off. Not really sure how to read the logs so thought I'll just put it here for someone that might now how to.

My system OS: Arch Linux Kernel: x86_64 Linux 5.18.0-arch1-1 WM: bspwm CPU: AMD Ryzen 9 5900X 12-Core @ 24x 3.7GHz GPU: AMD Radeon RX 6800 XT (sienna_cichlid, LLVM 13.0.1, DRM 3.46, 5.18.0-arch1-1)

steam-1874880.log

[Blisto91]

@SOlsson91 Just as a quick test does it change anything if you don't launch with mangohud and or gamemode

[SOlsson91]

@Blisto91 Here is a log with just PROTON_LOG=1 %command%

steam-1874880.log

[veikolippand]

I have same issue. I can run only with ArmaReforgerSteam.exe but can not stay in on any server, few seconds and out i go. ArmaReforger_BE.exe is not starting. Proton (7) Experimental.

Debian 11 bspwm NVIDIA GeForce RTX 2060 Intel i5-6400

[Baguettedood]

@veikolippand Have you made sure to install the Proton BattlEye Runtime in the Tools section of Steam?

[veikolippand]

yes i have Proton BattlEye installed.

[veikolippand]

I believe Arma3 is using same Proton BattlEye and Arma3 is running fine.

[Baguettedood]

Might just be a game-specific issue. Even many Windows players are reporting getting disconnected due to an "Internal error" about 30 seconds after joining a server.

[veikolippand]

Yes i have seen complaints about disconnecting and this can be server or whatever reason. Actually what i am worried about is that the ArmaReforger_BE.exe is not starting and this is an issue. And don't know what is the reason or where is it Arma or proton.

[imaami]

Anti cheat appears to be working since approximately 2 weeks ago. I have been able to play on every multiplayer server I've tried. I've so far only tried with GE-Proton7 so I can't speak for upstream Proton.

Would those who own this game please try multiplayer and report back?

[veikolippand]

Tried and yes it looks ok with battleye. I have Proton experimental and did not experienced any connectivity issues. But I still have graphics issues with hardware anti-aliasing when set in game settings. I can not use any multiplier. Have not seen any other user with this issue so i might have faulty setup. I have latest drivers installed but for some reason game is not able to render correct video when hardware anti-alias set.

[imaami]

Tried and yes it looks ok with battleye. I have Proton experimental and did not experienced any connectivity issues. But I still have graphics issues with hardware anti-aliasing when set in game settings. I can not use any multiplier. Have not seen any other user with this issue so i might have faulty setup. I have latest drivers installed but for some reason game is not able to render correct video when hardware anti-alias set.

Good to hear that upstream Proton Experimental works too.

I can't remember my hw anti-aliasing setting right now, but I have one persistent glitch too: the map view is black. I mean only the icons appear, no map image. And the icons leave tracers when the map is moved.

[imaami]

About the map glitch I mentioned earlier: I checked my settings and hardware anti-aliasing was enabled. After disabling it the map works fine.

With this I can say there are no bugs I know of left. Arma ReForger works in Proton 100%.

[veikolippand]

Game works with lower quality settings i would say. I don't know is it something to do with proton + linux or is it something in game. My hardware is Nvidia RTX 2060 (NVIDIA Driver Version: 515.65.01)

I added some screens to show how I see it with hardware anti-aliasing set to 2x and 4x. Maybe somebody can comment or have any idea what might cause it.

    

[Blisto91]

@veikolippand Hi there. Would you be able to post a proton log? 🙂

[veikolippand]

steam-1874880.log

[her001]

Between Arma Reforger and Arma Reforger Experimental, I have over 90 hours in the game. For the most part, things seem to "just work" with Proton.

However, I noticed that if I go to a particular spot, I can consistently cause a GPU reset with amdgpu (regardless of RADV or amdvlk).

How to reproduce

Start a new Game Master session on Arland and navigate to grid 024027, into the bush just east of the road, past the bridge (about where my cursor is below):

When moving into position, I always get GPU resets right about here:

Being anywhere else, I do not get these GPU resets (that I've seen so far).

Permutations I tried

At first I thought this was a regression in the kernel, as I had recently upgraded, but I can reproduce this with various versions (including zen-kernel 6.0.9, 6.0.12, and 6.1.1, and Linux 5.15 and 6.1.1). I can also reproduce this with Mesa 22.2.3, 22.3.1, and amdvlk 2022.Q4.4.

In game, this happens in any game mode or when controlling anything (like the game master camera or when playing as a soldier). My settings are at the low preset.

Extra info

Relevant dmesg lines:

[  164.939941] amdgpu 0000:35:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32778, for process enfMain pid 3382 thread enfMain pid 3395)
[  164.939946] amdgpu 0000:35:00.0: amdgpu:   in page starting at address 0x0000800229501000 from IH client 0x1b (UTCL2)
[  164.939950] amdgpu 0000:35:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00601030
[  164.939951] amdgpu 0000:35:00.0: amdgpu:      Faulty UTCL2 client ID: TCP (0x8)
[  164.939951] amdgpu 0000:35:00.0: amdgpu:      MORE_FAULTS: 0x0
[  164.939952] amdgpu 0000:35:00.0: amdgpu:      WALKER_ERROR: 0x0
[  164.939952] amdgpu 0000:35:00.0: amdgpu:      PERMISSION_FAULTS: 0x3
[  164.939953] amdgpu 0000:35:00.0: amdgpu:      MAPPING_ERROR: 0x0
[  164.939953] amdgpu 0000:35:00.0: amdgpu:      RW: 0x0
[  174.964447] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered
[  174.980632] amdgpu 0000:35:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32778, for process enfMain pid 3382 thread enfMain pid 3395)
[  174.980635] amdgpu 0000:35:00.0: amdgpu:   in page starting at address 0x0000800258fa1000 from IH client 0x1b (UTCL2)
[  174.980640] amdgpu 0000:35:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00601030
[  174.980641] amdgpu 0000:35:00.0: amdgpu:      Faulty UTCL2 client ID: TCP (0x8)
[  174.980641] amdgpu 0000:35:00.0: amdgpu:      MORE_FAULTS: 0x0
[  174.980642] amdgpu 0000:35:00.0: amdgpu:      WALKER_ERROR: 0x0
[  174.980642] amdgpu 0000:35:00.0: amdgpu:      PERMISSION_FAULTS: 0x3
[  174.980643] amdgpu 0000:35:00.0: amdgpu:      MAPPING_ERROR: 0x0
[  174.980643] amdgpu 0000:35:00.0: amdgpu:      RW: 0x0
[  185.204921] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered

While I can't attach it here, I can also share the renderdoc frame captured between GPU resets, if it would be useful.

[her001]

Adding to my last comment: my original testing was on my desktop with a Vega 56. I am able to reproduce this behavior on my Steam Deck.

[hakzsam]

@her001 Would you be able to try recording a gfxreconstruct trace of the issue, please?

[her001]

Hey, sorry for the very late replay. I've found that I can no longer reproduce the freeze on my desktop, so I'm guessing it was fixed. I can try again on my Steam Deck to see if it still happens there. I'll report back with the trace if it doesn't work.

[her001]

I just confirmed that this GPU reset no longer happens on the Steam Deck for me.

[Reidond]

I have constant game freezes to the point that game crashes, do proton logs will be sufficient? I have crashes on windows pc, but on steam deck they have a patern: when 20 minutes in game on full server and server fps is 20-30, game freezes to the point that steam deck because unresponsive until restarted.

[Reidond]

I have a regression or something like this, character textures are not loading and are just black color and map (when pressing M) is not loading it's just black.

Game: 1.0.0.59 Proton: 8.0-4 steam-1874880.log

[Reidond]

I have a regression or something like this, character textures are not loading and are just black color and map (when pressing M) is not loading it's just black.

Game: 1.0.0.59 Proton: 8.0-4 steam-1874880.log

I found out that this is because of hardware anti-aliasing.

glxinfo:

```sh name of display: :0 display: :0 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: AMD (0x1002) Device: AMD Radeon RX 6700 XT (navi22, LLVM 16.0.6, DRM 3.54, 6.6.2-201.fc39.x86_64) (0x73df) Version: 23.2.1 Accelerated: yes Video memory: 12288MB Unified memory: no Preferred profile: core (0x1) Max core profile version: 4.6 Max compat profile version: 4.6 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 Memory info (GL_ATI_meminfo): VBO free memory - total: 8115 MB, largest block: 8115 MB VBO free aux. memory - total: 31486 MB, largest block: 31486 MB Texture free memory - total: 8115 MB, largest block: 8115 MB Texture free aux. memory - total: 31486 MB, largest block: 31486 MB Renderbuffer free memory - total: 8115 MB, largest block: 8115 MB Renderbuffer free aux. memory - total: 31486 MB, largest block: 31486 MB Memory info (GL_NVX_gpu_memory_info): Dedicated video memory: 12288 MB Total available memory: 44392 MB Currently available dedicated video memory: 8115 MB OpenGL vendor string: AMD OpenGL renderer string: AMD Radeon RX 6700 XT (navi22, LLVM 16.0.6, DRM 3.54, 6.6.2-201.fc39.x86_64) OpenGL core profile version string: 4.6 (Core Profile) Mesa 23.2.1 OpenGL core profile shading language version string: 4.60 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL version string: 4.6 (Compatibility Profile) Mesa 23.2.1 OpenGL shading language version string: 4.60 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL ES profile version string: OpenGL ES 3.2 Mesa 23.2.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 ```

[runar-work]

Thanks for the info about the settings. I was able to reproduce the glitch with an RX 7600 and Mesa 23.2.1 as well as the most recent (the older ones I tried ran into the GPU hang mentioned earlier). I was able to narrow it down to a specific texture, at least. RenderDoc capture

[Aftermath]

Yeah, its quite the interesting combination of glitches for this game. I'm running a 7900 XTX with mesa 23.2.1 (w/proton experimental -> bleeding edge), Contact shadows cause the black skin issues (flipping the option around / off causes this to resolve itself), HW AA causes artifacting against skins. Turning both of these off seems to prevent that particular set of issues. Haven't found any combination of settings thus far to prevent the textures from forcibly reverting to playdoh, or not loading at all for inventory items (which really hurts the gameplay) - nor a way to prevent the random object dissappearings such as buildings or bridges. First load of textures in game also takes a rather long time. (with some random tinking, it seems that the higher the level of texture filtering active, the lower quality and slower loading textures/models are.)

[Reidond]

Haven't found any combination of settings thus far to prevent the textures from forcibly reverting to playdoh, or not loading at all for inventory items (which really hurts the gameplay) - nor a way to prevent the random object dissappearings such as buildings or bridges. First load of textures in game also takes a rather long time. (with some random tinking, it seems that the higher the level of texture filtering active, the lower quality and slower loading textures/models are.)

this happens when running on windows 11 too

[KovSandor]

The Hardware anti-aliasing setting is broken with NVIDIA drivers (using RTX 3060 Ti) as well. If it's not turned off the textures just float next to the models.

My system: Proton version: 8.0-5 & Proton Experimental Game version: 1.0.0.95 NVIDIA driver: 545.29.06 Kernel version: 6.7.4-200.fc39.x86_64

[nexpspace]

Almost everything works for me, too. Except that the map is transparent. Like @imaami mentioned disabling hardware anti-aliasing works around the map issue.

Game version: 1.1.0.42 Proton: Proton Experimental GPU: Radeon RX 6900 XT mesa: 24.0.4 Kernel: 6.8.7-gentoo

[kit-the-cat-skelanimal-plush]

Apologies if I'm posting this in the wrong place, haven't used Github before. I have been experiencing a very bizarre issue in Arma Reforger for quite a while now where the foliage will sometimes completely bug out if I'm at or around 100% GPU usage. This does not happen every time I play, and sometimes switching Proton versions will temporarily fix it, but after a couple days it shows up again. It also sometimes fixes itself for a bit without my input, but always reverts to being broken. Here's a video I took of it happening. My subtitles can be ignored, I thought at first that framerate was what caused it.

https://youtu.be/RdhsNIctri8?si=TmGDq_GIpmbA9dIG

GPU: Nvidia RTX 3060 Ti Driver: Nvidia 535 (happens on 545 as well, haven't tested any others) Kernel: 6.5.0, also happens on all other kernel versions I've tried Proton: Experimental, happens on all versions I've tried Game version: 1.1.0.42, once again has happened on all other game versions I've played

[BamsTheSergal]

i am having the exact same issue, with a 2070, and gpu driver version 550.

[1player]

Very annoying is the fact that textures and models load at glacial pace, even with an NVMe. On some maps it might take a couple of minutes after spawning in before everything is loaded.

[NickDeBeenSAE]

The game refuses to launch on any and all the latest custom, and official compatibility layers for me unless I moved the install directory to an EXT4 drive.

I have tried Proton9-10, 9-11, 6.3-8, Experimental versions of it, and 2 custom versions of it, 1 being GE-Proton9-11, and the other being TKG-proton-experimental.bleeding.edge.9.0.109273.20240725, all of them, the game does not launch after loading into a server, the game hard crashes the entire system.

My full-AMD build is affected by this bug.

CPU: AMD Ryzen 9 5950X

GPU: AMD RX 6700 XT 12GB

[NickDeBeenSAE]

I then realised where I had Reforger installed and it was in the main drive.

[NickDeBeenSAE]

The game still hard crashes on my system:

Ryzen 9 5950X and RX 6700 XT 12gb on Mesa 24.2.

[NickDeBeenSAE]

I just swapped my GPU because not even a System Update fixed this issue.

The game clearly isn't compatible with AMD GPUs and drivers.

[1player]

Doesn't crash on my 6800 XT so the problem clearly is on your machine.

On Thu, 5 Sep 2024, at 15:06, Nick De Been wrote:

I just swapped my GPU because not even a System Update fixed this issue.

The game clearly isn't compatible with AMD GPUs and drivers.

— Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/5847#issuecomment-2331778227, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFIPSCCESZ4B33ZY2BMJT3ZVBQOZAVCNFSM5WHFHGB2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMZTGE3TOOBSGI3Q. You are receiving this because you commented.Message ID: @.***>

[NickDeBeenSAE]

No its not.

[NickDeBeenSAE]

Doesn't crash on my 6800 XT so the problem clearly is on your machine. … On Thu, 5 Sep 2024, at 15:06, Nick De Been wrote: I just swapped my GPU because not even a System Update fixed this issue. The game clearly isn't compatible with AMD GPUs and drivers. — Reply to this email directly, view it on GitHub <#5847 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFIPSCCESZ4B33ZY2BMJT3ZVBQOZAVCNFSM5WHFHGB2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMZTGE3TOOBSGI3Q. You are receiving this because you commented.Message ID: @.***>

How is it an issue with my System, wherein its perfectly fine playing Arma 3?

[NickDeBeenSAE]

Again, its not my PC, its Mesa, and AMD not applying updates correctly.