Game launches and runs fine here, at least during the first mission.

~However, I'm having issues getting the game to use my Dualsense controller (Flatpak Steam). Tried fiddling a bit with Steam input but no luck so far.~ Fixed by using gamescope.

From Easy Anti-cheat window:
"Launch Error"
"Unexpected error. (#1)"

This system uses the same game install folder for 2 (two) users. However each user has its own game-running-software in the $HOME directories--Easy Anti-cheat; Proton; runtime_sniper/solder, etc.

Running Steam from console show no permission errors (anymore).

steam-1888160.log

1633.789:0028:002c:warn:seh:check_bpf_jit_enable Could not open /proc/sys/net/core/bpf_jit_enable.
1635.257:0128:0170:err:kerberos:kerberos_LsaApInitializePackage no Kerberos support, expect problems
1635.262:0128:0170:err:ntlm:ntlm_LsaApInitializePackage no NTLM support, expect problems

I played the first 10-11 mission. But my game seems to freeze when I fight Balteus. Does anybody else got this issue?
Found my issue. It seems that resizable bar made the game freeze on this fight. This is not the first game causing issues with rezisable bar on my system. So I don't think it's Armored core related.

NVIDIA 3070 RTX
AMD RYZEN 3700X
NVIDIA 535.104.05

Game also crashes for me a few seconds into the Balteus fight in the Watchpoint level. This is a few hours in and 100% repeatable.

Aug 24 23:59:59 torrent kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=84250579, emitted seq=84250581
Aug 24 23:59:59 torrent kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process armoredcore6.ex pid 44352 thread armoredcore6.ex pid 44352
Aug 24 23:59:59 torrent kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset begin!
Aug 24 23:59:59 torrent kernel: amdgpu 0000:03:00.0: amdgpu: BACO reset
Aug 25 00:00:01 torrent kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset succeeded, trying to resume
Aug 25 00:00:01 torrent kernel: [drm] PCIE GART of 512M enabled (table at 0x00000081FEE00000).
Aug 25 00:00:01 torrent kernel: [drm] VRAM is lost due to GPU reset!
Aug 25 00:00:01 torrent kernel: [drm] PSP is resuming...
Aug 25 00:00:01 torrent 
kernel: [drm] reserve 0x900000 from 0x81fd000000 for PSP TMR

GPU crashes then recovers but takes X with it in the process.

steam_info.txt

Guess I'll have to try disabling resizable BAR.

Edit: Disabling resizable BAR did not help.

@brandonegbert are you to provide a save game if they are sharable? 👀

Reproducing this is going to be a nightmare if we cannot share saves. I'm seriously struggling getting past the tutorial boss ...

Not having any problems with my 5900X+6700XT yet, besides lower performance than I would have expected.

But while experimenting with WINE_CPU_TOPOLOGY I managed to get the game to crash as it launches after the EAC popup.
WINE_CPU_TOPOLOGY=12:0,1,2,3,4,5,12,13,14,15,16,17 to contain the game to the first CCD crashes every time. steam-1888160.log
WINE_CPU_TOPOLOGY=12:0,1,2,3,4,5,6,7,8,9,10,11 for just physical threads of both CCDs works.

The game that lead to me finding out about WINE_CPU_TOPOLOGY, Mechwarrior Online, doesn't crash with the first option.

I got past the boss and grinding through the (trivial) missions ...

I'm stuck at "[Press Any Button]"
Disregard, I guess. Maybe I wasn't giving it enough time to compile shaders or something. It seems to work fine now.

My game was running completely fine for 4 hours, but that was until I got to the boss: "AA P07 Balteus". The game keeps crashing when he does a flamethrower spinning attack, it's the second move he does upon entering combat. I've crashed at the same point 6 times now, I've tried different Proton versions like 7.0-6, 8.0-3 and experimental.

Also getting the Watchpoint/Baltheus crash. Both on Proton 8 and bleeding-edge. The annoying part is it happens on the end boss of a lengthy level and you have to start it over every time it crashes. Will continue testing.

• Nobara 38, kernel 6.4.10
• 4070 Ti, driver 535.104.05

Saves are too big to upload here and don't compress at all, so here a link: https://drive.google.com/file/d/1HJ5uHyvlOEP7mtbbAofGBeee6ycounn6/view?usp=sharing
Saves are found in (guessing the numbers folder might have different numbers): pfx/drive_c/users/steamuser/AppData/Roaming/ArmoredCore6/76561197967793517/

steam-1888160.zip

Looks like @frozen-sea got you a save game but if you need another I can get one uploaded tonight.

On a hunch, I started by trying it in offline mode without the anti-cheat. Was able to make multiple attempts lasting several minutes each (even got him to below 50% once!) at the boss in question without crashing, where as previously it would crash within like 30 seconds.

Launch option: eval $(echo "%command%" | sed "s/start_protected_game.exe/armoredcore6.exe/")

Adding log of that session for good measure.
steam-1888160-nocrash.zip

Edit: I then un-did the workaround and can no longer reproduce it on Proton 8 with no launch options... Literally nothing else has changed, not even rebooted.

For anyone that has it working: are you on RDNA3 at all?

I'm having the same issue

Arch, kernel 6.4.12, nvidia 535.104.05, proton 8.0-3/bleeding-edge, Hybrid and dedicated graphics tested.
System: Intel i5 12500H, RTX 3050 mobile and 16 GB of ram.

I've already tested a variety of graphics combinations, but with no luck.

Edit: I forgot to mention the issue only occurs at the start of the chapter 1 last boss as it was mentioned in another comment. But to add: I could reproduce the freeze as well on the Strider mission setting the graphics settings to low (from normal or high) for some reason.

I cannot reproduce any hang on RX 7600. Finally got to the boss after playing this all day <_<

I can reproduce it on 5700xt however.

Steam Overlay doesn't work. I had this problem also on Elden Ring. idk If that has something to do with that, but the Easy Anti Cheat slpash screen has the Steam Overlay.

Couldn't beat it but I got Balteus to about 25% left on the second phase without a crash of any sort. That super assault armor attack of it tanks my fps to 30 every time, though...
Still 6700XT.

Tried @frozen-sea solution of disabling EAC, but unfortunately it doesn't do the trick for me - game still crashes at around boss's second salvo, never experienced a crash before this mission.

Using Nvidia RTX 1650 Mobile (535.98), with AMD Ryzen 5 4600H on Arch Linux 6.4.11-arch1-1.

Tried disabling EAC, tried some other suggestions including: reducing graphics fidelity and disabling auto-adjust but I also kept crashing on the first salvo of Balteus.

My only solution was to get AC6 on my Steam Deck and then beat the boss from there.

Now I have a 100% reproducible error on the mission immediately afterwards. Where 'restart from checkpoint' will cause my system to crash on the fight with 'The Cleaner.'

Finally root caused it. It's a game bug.

It crashes in a shader which samples a texture, but there's actually a uniform buffer there, which causes GPU crash:

============
Fault type: MISMATCH_DESCRIPTOR_TYPE
CBV_SRV_UAV heap cookie: 7
Shader hash and instruction: b8140dcf1aa2320a (1)
Accessed resource/view cookie: 9
Shader desired descriptor type: 1 (SAMPLED_IMAGE)
Found descriptor type in heap: 4 (UNIFORM_BUFFER)
Failed heap index: 10336
==========
0298:err:vkd3d_descriptor_debug_qa_check_entry: Num failed checks: 212
0298:err:vkd3d_descriptor_debug_qa_check_report_fault: 
============
Fault type: MISMATCH_DESCRIPTOR_TYPE
CBV_SRV_UAV heap cookie: 7
Shader hash and instruction: b8140dcf1aa2320a (1)
Accessed resource/view cookie: 9
Shader desired descriptor type: 1 (SAMPLED_IMAGE)
Found descriptor type in heap: 4 (UNIFORM_BUFFER)
Failed heap index: 24823
==========
0298:err:vkd3d_descriptor_debug_qa_check_entry: Num failed checks: 212
0298:err:vkd3d_descriptor_debug_qa_check_report_fault: 
============
Fault type: MISMATCH_DESCRIPTOR_TYPE
CBV_SRV_UAV heap cookie: 7
Shader hash and instruction: 8450c12e29bda693 (8)
Accessed resource/view cookie: 9
Shader desired descriptor type: 1 (SAMPLED_IMAGE)
Found descriptor type in heap: 4 (UNIFORM_BUFFER)
Failed heap index: 1521
==========
0298:err:vkd3d_descriptor_debug_qa_check_entry: Num failed checks: 905
0298:err:vkd3d_descriptor_debug_qa_check_report_fault: 
============
Fault type: MISMATCH_DESCRIPTOR_TYPE
CBV_SRV_UAV heap cookie: 7
Shader hash and instruction: 8450c12e29bda693 (8)
Accessed resource/view cookie: 9
Shader desired descriptor type: 1 (SAMPLED_IMAGE)
Found descriptor type in heap: 4 (UNIFORM_BUFFER)
Failed heap index: 5745
==========

Using descriptor QA also masks the bug since invalid access will be turned into a NULL descriptor.

How did you manage to start it at all? My easy anti cheat launcher just is stuck "Initializing" indefinitely.
nvidia 3090 on ubuntu 22.04

https://discord.com/channels/481706387278397440/1144637082799710280/1144742374623416380

There's a handful of reports of similar crashes at the start of the Balteus fight on Windows in this thread: https://steamcommunity.com/app/1888160/discussions/0/3820795131605892308/
And this one: https://steamcommunity.com/app/1888160/discussions/1/3820795131608400290/

May not be isolated to Linux.

There's a handful of reports of similar crashes at the start of the Balteus fight on Windows in this thread: https://steamcommunity.com/app/1888160/discussions/0/3820795131605892308/
And this one: https://steamcommunity.com/app/1888160/discussions/1/3820795131608400290/

May not be isolated to Linux.

With this, the threads got cross-referenced. I wonder if there could be a proton workaround for the problem or if this can only be fixed by the developers. I really appreciate the finding, and I wonder how we could report this to Bandai to get this fixed asap.

Finally root caused it. It's a game bug.

It crashes in a shader which samples a texture, but there's actually a uniform buffer there, which causes GPU crash:

Create a new mesa issue and request a workaround:
https://gitlab.freedesktop.org/mesa/mesa/-/issues

GiGurra did you try @frozen-sea launch option? That workaround gets the game to start on my machine: eval $(echo "%command%" | sed "s/start_protected_game.exe/armoredcore6.exe/")

Timon was having a similar EAC launch issue on windows:
https://steamcommunity.com/app/1888160/discussions/0/3820795131605739862/?ctp=3#c3820795131606924426

Timons windows solution:

1. Go to Library > right click > manage > browse local game files
2. Go to the Game folder and find start_protected_game.exe
3. Right click the app, Properties > Compatibility > Change Settings for All Users > Run this program as administrator
4. Do the same for armoredcore6.exe, and the game should finally load.

However, I read that wine by default runs programs with administrator previlages. Does someone know how to confirm administrator previlages for start_protected_game.exe and armoredcore6.exe running in Proton?

I was finally able to finish Balteus without crashing - in offline mode without the anti-cheat by using @frozen-sea launch option:

eval $(echo "%command%" | sed "s/start_protected_game.exe/armoredcore6.exe/")

Replying to https://github.com/ValveSoftware/Proton/issues/7045#issuecomment-1694143730

I did try running the armoredcore6.exe instead of the eac launcher, like was suggested here, but that only launches, turns into a black screen with game cursor, and then 1 second later closes.

I am currently still running into the issue of starting up the game I get a white screen for about 4 seconds with a curious that I can see and moves when it goes to black my cursor is gone and the game crashes anyone any advice I tried everything in these guides

https://www.ghostarrow.com/armored-core-6-crashing-not-launching-white-black-screen-fix
https://updatecrazy.com/armored-core-6-wont-launch-black-screen-easy-fix/
https://digistatement.com/armored-core-6-ac6-fires-of-rubicon-black-screen-issue-is-there-any-fix-yet/
https://www.reddit.com/r/armoredcore/comments/160gcs1/black_screen_on_startup/

Replying to [#7045 (comment)](https://github.com/ValveSoftware/Proton/issues/7045#issuecomment-1694143730)

I did try running the armoredcore6.exe instead of the eac launcher, like was suggested here, but that only launches, turns into a black screen with game cursor, and then 1 second later closes.

If I try to add extra commands to the eval part e.g. gamemoderun mangohud %command% - game crashes either with white or black screen. Removing gamemoderun and using only mangohud %command% does work for me, tho.

I was finally able to finish Balteus without crashing - in offline mode without the anti-cheat by using @frozen-sea launch option:

eval $(echo "%command%" | sed "s/start_protected_game.exe/armoredcore6.exe/")

@Cyber-Oto what is the windows equivalent for this, is it just running in administrator mode?
if i try launching one in administrator mode, how can i be assured the other exe will as well, even if i set the compatibility setting to administrator mode permanently?

I was finally able to finish Balteus without crashing - in offline mode without the anti-cheat by using @frozen-sea launch option:
eval $(echo "%command%" | sed "s/start_protected_game.exe/armoredcore6.exe/")

@Cyber-Oto what is the windows equivalent for this, is it just running in administrator mode? if i try launching one in administrator mode, how can i be assured the other exe will as well, even if i set the compatibility setting to administrator mode permanently?

@aram909 What this command does is telling Steam to use armoredcore6.exe instead of start_protected_game.exe.

I couldn't really find any suitable one-liner for Windows, so even though there should be one, what I can advice is to just paste there your full path to the .exe, something like this.

"C:\Program Files (x86)\Steam\steamapps\common\ARMORED CORE VI FIRES OF RUBICON\Game\armoredcore6.exe" %command%

It will try to use that .exe directly. I believe you must keep %command%, or Steam will ignore your custom command altogether. Just make sure that path is adapted to your setup and points to armoredcore6.exe on your machine.

Not sure about setting administrator mode, you can try to set if it doesn't work. A sign that it worked will be that game stars without EAC popup and uses offline mode.

Also, I should point out that it is not guaranteed to fix Balteus crash, unfortunately, since it worked for some and didn't for another, like me.

yeah EAC kept popping up

do I put it into the alternate launch options for steam, like so?

or directly into the terminal/cmd prompt?

@aram909 Yes, directly there in Launch options, make sure that you have set your actual path to the file and kept all double quotes with %command%, i.e. "FULL_PATH_TO_EXE" %command% otherwise it won't work. If all is correct and it still won't work, not sure if I can help further, since I use Linux without dual-boot to Windows to check.

%command% Isn't a thing in Windows Steam. Unless they added it with the GUI update.

This seems to launch fine straight out of the box and works fine with keyboard and mouse but not with my ps4 controller or xbox controller when they work in all other games ok.

Symptoms

On starting the game, it crashes after briefly loading. I expect a pre-rendered video is the issue, but no versions of Proton I've tried including GE seem to get it working past the menu screen on my end.

Reproduction

* Open the game.

* Click New Game or Continue.

* It crashes.

It seems that Steam's preload may have been the root cause of my problems regarding EAC and the game not letting me play.

After verifying the files, the game patched ~35GB and downloaded ~800MB and EAC now seems to allow me to log in. I can also now actually get past the first loading screen.

is there any confirmed fix to the crashes on windows?

seems like a patch is necessary for some of the issues, unfortunately. based on earlier in the thread, its a shader compilation issue?

I repeated under a number of different settings configurations, probably 2 dozen in all, and i found that when i turned my settings to low, and at lower and lower resolutions, the crash occured later and later in the particular fight.

Saw a post on reddit here https://www.reddit.com/r/armoredcore/comments/16184hj/comment/jxzrcdu/?utm_source=share&utm_medium=web2x&context=3 recommending proton 7. I went from crashing consistently after about the second volley in the Balteus fight, to being able to do 5 attempts without a crash. Seems to have fixed, or at least improved the situation.

I lost on purpose to test it multiple times, clearly.

Saw a post on reddit here https://www.reddit.com/r/armoredcore/comments/16184hj/comment/jxzrcdu/?utm_source=share&utm_medium=web2x&context=3 recommending proton 7. I went from crashing consistently after about the second volley in the Balteus fight, to being able to do 5 attempts without a crash. Seems to have fixed, or at least improved the situation.

I lost on purpose to test it multiple times, clearly.

I've finished the fight! I had to lower the game resolution to 800x600 and settings to low to get decent FPS, but going back to Proton 7 made the fight not freeze/crash the game.

Agreed, swapped to proton 7 and was able to get through the fight

At least, it held up as long enough as my skill issue took to catch up to get through the boss.

Can confirm that using Proton 7.0-6 allowed me to kill the boss after several attempts. No crashes at all, but performance got a severe hit, especially in Sortie screen and when assembling AC.

Unfortunately the next mission is basically unplayable for me due to extremely low fps, regardless of graphics settings. So I'd say while 7.0-6 allowed to pass Balteus, further playthrough is out of the question like this.

Can confirm that using Proton 7.0-6 allowed me to kill the boss after several attempts. No crashes at all, but performance got a severe hit, especially in Sortie screen and when assembling AC.

Unfortunately the next mission is basically unplayable for me due to extremely low fps, regardless of graphics settings. So I'd say while 7.0-6 allowed to pass Balteus, further playthrough is out of the question like this.

I went back to proton 8.0-3 to continue playing and was able to complete the next mission and arena fights with no problem. People were reporting some weird red flickering during the boss fight, so the shader problem might cause freeze/crash on some GPUs while others only have the flicker effect.

Replying to https://github.com/ValveSoftware/Proton/issues/7045#issuecomment-1694789530

Checked further and yes, all arena fights and several next missions completed without a hitch on GE Proton 8-13 into the beginning of chapter 3. As a sidenote, using Low settings causes crashes even in usual fights, playing on High does not. I guess different shaders are being used depending on the quality, so some as broken, some are not.

Proton 7.0-6 also crashes for me in the same way on Balteus.

I will be looking into a potential workaround.

Getting a strange hang (on Proton 7.0, 8.0, Experimental, and GE 8-13) after some time playing the game (sometimes 30-40 minutes, sometimes 5-15).
Specs are AMD Ryzen 5900X, 32GB 3200MHz, AMD 7900 XTX (specifically a Merc 310)
Running on RebornOS/Arch.

My screens freeze, and if I'm lucky I can get out into a tty upon which they unfreeze again. Can't get back into KDE (on Wayland) though, even if I kill the game and related processes :/

I can get any logs that could help, I just need to know what those would be, and where they might be located.

This is cut from the end of dmesg prior to shutting down via tty.

[ 6902.299753] amdgpu 0000:0c:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32831, for process armoredcore6.ex pid 122266 thread armoredcore6.ex pid 122266)
[ 6902.299761] amdgpu 0000:0c:00.0: amdgpu:   in page starting at address 0x000080000843c000 from client 10
[ 6902.299764] amdgpu 0000:0c:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00301430
[ 6902.299766] amdgpu 0000:0c:00.0: amdgpu: 	 Faulty UTCL2 client ID: SQC (data) (0xa)
[ 6902.299768] amdgpu 0000:0c:00.0: amdgpu: 	 MORE_FAULTS: 0x0
[ 6902.299770] amdgpu 0000:0c:00.0: amdgpu: 	 WALKER_ERROR: 0x0
[ 6902.299771] amdgpu 0000:0c:00.0: amdgpu: 	 PERMISSION_FAULTS: 0x3
[ 6902.299773] amdgpu 0000:0c:00.0: amdgpu: 	 MAPPING_ERROR: 0x0
[ 6902.299775] amdgpu 0000:0c:00.0: amdgpu: 	 RW: 0x0
[ 6912.734675] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered

I'm using echo "mangohud %command%" | sed 's/start_protected_game.exe/armoredcore6.exe/' | sh as the custom launch settings to run the game without EAC. I've also had gamemoderun and DXVK_ASYNC in there, but no difference (both to performance and crashyness).

quick edit: I know this has a non-zero chance of not being relevant here, but I couldn't get into the freedesktop gitlab (because it's timing out, 504) mesa to look around there to find somewhere more relevant

2023-08-29 update: I got it to work using the amdvlk drivers instead of vulkan-radeon. No crashes so far, and only a few issues towards the start of my session.

The game will no longer start for me. I just get a white screen and then I am booted out. It used to work just fine.

Replying to https://github.com/ValveSoftware/Proton/issues/7045#issuecomment-1694514368

Verifying the files did not work for me. I suspect it's a patch related thing.

Please try: https://github.com/HansKristian-Work/vkd3d-proton/pull/1672. This resolved any crash issues for me on Baltheus on NV and RDNA1.

Please try: HansKristian-Work/vkd3d-proton#1672. This resolved any crash issues for me on Baltheus on NV and RDNA1.

You can get a build from github actions: https://github.com/HansKristian-Work/vkd3d-proton/suites/15606862553/artifacts/890629683

and copy the x64 d3d12.dll d3d12core.dll next to the game's .exe for testing.

It's working fine on my 5700XT using the instructions from @mbriar, @HansKristian-Work. Now... Tell me you are trolling us buffing this MFing boss and it's not like this on the game

That build is working as well for me on my RTX 3050 mobile. Thank you @HansKristian-Work for the fix and @mbriar for showing how to test it! Now I can replay this mission an the other one with a similar freeze on Proton 8.0-3 again.

I can report that I had zero crashes during the "Attack the Watchpoint" boss fight, and had to take many attempts at it. Running Experimental (Bleeding-Edge).

I had zero crashes after using the fix

That patch works for me as well, thanks a ton!

Either the patch, or the patch combined with switching to amdvlk from my earlier post, has fixed the crashing as far as I can tell. Just had a successful multi-hour session with no issues.

@mbriar While I wasn't crashing, these DLLs seem to have fixed Balteus/Snail Balteus thrusters having rainbow colored flashing lights.

Confirmed that the new DLLs fixed it for me. TY for the quick fix @HansKristian-Work.

So this means that instead of trying to apply the bad shader to the image it's just skipped instead of crashing? If so, the shader not being applied was not visually noticeable to me in at least this instance - though I was also busy trying not to get missiles in my face.

@brandonegbert I don't think any shader is skipped, it's just more robust against accessing resources in a shader as the wrong type.

Worked for me as well :) I can play both Balteus fights w/o issue and have not experienced any more crashes in the game.

Game launches and runs fine here, at least during the first mission.

~However, I'm having issues getting the game to use my Dualsense controller (Flatpak Steam). Tried fiddling a bit with Steam input but no luck so far.~ Fixed by using gamescope.

I have the same gamepad problem. Switching to gamescope worked once, but then it broke again on the next launch.

Please try: HansKristian-Work/vkd3d-proton#1672. This resolved any crash issues for me on Baltheus on NV and RDNA1.

You can get a build from github actions: https://github.com/HansKristian-Work/vkd3d-proton/suites/15606862553/artifacts/890629683

and copy the x64 d3d12.dll d3d12core.dll next to the game's .exe for testing.

Thanks for much for this! Worked for me as well!
Using my 5700XT

@matyat This is probably a steam flatpak issue, and not an Armored Core issue https://github.com/flathub/com.valvesoftware.Steam/wiki#my-controller-isnt-being-detected.

Using nvidia driver version 535 and a Quadro M2200, I am getting the startup white-screen crash that @stealthswor is getting, and Hans' fix unfortunately did not work. Is anyone else getting this crash? It seems to be OS-agnostic since I see AI-generated articles on fixing it for Windows.

https://github.com/tuffee88/d3d12ProxyEdrDx11_0

I tried using this and it didn't work at all...

@nmlynch94 Thanks - I am using flatpak. I'll give that a look.

Yo, i recently got this game and i made it work with almost no problems at all, i used port proton/port wine, and every time it crashed i switched from LG to GE or from GE to LG, i know that this sounds really unprofessional but it worked out for me

On Nvidia Optimus laptop, it seems like the game will get stuck on black screen with Nvidia's PRIME environment variable (__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia) in the launch option.

Edit: added log from proton
steam-1888160.log

Changing to proton experimental fixed my issue

All of a sudden I'm unable to start the game. The EAC popup doesn't appear, clicking play just goes from play>stop>play.
Earlier today I had gotten updates for Proton Experimental (standard), as well as the Soldier and Sniper runtimes.
I tried Proton 8.0-3c and GE-Proton 8-14 as well but they get the same error. The only notable system updates I've gotten since I last ran the game was Kernel 6.4.14 last night, so I tried with the last two Kernel versions but no difference.
steam-1888160.log
Setting Sniper runtime to previous_release beta still has the same crash so I have no clue what the problem is.
steam-1888160.log

Other DX12 games such as DRG and MHR still launch without issue, as well as DX9-11 games.
System Information Steam Runtime Information

All of a sudden I'm unable to start the game. Earlier today I had gotten updates for Proton Experimental (standard), as well as the Soldier and Sniper runtimes. I tried Proton 8.0-3c and GE-Proton 8-14 as well but they get the same error. The only notable system updates I've gotten since I last ran the game was Kernel 6.4.14 last night, so I tried with the last two Kernel versions but no difference. steam-1888160.log Setting Sniper runtime to previous_release beta still has the same crash so I have no clue what the problem is. steam-1888160.log

Other DX12 games such as DRG and MHR still launch without issue. System Information Steam Runtime Information

I've gotten the same problem. you need to disable EAC to launch the game, I'm not sure how to fix EAC.

add this to the luanch options, it disables EAC but you can play single player

eval $(echo "%command%" | sed "s/start_protected_game.exe/armoredcore6.exe/")

EAC was working for me as is with no tinkering from day 1 to yesterday, though. Even played a few PVP matches the other night.
Trying to launch the game with that launch option and logging enabled resulted in the game window opening, but got stuck on a black screen seemingly unresponsive with several cores pegged at 100%. The log quickly ballooned to 2GB, so I alt+f4'd the game.
The game does run normally with that launch option if I disable the Steam Overlay.

I forgot to mention about the steam overlay, I don't use it by default.

EAC was working for me as well, until today

On a hunch I removed the shader cache folder for the game (1888160). The EAC popup returned and launched without issue again.
I did also see a shader precache download yesterday before I couldn't launch it.

I've already had to do this a second time, so it's something that should probably be looked into.

On a hunch I removed the shader cache folder for the game (1888160). The EAC popup returned and launched without issue again. I did also see a shader precache download yesterday before I couldn't launch it.

Thank you.

this worked

Please try: HansKristian-Work/vkd3d-proton#1672. This resolved any crash issues for me on Baltheus on NV and RDNA1.

Hey! Do you know if this is included on Proton Experimental? Can I delete the testing DLL files from the game?

It's included in Experimental now yes

Anyone else having glitches placing decals? On the AC6 subreddit someone else reported this issue as Linux/Proton specific as well - https://www.reddit.com/r/armoredcore/comments/164tgmb/decal_bugs/

I also have issues placing decals. Fromsoft support said SteamDeck and Linux are not officially supported but stay tuned for updates. Hoping an update to proton can resolve this issue.

Game on the Steam Deck Works widouth any isues on the default settings but on PC, any proton configuration aside from Proton GE 8-13 will result with the fps droping to single digits on the Garage/Asembly menu, also on Proton GE 8-13 any resolution above 1600 x 800 will give Tearing issues, on other versions of proton the issue seems aliviated with lower reolutions but it doesnt fix it like Proton GE 8-13 does

Specs
GTX 1050M 4gb
I5 8300h
NVME intel optane 512gb (game installed here)
Kingston A400
Hgste 500gb
WD Black 4TB

game works just fine on windows under the same PC so i guess its a problem related to resolution in the garage under Proton

https://github.com/ValveSoftware/Proton/issues/7045#issuecomment-1777122435

I've started having this issue placing decals about a week ago; before that time I had no issues. Because I'm using Proton Experimental, I thought a recent update could have caused it, so I also tried downgrading to the previous 2 versions, but neither worked.

System information

OS: Linux Mint 21.3 Cinnamon
Kernel: 5.15.0-112-generic
GPU: AMD Radeon RX 5700 XT
CPU: AMD Ryzen 7 3700X 8-Core Processor × 8
Proton: Experimental, 9.0-2, 8.0-5

I get an anticheat error (error no. 1) from the launcher unless I limit my CPU topology to 20 cores down from 64.

matt@threadripper-pc:~$ inxi -GSC
System:
  Host: threadripper-pc Kernel: 6.10.2-201.fsync.staging.fc40.x86_64
    arch: x86_64 bits: 64
  Desktop: KDE Plasma v: 6.1.3 Distro: Nobara Linux 40 (KDE Plasma)
CPU:
  Info: 32-core model: AMD Ryzen Threadripper 7970X s bits: 64
    type: MT MCP MCM cache: L2: 32 MiB
  Speed (MHz): avg: 1985 min/max: 545/5673 cores: 1: 545 2: 545 3: 545
    4: 5639 5: 4802 6: 545 7: 545 8: 545 9: 545 10: 5334 11: 545 12: 545 13: 545
    14: 4814 15: 4858 16: 4866 17: 545 18: 545 19: 545 20: 545 21: 545 22: 545
    23: 545 24: 4952 25: 5176 26: 545 27: 5127 28: 5178 29: 5322 30: 4810
    31: 5266 32: 4931 33: 5451 34: 545 35: 5618 36: 545 37: 545 38: 545
    39: 545 40: 5622 41: 545 42: 545 43: 545 44: 5334 45: 545 46: 545 47: 545
    48: 545 49: 545 50: 545 51: 545 52: 545 53: 545 54: 545 55: 545 56: 545
    57: 545 58: 545 59: 545 60: 545 61: 545 62: 545 63: 5133 64: 4844
Graphics:
  Device-1: AMD Navi 31 [Radeon RX 7900 XT/7900 XTX/7900M] driver: amdgpu
    v: kernel
  Display: wayland server: Xwayland v: 24.1.0 compositor: kwin_wayland
    driver: N/A resolution: 3440x1440
  API: EGL v: 1.5 drivers: radeonsi,swrast
    platforms: wayland,x11,surfaceless,device
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.1.3 renderer: AMD
    Radeon RX 7900 XTX (radeonsi navi31 LLVM 18.1.6 DRM 3.57
    6.10.2-201.fsync.staging.fc40.x86_64)
  API: Vulkan v: 1.3.280 drivers: N/A surfaces: xcb,xlib,wayland

without any launch options - anti-cheat error:
steam-1888160-64-cpu.log

with WINE_CPU_TOPOLOGY=20:0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19 - successful launch:
steam-1888160-20-cpu-topology.log

ARMORED CORE™ VI FIRES OF RUBICON™ (1888160) Not Detecting Controller

Issue transferred from [#9390](https://github.com/ValveSoftware/Proton/issues/9390). @ashtonx posted on 2026-01-11T05:07:38:

Regarding this one, it appears to work with Proton Experimental taken from steam. Not sure if it's steam input being fixed in that version or dualsense being detected, but it fixed this, and few other games that did not work.

The game appears to run well for me on Proton 10.0-4, but it does have regular small FPS drops that aren't present on Windows with the same hardware (5700x3d, 7800 XT, 32GB RAM).

[#7045(comment)](https://github.com/ValveSoftware/Proton/issues/7045#issuecomment-1777122435)

I am reproducing this decal placement issue in Armored Core VI on Proton Experimental (as of 2026-07-22).

Key Positional Observation:
Through testing, I noticed that the valid decal placement check seems to be strictly confined to the upper half of the screen's coordinate space on the mech surface. When attempting placement at coordinates in the lower half of the screen, all coordinates become unplaceable.

System Specs:
OS: openSUSE Tumbleweed
Desktop Environment: KDE Plasma (Wayland)
CPU: AMD Ryzen 7 9700X
GPU: AMD Radeon RX 9060 XT
RAM: 64 GB (DDR5 PC5-44800 32GB x2)
Proton: Proton Experimental (2026-07-22)

(Note: This report was translated from Japanese to English with the assistance of Gemini.)