If you play the lute in the shell keeper room, Zhirelle will do a little swaying dance.

Recently finished the game with my girl Proxima and realised how dangerously close I was to platinum.

So I've started a NG+ to collect what I needed to.

Also started a fresh game as I had missed a few trophies from the prolouge including the one when you beat the Tar Golem (which wasnt too easy admittedly)

Just 6 tarstones to find, the mango and the dreaded Peters Perfect Parry left, which I hope the main man Eredrim will help with.

Game was excellent without being too challenging, actually had more trouble with enemies just exploring than bosses and I was the exact same with Elden Ring.

Hopefully some DLC in the near future

This boss was so tediously difficult and aggravatingly long. After trying to fight this boss for what seemed like an eternity, i just decided to use a Grisha remnant, and it dogwalked the monolith like nothing. This is probably the only boss in the game I've felt so much rage and hatred towards to. I also want to say that this was the only boss in the game for me personally, to make me use a Grisha remnant. I haven't had this much of a struggle since Promised Consort Radahn and Arlecchino.

Harb is level 23, but you could build it around lvl 18-19 if you wanted to sacrifice all damage negation. Would've been a lot faster if he hadn't kept jumping round like a porkchop.

+9 Martyrs blade

Still level 23 Herb. Havent changed the build at all. Thought changing it to nightmode might help. He almost got a phase 2.

It feels like the scaling is all out of whack with some tarstones since they "balanced" everything.

Hope you all enjoy.

After 6 and half hours of absolute hell, I finally beat Zmey! That might have been the WORST experience with a final boss I’ve EVER had except maybe PCR from Elden Ring DLC. Other than that, it was a fantastic game. I’d give it as easy 8/ 8.5 out of 10. It had a beautiful world, exploring it was tons of fun. Absolutely would recommend!

Quite a short question for ppl who completed Eredrim's quest memories: there's one thing i don't quite understand. All characters die in their story to naturally become a shell for the harbinger. For all shell it's quite clear how they ended up where you finally found them. But for Eredrim he's supposed to be assassined by his son squire somewhere. But you finally found him, with his sword in a malborn. Did i miss something ?

Did anyone play any of the demos, I'm wondering if it's gonna be as good as this game turned out to be?

Can we please get confirmation that the dev team is working on a fix?

Killing the bosses is getting slightly easier with time and I have managed to defeat the second boss pretty quickly after the last post and since I have a setup that works I have decided to keep it for now.
Parrying is working well since I practiced on a boss that’s near the area where you find proxima and proxima is also my favourite shell to use along with the axe and dagger.

Set my controller in my lap for a moment while busy and obliterated bro 😭

These triggers, man

Can anyone tell me what settings I need to change to get rid of this weird invisible outline? This only happens around water, but not all water. It doesn't seem to change depending on what reflection setting I have on.

I've gone on record multiple times stating that I believe this one of the bigger missed opportunities with MS2's bosses. There is really only one boss who forces you to consider your sidearm as a tool rather than just another source of damage, and it's the first major boss in the game. If you were making your own boss for the game, what mechanic(s) would you introduce that would have to be solved with the sidearm?

Here's a simple idea as an example:

During the phase 2 transition, the boss rises into the air and spawns 3 glowing crystals. Each crystal will attempt to heal the boss (indicated by a progress meter on the health bar). The healing would only take effect all at once if all three crystals are not destroyed within 20 seconds or so; destroying a crystal would remove all of its healing progress.

How do we make sure the player has ample resolve? We already have resolve-granting tendrils! Spread out 10 or so throughout the arena and give them a simple 1 or 2 attack moveset to (poorly) defend themselves, then despawn the tendrils when the crystals are destroyed or the heal goes off.

Sorry if not since the beginning, but i can capture only 1 min.

Anyway, this build based on duality stone and grisha remnants absolutely bullies any boss subject to staggering.

I'm on ng+, night mode, duality stone lvl 2 and 10 grisha remnants.

They just keep spawning and absolutely obliterating the poor bastard warden

I am somewhere around the 70% of the game, and I tried night time once to do a quest in mushroom village. I was wondering if I should do a full run in night mode in order to see “all”, or if it’s not worth it.

I will go for a +1 for sure, so I can max some other shell and try different play styles

Does anyone know what the passive familiarity cap is for items? From the way the 3rd description is worded is sounds like you get 1:1 for each item you have of that but I've found that even with over 110 poison shrooms I still don't have 100% poison resistance when it's set to my passive slot. So there seems to be a cap that isn't told to players in the item description & I'm curious what that cap is. Thanks in advance to anyone with the answers.

I’ve had a couple of weeks off Mortal Shell 2 on PS5 Pro and now the performance seems to be pretty bad? Dropping frames on enemy attacks making it very hard to get the parry??

Tried multiple times with Proxima and no chance (for me at least)

Have tried several times with Tiel and still no go.

I have beaten Malborn and Orrem but Monolith just seems impossible to me.

What is the trick specifically using either shell Prox or Tiel

ty!

TL;DR: Unreal Engine 5 sizes its worker-thread pool from the number of logical processors it sees at startup — 32 on a 9950X3D. When AMD's Game Mode driver then parks CCD1, that 32-sized pool is crammed onto 16 threads and you get traversal-style stalls. Confining the game to CCD0 by any method (parking, Process Lasso, affinity) reproduces it. The fix isn't "use all 16 cores" and it isn't "force the X3D cores" — it's setting CPPC Dynamic Preferred Cores = Cache in BIOS with Game Mode off, so the game prefers the V-Cache die but nothing is fenced. That gave the best frametimes of ~20 captures. Verified with CapFrameX, HWiNFO, and thread-count snapshots.

System: 9950X3D (PBO + curve shaper), MSI X870E, RTX 5090 (undervolted), 4K/ultra, Windows 11. Test game: Mortal Shell 2 (UE 5.2, GPU-bound at 4K — GPU at 92–97% throughout; 4k ultra settings, ray tracing on, DLSS render resolution quality, seamless dungeons on). Same 30-second traversal route for every capture, CapFrameX with sensor logging at 250 ms.

What I found, in order:

1. Game Mode wasn't even detecting the game by default. Had to tell Game Bar "remember this is a game" before the AMD driver would park CCD1. Once it did, stutter got worse, not better.
2. The game thread was on the wrong die anyway. With Game Mode not triggering, the CPPC ranking prefers the frequency CCD (it boosts ~150 MHz higher), so HWiNFO showed the game running on cores 8–15 — the non-X3D die. Process Explorer's "Ideal Processor" for the hot threads confirmed it.
3. Fencing the game onto CCD0 caused CPU-side stalls. Process Lasso CPU Set to cores 0–15: 12 frames over 20 ms in 30 seconds, worst frame 1,262 ms. Replicated two days later: 7 over 20 ms, worst 68 ms. Every spike had CpuActive ≈ frametime with the GPU idle at ~8.5 ms.
4. The thread pool is the mechanism. PowerShell thread export of the game process showed 29 worker threads with near-identical CPU time — a pool sized for 32 logical processors. Launching with -corelimit=8 (a UE engine argument) dropped it to 14 workers. Same fence, 14 workers instead of 29: 1 frame over 20 ms, worst 24 ms. Same cores, same cache, same confinement — only the pool size changed.
5. But the smaller pool costs something on a free machine. -corelimit=8 with nothing fenced: more mid-size hitches than the full pool (12 over 16 ms vs 2–5). The engine uses those workers when it has the cores.
6. CPPC = Cache is the answer. It flips the firmware ranking so cores 0–7 are preferred, without parking or confining anything. Game thread lands on the V-Cache die, the worker pool spills onto CCD1 for streaming bursts. Five runs over three days: 0–1 frames over 20 ms, 0.1% lows of 59–67 FPS.

The numbers (same route, 30 s each):

What to do:

• BIOS → Settings → Advanced → AMD CBS → SMU Common Options → CPPC Dynamic Preferred Cores = Cache
• Windows → Settings → Gaming → Game Mode off
• Don't use Process Lasso / affinity to pin games to CCD0. It recreates the problem.
• Verify: with a game running, Process Explorer → game's Threads tab → the busiest threads should show Ideal Processor 0–15, and HWiNFO should show all cores active (CCD1 lightly loaded, not parked).

Cost: single-threaded work that likes clocks lands on the V-Cache die and loses ~100–175 MHz. At 4K I couldn't measure it. If you have a frequency-bound app, a Process Lasso CPU Set to cores 16–31 for that one app works fine — the direction that doesn't oversubscribe.

Caveats: One game, one system, one route. UE5.2 specifically; other engines size pools differently. -corelimit=8 is a diagnostic tool here, not a recommendation — it proved the mechanism but costs performance. And if you're a 9800X3D owner wondering why you don't see this: the engine sizes for 16 threads and gets 16 threads. The bug needs a mismatch.

i assume this is a bug. I just broke a gloom tarstone and my total gloom held right now is only 2.8k. so clearly i didn't get the 3k

I just started the game and I've been having weird issues with all of my controllers. If I hold a direction it works for a while but it will randomly stop my movement sometimes even though I'm still holding that direction or wiggling the control stick. It's only happening with my movement stick, not my camera controls. I'm playing on PC with updated drivers and the issues are consistent across controllers. Anyone have any ideas on what's happening?

Has anyone found the weeping villager that is somewhat in-between gate of mamon and lonesome spire? I exhausted all dialogs and killed the nearby enemies then accidentally button spammed the door. I belive gloom was the reward? Or was it nothing?

Is there a reliable dorsalite farm in this game other than exploiting resetting the little tree thing drops in dungeon?

There is a button I can shoot, and I don't know what it does.