protonscr

Steam Client | Installed DLC Content Improperly Handled (For: NARUTO SHIPPUDEN: Ultimate Ninja STORM 4) by Steam Client

steamclosed
ValveSoftware/steam-for-linux#11946 · opened 2025-04-26 by YoreonX · updated 2025-04-29 · 6 comments · github
YYoreonX 2025-04-26 github

Your system information

  • Steam client version (build number or date): Version: 1745269938

  • Distribution (e.g. Ubuntu): Fedora Linux 42 (KDE Plasma Edition)

  • Opted into Steam client beta?: Affects both - [Yes]

  • Have you checked for system updates?: [Yes]

  • Steam Logs:

Steam Logs (TAR.GZ) - steam-logs.tar.gz

Generated System Report - systemreport-20250426214343.txt

Steam Runtime Information - steam-runtime-information.txt

System Information Log - system-info-04-26-25.txt

  • GPU: AMD RX 9070 XT 16GB

Please describe your issue in as much detail as possible:

https://steamcommunity.com/app/349040/discussions/

Above is Relative Steam Discussion Page for App ID: 349040, there are Dozens of Threads Concerning this across languages & Operating Systems.

Image

If you are an owner of NARUTO SHIPPUDEN: Ultimate Ninja STORM 4 & Own DLC content such as:

'Season Pass' or "NARUTO STORM 4 : Road to Boruto Expansion DLC".

You will notice on both client versions of Steam such as Steam Client(Stable) & Steam Client: "Steam Beta Update" that DLC for this title will not register upon launch despite being checked.

Image

The DLC are present as reflected in the above screenshot.

(This is not a Proton Issue, it happens on Steam Client Stable for Windows also)

Steps for reproducing this issue:

  1. (Open)Steam Client ---> Steam / Settings --> Interface --> Client Beta Participation: Set to Beta(Also Happens on Stable).

  2. Have NARUTO SHIPPUDEN: Ultimate Ninja STORM 4(App ID: 349040) + All DLC Installed.

  3. Launch Game.

4(a). If the DLCs are not activated your Menu Screen will look like this:

Image

4(b). If the DLCs are installed corrected this is how the initial Menu w/DLC Installed will look:

Image

  1. If the DLC is not installed and you proceed past The Initial Menu:

Image

You will be prompted to delete all of your saved data in-order to play the game, rendering it effectively unplayable at best & at worst you don't get access to the DLC you paid for.

Misc:

(The Specific DLC that changes the Initial Menu is "NARUTO STORM 4 : Road to Boruto Expansion" btw, not super relevent since all DLCs are formally busted.)

Just to recap - The DLCs are installed nothing has changed. The reason I resort to calling this a(potential) Steam Client issue, is due to one of my Steam friends(Windows Version) was on (Beta)Steam & noticed this issue(Inability to Play w/o DLC) on the Steam Beta Release for April 9th 2025. The solution was to switch to Steam(Stable) Client.

Not before we exhausted other alternatives | Checking Game Files for DLC Content, Manually Deleting All Related Folder Content & Verifying All Files(Full Uninstall), Preserving(Copying) Save Files & Removing them. Then proceeding w/new Save Files.

Everything more or less points to some issue happening under the hood(DRM?) that I cannot verify since Steam is Proprietary Software so I have to report it here.

(Would have reported it back then but i'm recovering from surgery ;P)

Kkisak-valve maintainer 2025-04-26 github

Hello @YoreonX, 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/2389#issuecomment-2832730213.

YYoreonX 2025-04-27 github

I will respect that, but I am of firm belief that this is not Proton related.

It can be reproduced on Windows(Was initially found on Steam Client: Beta for Windows).

If it's easier to track the origin of Steam Client related bugs(since I am on Linux & did use Proton for this data collection), via specific Proton game-based issue threads I'll concede; that's fine.

I just know the issue is not Proton related, since it occurs ever since the new Client Stable update on all Operating Systems.

So hopefully it goes where it needs to go, I don't want to waste anyone's time.

Ffapzeg 2025-04-28 github

Has anyone found a solution to the problem? A fix file? To make everything work. Or should I only run it through the old Steam client?

YYoreonX 2025-04-28 github

Has anyone found a solution to the problem? A fix file? To make everything work. Or should I only run it through the old Steam client?

There is nothing we can do on our end on Windows or Linux.

This is a bug from Beta Steam Client that has made its way into the Stable Client release.

It's entirely up to Valve to resolve this.

I don't expect @kisak-valve to allow this thread to be reopened though.

Jjn64 2025-04-29 github

@YoreonX @fapzeg @MrDotDan There's a Steam client beta update April 28th today that seems to address this.

How to enable Steam client beta:
https://help.steampowered.com/en/faqs/view/276C-85A0-C531-AFA3

YYoreonX 2025-04-29 github

@YoreonX @fapzeg @MrDotDan There's a Steam client beta update April 28th today that seems to address this.

How to enable Steam client beta:
https://help.steampowered.com/en/faqs/view/276C-85A0-C531-AFA3

Thank you, I've spread the word to the effected communities, as can confirm the hotfix does indeed resolve the issue for the Storm community atleast.

I will now informally consider the issue closed.

Upstream links