>>715866505 (OP) Even the Series X and PS5 Pro would shit their pants if you started having massive destructible environments and things shifting things all over the place. I'm going to assume whatever's causing those mud ripples is creating a bunch of geometry objects all moving simultaneously given how uneven and jittery it gets, and the engine is probably shitting itself trying to process all of it at once; might be an optimization issue, but at that point it doesn't matter what hardware it would be on.
This is a really weird segment because it's literally JUST this boss fight that performs like that and it happens in a really simple area compared to most others. But we're gonna see it posted for the next 6 months. Good job, Nintendo.
Anonymous
7/19/2025, 10:40:16 AM No.715867525
>>715866505 (OP) I wonder how did this pass the QA? did they just say fuck it it's fine, ship it like that?
>>715866887 Seems more like a shitty vsync solution where dropping any frames from 60 to say 55 or something will immediately lock you to 30. But the game is definitely also shitting itself somewhat, look at that expanding ring of mud or whatever at the end, the segments are all extremely jittery and shit, while this doesn't happen during the second animation loop.
Anonymous
7/19/2025, 11:27:01 AM No.715869379
>>715866887 How is this a defense? At best that just means the switch 2 is fine but they still made a shitty game for the hardware.
>>715866505 (OP) Still posting the same exact video from the same exact boss fight midway through the game, and have yet to provide other examples of it doing the same in other parts of the game. Spoiler: There isn't. Not even the Void Kong rematch at the Planet Core.