Terrible Performance. No, thank you.

[Ovan]

As far as I played the demo, the game runs horribly.
I have no problem running MH World, but Wilds simply can't keep 60fps and DLSS makes the game look awful.

[firepistol95]

Escrito originalmente por del_bosque_dol:

Escrito originalmente por firepistol95:

It was also a vram overflow issue.
Dataminers found that the build the "beta" was using was from back in early 2024 with many incomplete assets, files and even broken World assets used for testing.
So in actuality the "beta" was an Alpha build.
Also found the build had NO lod system in place so everything was running in their max detail at any distance from the player. Which really hit perf hard and caused that weird N64 polygon bug.

What system do you have in order to get polygon? Pathetic gears.

i never had that issue personally since I had the cpu and vram to handle it. But tiny areas like the outpost hub dropping into the 30s/40s, despite the alpha build NEVER hitting 100% gpu usage (hanging around 70%) is already the easiest sign to tell the game is barely using PC hardware properly.
And then with the CPU having the 1st 2 or 3 cores being heavily used despite still enough cores to distribute workload across that are not being used much.

So the result of it is that its not the consumers fault or the MH devs fault.
And a lot of this issue from people can be solved, if they clarified how old the build was and that it wasnt representative to how the game would run.

[SoftpilLoW]

Escrito originalmente por del_bosque_dol:

Escrito originalmente por SoftpilLoW:

Rise is not an open world game, it was designed for the Switch and as you can see Rise has a much worse detail than World but is more CPU intensive.

I have an old PC with an i7 4790 + 1080Ti and it can play World perfectly without any FPS drop from 60, but Rise has frequent FPS drops and stuttering at the same specs, both running at Ultra 1440p settings.

Rise was initially designed but it is not the same for PS5 and PC, as a matter of fact, PS4 and PS5 versions are different.

SO you want more detailed textures unlike MHR or you will be hopeless as your PC specs will be a joke for a game designed for PS5 Pro.

You know that it is time to update your gears.

Again, the game engine has nothing whatsoever to do with your dated PC specs.

That's my other PC. I'm using the example of how the RE engine has terrible CPU usage, even though it has worse world details than World, but it needs a CPU more powerful than 4790 to play smoothly at 60 FPS.

The PC I use to play DD2 and Wild beta is i7 12700F + 4070ti 32GB ram SSD m2, which can't do 60 fps stable with Wild beta, and I'm sure it's better than PS5 and PS5 pro.

[del_bosque_dol]

Escrito originalmente por firepistol95:

Escrito originalmente por del_bosque_dol:

What system do you have in order to get polygon? Pathetic gears.

i never had that issue personally since I had the cpu and vram to handle it. But tiny areas like the outpost hub dropping into the 30s/40s, despite the alpha build NEVER hitting 100% gpu usage (hanging around 70%) is already the easiest sign to tell the game is barely using PC hardware properly.
And then with the CPU having the 1st 2 or 3 cores being heavily used despite still enough cores to distribute workload across that are not being used much.

So the result of it is that its not the consumers fault or the MH devs fault.
And a lot of this issue from people can be solved, if they clarified how old the build was and that it wasnt representative to how the game would run.

Yeah what you wrote is the exact problem of this game. But running at 100% may cause sudden performance drops, which make even less playable.

[del_bosque_dol]

Escrito originalmente por SoftpilLoW:

Escrito originalmente por del_bosque_dol:

Rise was initially designed but it is not the same for PS5 and PC, as a matter of fact, PS4 and PS5 versions are different.

SO you want more detailed textures unlike MHR or you will be hopeless as your PC specs will be a joke for a game designed for PS5 Pro.

You know that it is time to update your gears.

Again, the game engine has nothing whatsoever to do with your dated PC specs.

That's my other PC. I'm using the example of how the RE engine has terrible CPU usage, even though it has worse world details than World, but it needs a CPU more powerful than 4790 to play smoothly at 60 FPS.

The PC I use to play DD2 and Wild beta is i7 12700F + 4070ti 32GB ram SSD m2, which can't do 60 fps stable with Wild beta, and I'm sure it's better than PS5 and PS5 pro.

Performance target for PS5Pro is 4k 60fps, and likely 1080 120fps, as I saw an option choosing 120 fps mode during PS5 OBT. (PS5Pro release was 1 day after OBT ended).

Your system should be more capable than PS5Pro, and I see your point. You have every reasons to believe your PC should be capable of running at 120fps without drop.

Wait for demo before the release or even wait until driver update for Wilds will be more careful approaches.

[Spardacus]

Performance were bad, especially that the game looks just OK, nothing WOW, what we see on the screen doesn't justify the perfs.

[[{******---Dead4Life---******}]]

Escrito originalmente por Spardacus:

Performance were bad, especially that the game looks just OK, nothing WOW, what we see on the screen doesn't justify the perfs.

Agreed, even if it runs just ok for me on PC, it's not a well optimised game.
DD2 incoming.

[firepistol95]

Escrito originalmente por del_bosque_dol:

Escrito originalmente por firepistol95:

i never had that issue personally since I had the cpu and vram to handle it. But tiny areas like the outpost hub dropping into the 30s/40s, despite the alpha build NEVER hitting 100% gpu usage (hanging around 70%) is already the easiest sign to tell the game is barely using PC hardware properly.
And then with the CPU having the 1st 2 or 3 cores being heavily used despite still enough cores to distribute workload across that are not being used much.

So the result of it is that its not the consumers fault or the MH devs fault.
And a lot of this issue from people can be solved, if they clarified how old the build was and that it wasnt representative to how the game would run.

Yeah what you wrote is the exact problem of this game. But running at 100% may cause sudden performance drops, which make even less playable.

No I mean if the game is running around that fps then the GPU should already be at 100% usage. But since it is nowhere near that, it means the game isnt properly using the "power" of the hardware ie Wasted Performance

[Old_Viking]

I love how 4070 - 90 kids talking about upgrades :D
average card today is 3060/4060, the fact that you want and can spend money on better PC doesn't put you in a "majority" position :) Game developers will always be making games for average PC not this top shelf nonsence. Check the recommended settings, developers recommend 2060, what upgrades are you talking about?

Another thing. Have you heard KC:D players complain about low frame rate? No. Do you know why? Because game has amazing optimization and looks fantastic. It runs better then the 1st part to be honest. So why would Wilds not run better than World? It looks exactly the same, have they spend all the money on hair animations, instead of optimization? I don't know. I run everything on my 3060 laptop on High just fine, so why wouldn't I expect to have the same performance from an ok-ish looking game with recommended 2060?

[@InfaMissGoddess on X]

Escrito originalmente por Ramirez:

Another thing. Have you heard KC:D players complain about low frame rate? No. Do you know why? Because game has amazing optimization and looks fantastic. It runs better then the 1st part to be honest. So why would Wilds not run better than World? It looks exactly the same, have they spend all the money on hair animations, instead of optimization? I don't know. I run everything on my 3060 laptop on High just fine, so why wouldn't I expect to have the same performance from an ok-ish looking game with recommended 2060?

KC:D2 runs on a modified old ass cryengine build, because there hasnt been an update to cryengine in years. Cryengine games always looked great on the surface level, but its not doing anything tech wise that would push gpu's hard.

[Surf]

Escrito originalmente por InmaDjinn Samalik:

To be fair you are playing a beta.

Give the feedback and they are likely gonna patch it before relase

My brother in Christ, this game has been worked on for 6 years, and its releasing in less than 20 days. Why are you like that?

[Soren]

Escrito originalmente por Surf:

Escrito originalmente por InmaDjinn Samalik:

To be fair you are playing a beta.

Give the feedback and they are likely gonna patch it before relase

My brother in Christ, this game has been worked on for 6 years, and its releasing in less than 20 days. Why are you like that?

The concept could apply to balance changes or other minor mechanics. Like with Resident Evil 4, Capcom received feedback the rain was too heavy in trailers. They changed that with the day 1 patch before players even got to play the game.

But yeah, optimisations are not easy. They will only do so much in the day 1 patch. And no amount of feedback will change what we're getting as the performance is set in stone at this point. If I'm not mistaken, the team said they're focusing on optimising some later parts of the console versions before launch too.

[Marquez2002]

The main problem with the game is that they made it with 30fps in mind, you can know this just by looking at the game recommended hardware, they say that in order to have 60fps, at any preset this is either minimum seting or ultra settings, you will have to enable framegen, for mi im just gonna play it at 45 capped fps and hope for a pacth or a mod that can do something about the performance

[Branded Lost]

Escrito originalmente por Ovan:

Escrito originalmente por InmaDjinn Samalik:

To be fair you are playing a beta.

Give the feedback and they are likely gonna patch it before relase

More likely for them to patch it 6 months after release, like they did with DD2.

trueeeee

[Santa]

Escrito originalmente por InmaDjinn Samalik:

To be fair you are playing a beta.

Give the feedback and they are likely gonna patch it before relase

They did not it appears. Guess it’s going to be patched after release, weird way of doing it.

[Ovan]

Escrito originalmente por Kai:

Escrito originalmente por InmaDjinn Samalik:

To be fair you are playing a beta.

Give the feedback and they are likely gonna patch it before relase

They did not it appears. Guess it’s going to be patched after release, weird way of doing it.

Of course they didn't patch it. That's the excuse of literally every developer, "the demo is an old build, it will be better at release". Get release still broken.