protonscr

Nier Replicant DLC items invisible/crashing

steamclosed
ValveSoftware/steam-for-linux#11951 · opened 2025-04-28 by jn64 · updated 2025-04-29 · 3 comments · github
Jjn64 2025-04-28 github

Your system information

  • Steam client version (build number or date): version 1745269938, build date Mon, Apr 21 19:22 UTC -08:00
  • Distribution (e.g. Ubuntu): Fedora 41
  • Opted into Steam client beta?: No
  • Have you checked for system updates?: Yes
  • Steam Logs: removed
  • GPU: AMD RX 6600

Please describe your issue in as much detail as possible:

Starting within the last two weeks, the NieR Replicant 4 YoRHa DLC for NieR Replicant™ ver.1.22474487139... has become unusable:

  • The DLC weapons are invisible when equipped.
  • Changing to a DLC outfit and then loading a save where that character is present crashes the game. (Outfits are changed in the main menu before loading a save.)

The earliest report I can find is April 13th this review from April 18th; more than a dozen others have since reported the same in this thread. One user claims rolling back Steam client to March 12th resolves it, but I have not attempted to replicate.

The game and DLC's public depots have not changed recently (as far as I can tell from SteamDB and my logs) and the issue is OS-agnostic hence I'm reporting against Steam client.

Steps for reproducing this issue:

  1. Load a save in Nier Replicant

  2. Equip a DLC weapon (e.g. "Virtuous Contract")

  3. Weapon becomes invisible

  4. Return to title

  5. Equip a DLC outfit (e.g. "Type-S" for Boy) in main menu > Options > Wardrobe

  6. Load a save with the boy main character - Crash

Kkisak-valve maintainer 2025-04-28 github

Hello @jn64, we're tracking issues with games run with Proton in the Proton issue tracker. Also, we're using one issue report per unofficially supported game title, so I've gone ahead and transferred this issue report to https://github.com/ValveSoftware/Proton/issues/4777#issuecomment-2836288507.

Jjn64 2025-04-28 github

@kisak-valve It's not a Proton issue. I'm using Proton but other reports are from Windows users.

Besides, I am using a specific old custom Proton build (GE-Proton9-13) from 2024-09 to work around long-standing cutscene issues so it cannot be the cause of this new problem.

How else should I report this so it isn't buried wrongly in an inactive Proton issue where nobody will see it?

Jjn64 2025-04-28 github

Found #11946 affecting another game in the same way (DLC stopped working recently despite no change in game/DLC files), also clearly not a Proton bug affecting both Windows and Linux users, also closed immediately without due consideration.

Proton versions

Upstream links