Thread 715686824

>horrible pop-in
>blocky shadows
>only 1080p (dynamic res so sometimes drops below that)
>drops to 30fps frequently, including multiple entire bossfights
>constant microstutters when moving camera or picking up items
>FSR1
>destroyed terrain just floats in place with nothing supporting it
>even worse performance docked due to lower clock speed
All this while it looks like a fucking Wii game. What the hell is going on? This is not a good look for the rest of the gen. I'm honestly pissed Nintendo skimped so hard on performance.

it's really sad.
Nintendo could probably poach top technical programming talent and make some really nice games. But they just refuse to because they're betting on tendies paypigging no matter what.

>>715686824 (OP)
Glad I never bought this dogshit

Shit CPU running at basically the same clocks as the one in Switch 1 for one but apparently the game is also using FSR1 instead of DLSS and triple buffering crippling fps at even a minor drop which is to say, the game is coded as if it was still supposed to run on Switch 1.

>>715686824 (OP)
Better than 17fps PS5.

And it's zero FPS on your system LMFAOO

>>715686824 (OP)
It's a shitty mobile chip from 2022 based on a GPU architecture from 2020 that's not even allowed to run at max TDP because Nintendo couldn't stand the device becoming 5mm more thick.

>>715686824 (OP)
lmao and remember this game was being made for the original switch and it still runs like garbage.

>>715688435
>>715688472
>>715688920
>>715689152
Just wait for the Switch 3 bros

Why did Nintendo give up on competitive technical specs since the Wii? Their playerbase doesn't care if it's low fidelity cartoon shit but it can't even run those properly. And it isn't even the budget console anymore.

Snoys coping hard today huh?

>>715686824 (OP)
>>FSR1
it doesn't use upscaling at all anon
glad to know i can ignore everything else you said

>>715686824 (OP)
>he boughted

>>715686824 (OP)
It's using double buffer vsync just like mario wonder lmao.

>>715686824 (OP)
Those rings are the only fucked up part of this clip. I don't know what's producing the rings, maybe they're supposed to move like that as part of some attack pattern.

>>715689554
DF already said it uses FSR1 and the documentation proves it

>>715691223
The same people that already got caught more than thrice about the switch 2 alone?

>>715686824 (OP)
I'm sure theres more technically going on under the hood in DonkeyCraft, but it sure doesn't look better than Odyssey

>>715691525
It's because of this voxel shit. Everything in the game is made up of tiny cubes. Every tiny cube of terrain has to record shit like what kind of material it is, how much damage it has taken, probably some acoustical properties (there was a TotK presentation at GDC where they explained some technique that makes sounds echo more accurately, not sure if Bananza is using this). Without this destruction mechanic you would only have to update the position of the player character, enemies and NPCs every frame while the terrain would be static. With destruction you have to update every single cube of ground terrain every frame.
Imagine a 2D game but instead of updating just the Donkey Kong sprite, the Kremling sprites, and the spinning bananas, you have to update every individual pixel including the ones that make up the ground, trees, grass, etc.

>>715686824 (OP)
literally the only thing wrong with this clip is the mud waves stuttering, and thats separate from fps in every way. theres nothing wrong with running at 30fps as long as its constant, and you retards would never know the difference if you didnt have something telling you the number.

>>715686824 (OP)
Yet somehow it's a fun game

>>715686824 (OP)
Obvious bait thread but for anyone who wants to know this game isn't pushing the hardware as a whole, it's being bottlenecked on the CPU thanks to the voxel terrain, voxel terrain in general, especially with this sort of dynamism in such a large environment is both hard to optimize and hard to run well.

>>715686824 (OP)
switch 2 is basically a PS4
what did you expect?

>>715686824 (OP)
This looks extremely ugly

>>715686824 (OP)
I just dont get it
Where is this stress on the hardware coming from? Theres barely anything on the screen in terms of effectsand that lava is embarrassing
Does donkey kong have millions of polygons or something?

>>715693534
Literally multiple generations of hardware features ahead and the CPU and GPU are much faster, it's not basically a PS4, it's more like a PS4 pro.

>>715693534
a ps4 can't even run it's own games at a stable and consistent 30fps, this hits 60 with only occasional dips to 30 during heavy live terrain terraforming

>>715693747
The graphics in this game aren't at all comparable to the best on a PS4, DK's hair is less geometrically dense than most PS4 characters hair in the top detailed games, it's already obvious that the bottleneck here is the CPU, which is confusing as hell, Switch 2 is cooler than Switch 1 while docked, they had the room to boost CPU clocks but just chose not to.

>>715689292
Nintendo doesn't like selling hardware at a loss. They can't tolerate it like Microsoft or Sony.

>>715686824 (OP)
>>715689554
>>715691223
>FSR1

>uses AMD upscaling on noVidia chip
as always OP is a faggot

>>715686824 (OP)
It's not, there's nothing in Bananza that should be causing the system to chug, this is most likely a.patch-able issue, the game is not actually dropping frames but purposefully jumping from 60fps to 30fps for some weird reason.

>>715694304
There's probably like 4 unique posters total in this thread

>>715688472
this. nowadays every game pushes the console to its "limit", unless they're 2D indieshit. it just depends how the developer utilises this what's available - you can easily waste clock cycles on something that the player doesn't even see.

at least Nintendo still doesn't use UE5 and forces fake frames and smeared antialiasing

Shit performance like literally every AAA game released today. What's the problem?

>devlets when launch titles don't use the hardware as optimally as late gen releases
Super Mario 64 could've ran at 60 FPS if only they spent half a decade studying the Nintendo 64's architecture btw I'm very smart actually

>implying that there will ever be a point in time where the Switch 2 doesn't run like complete dogshit
>implying that the difference in developing software for the SNES and the 64 is remotely comparable to the difference between the Switch 1&2
>implying that the development difficulties of 64 were not compounded by it being the first 3D Mario (and one of the first 3D platformers in general) while greed and incompetence are the chief limiting factors for current releases
But go ahead, keep choking on that NuTendo cock. I bet it's tasty.

I thought the switch had DLSS. Why not use frame gen for those situations?

>>715697349
DLSS is not frame gen

>>715697747
DLSS3 includes framegen, so I thought the Switch 2, being a new device, would include said feature.

>>715686824 (OP)
You didn't take Bananza mogging Death Stranding 2 well

>>715697349
Two separate technologies. Switch 2 has DLSS support but because Bananza was a switch holdover title, it doesn't use it

>>715697791
DLSS is upscaling. Frame generation was introduced together with DLSS3 but is a separate thing.
Frame gen is really only worth it if you are already hitting at least 60FPS and want to go higher

PS4Pro ran bloodborne at stable 60fps using a mod
Apologize