NARUTO SHIPPUDEN: Ultimate Ninja STORM 4 (349040)

[aardbol]

Compatibility Report

• Name of the game with compatibility issues: NARUTO SHIPPUDEN: Ultimate Ninja STORM 4
• Steam AppID of the game:

System Information

• GPU: RX 580
• Driver/LLVM version: Mesa 18.3
• Kernel version: 5.0
• Link to full system information report as Gist: https://gist.github.com/IsaakGroepT/44a9548da0089442e8e36ce3398bcff2
• Proton version: 3.16-7 Beta

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.

Symptoms

I'd like to report consistent crashes with UNS 4. Especially at loading the level where Sasuke and his team have to prove their worth by fighting the three hokage. It's a level in the beginning and I can't continue the story game due to these crashes.

Log: https://gist.github.com/IsaakGroepT/ba6cc25912150ba3ddb6b2c5c10d3715

Aside from the above, other crashes also happen with Free Battles. I think also during loading.

Reproduction

Start the level as described above

[kisak-valve]

Possible line of interest from the log: fixme:wincodecs:CreateComponentInfo {6fddc324-4e03-4bfe-b185-3d77768dc919} is not supported

[aardbol]

Just want to add that the issues remain with Proton version: 3.16-8 Beta

[zzhiyi]

https://github.com/wine-staging/wine-staging/tree/master/patches/windowscodecs-TIFF_Support should fix this. However it needs a real controller to enter main menu so I can test it at the moment.

[vjr2]

I just realize that some character models wont load in versus screen (like Sasuke) and other ones like Yamato will make the crash. In versus mode just try to select Yamato. I'm pretty sure it Will crash

[zzhiyi]

https://github.com/wine-staging/wine-staging/blob/master/patches/windowscodecs-TIFF_Support/0009-windowscodecs-Add-support-for-128bppRGBAFloat-format.patch applies cleanly and fixed this. Tested with 4.2-1 with a PS4 controller.

[vjr2]

https://github.com/wine-staging/wine-staging/blob/master/patches/windowscodecs-TIFF_Support/0009-windowscodecs-Add-support-for-128bppRGBAFloat-format.patch applies cleanly and fixed this. Tested with 4.2-1 with a PS4 controller.

How did you apply that??

[zzhiyi]

https://github.com/wine-staging/wine-staging/blob/master/patches/windowscodecs-TIFF_Support/0009-windowscodecs-Add-support-for-128bppRGBAFloat-format.patch applies cleanly and fixed this. Tested with 4.2-1 with a PS4 controller.

How did you apply that??

cd proton/wine && git apply 0009-windowscodecs-Add-support-for-128bppRGBAFloat-format.patch

[zzhiyi]

Fixed in proton 4.2-3

[aardbol]

I've finished already 38% of the game and yes it's been running stable so far. But there's still one issue that's left unfixed. After x amount of time my monitor goes into standby mode. It's probably related to the energy saving setting in KDE Plasma. But it happening has an effect on the stability of the game after coming back out of standby mode by moving the mouse (I'm playing with a controller). It caused the movies to have a lag and the subtitles not displaying properly.

[kisak-valve]

naruto shippuden ultimate ninja storm 4 crash at startup

Issue transferred from https://github.com/ValveSoftware/Proton/issues/4053. @claimax10 posted on 2020-07-08T15:01:13:

when i open naruto shippuden ultimate ninja storm 4 it opens 3 sec and then exits please help

[TheHighGroundWins]

I want to comment that after messing around with different proton versions, proton experimental fixed my game not starting and my game crashing when Hashirama is selected or Hanabi is hovered over in the character select screen.

this may be helpful for some of you.

[kisak-valve]

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

Issue transferred from https://github.com/ValveSoftware/steam-for-linux/issues/11946. @YoreonX posted on 2025-04-26T23:03:58:

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.

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.

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:

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

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

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)

[YoreonX]

This is not a Proton issue @kisak-valve.

This is an issue w/a(potential) error in Steam Client's verification process or DRM failure within Steam's Client Software.

This happens on Windows Also(For this game), so Proton is not the appropriate thread for my post.

The issue is not related to the Game's code either, as its Publisher has claimed that this is related to the latest Steam update.

Proton is strictly for Game Compatibility issues strictly relating to Linux & other Platforms, Architectures that use Wine/Proton & the relevant bugs that are related to that.

This was originally discovered on Windows as far back as April 9th 2025 & made its way into Stable Client last update as of 04/26/25.

[YoreonX]

Replying to https://github.com/ValveSoftware/Proton/issues/2389#issuecomment-2832835300

Just to follow up.

The Steam Discussion Threads are exploding.

Across All Operating Systems. (Windows or Proton.)

This bug was originally noticed by Beta Steam Users.

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

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

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

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

[YoreonX]

Replying to https://github.com/ValveSoftware/Proton/issues/2389#issuecomment-2833687233

I do not work at Valve nor do i have access to the proprietary code, it seems like a DRM failure with the Steam client that is preventing DLCs from working.

Which is why i posted originally in the Steam-For-Linux Issue thread @kisak-valve .

[YoreonX]

Replying to https://github.com/ValveSoftware/Proton/issues/2389#issuecomment-2833687233

I do not work at Valve nor do i have access to the proprietary code, it seems like a DRM failure with the Steam client that is preventing DLCs from working.

Which is why i posted originally in the Steam-For-Linux Issue thread @kisak-valve .

@kisak-valve Original Issue has been fixed by a Steam-for-Linux Beta Client Update: https://github.com/ValveSoftware/steam-for-linux/issues/11946

Contributors: Ignore any other responses of mine in this Proton thread prior to this commeng as they were not Proton specific issues & has been resolved.

[GyomeiHimejima9906]

the game don't reconize my PS4 controller (recuneze the controller but you can't use it) log:

steam-349040.log

error: 2299.373:011c:0120:fixme:combase:RoGetActivationFactory (L"Windows.Gaming.Input.RawGameController", {eb8d0792-e95a-4b19-afc7-0a59f8bf759e}, 00006FFFFD458960): semi-stub at line 949

[GyomeiHimejima9906]

the game don't reconize my PS4 controller (recuneze the controller but you can't use it) log:

steam-349040.log

error: 2299.373:011c:0120:fixme:combase:RoGetActivationFactory (L"Windows.Gaming.Input.RawGameController", {eb8d0792-e95a-4b19-afc7-0a59f8bf759e}, 00006FFFFD458960): semi-stub at line 949

i fixed them by using Arch Linux base with a kernel 6.15.3-zen1-1-zen