search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
24.63k stars 1.07k forks source link

ARMORED CORE VI FIRES OF RUBICON (1888160) #7045

Open kzdixon opened 1 year ago

kzdixon commented 1 year ago

Compatibility Report

System Information

I confirm:

steam-1888160.log

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

Have tried every permutation possible to try and get it working on my system:

Notably:

UPDATE: It seems that Steam's preload may have been the root cause of my problems regarding EAC and the game not letting me play. 2023-08-26-18:26:25-screenshot 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.

HansKristian-Work commented 1 year ago

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

mbriar commented 1 year ago

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.

alosarjos commented 1 year ago

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

Italo-ols commented 1 year ago

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.

kzdixon commented 1 year ago

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

HenrikDK2 commented 1 year ago

I had zero crashes after using the fix

theOperand commented 1 year ago

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

lyssieth commented 1 year ago

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.

DonKatsu commented 1 year ago

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

brandonegbert commented 1 year ago

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.

mbriar commented 1 year ago

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

lostpolaris commented 1 year ago

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

matyat commented 1 year ago

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.

LucasSymons commented 1 year ago

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

nmlynch94 commented 1 year ago

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

nilbuz commented 1 year ago

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.

stealthswor commented 1 year ago

https://github.com/tuffee88/d3d12ProxyEdrDx11_0

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

matyat commented 1 year ago

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

ULTRAMEGASUPERDELUXE commented 1 year ago

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

seasea128 commented 1 year ago

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

stealthswor commented 1 year ago

Changing to proton experimental fixed my issue

DonKatsu commented 1 year ago

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

tvienneau404 commented 1 year ago

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/")

DonKatsu commented 1 year ago

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.

tvienneau404 commented 1 year ago

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

EAC was working for me as well, until today

DonKatsu commented 1 year ago

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.

tvienneau404 commented 1 year ago

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

alosarjos commented 1 year ago

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?

Blisto91 commented 1 year ago

It's included in Experimental now yes

StarrKiss commented 1 year ago

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/

kisak-valve commented 1 year ago

ARMORED CORE™ VI FIRES OF RUBICON™ (1888160)

Issue transferred from https://github.com/ValveSoftware/Proton/issues/7191. @CaptainBasch posted on 2023-10-24T08:38:51:

Compatibility Report

System Information

I confirm:

steam-1888160.log

Symptoms

The decal cursor does not recognize the surface of the Armored Core model when in decal placing mode. As a result, decorating Armored Cores with decals is almost completely non-functional.

Reproduction

  1. Open Armored Core VI: Fires of Rubicon on any Linux distro with Steam Play enabled for all titles.
  2. Play past the intro level, or get a save file that is past the intro.
  3. Go to AC Design -> Decals -> Head/Core/Arms/Legs -> Custom Decals in the main menu.
  4. Try to place a "Custom Decal" on any of the parts.
  5. Move the cursor around and observe it's terrible unreliability.
cheyngoodman commented 1 year ago

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.

CherryTheGoth commented 6 months ago

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

char-cole commented 5 months ago

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

matte-schwartz commented 4 months ago

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 ``` 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