Dont Review Bomb Over Petty Things

[Jesse]

All of these people spouting negativity over basically nothing are likely going to make this game be a "mixed" release.

Lets be mature and focus on the game as a whole and not the 15 hours of story or the performance. If you've ever played monster hunter you know the story is barely the tutorial and make sure your PC hardware has been updated in the past couple years before you cast judgement.

[Bacuda]

If the game still runs or close to how it was in beta, a lot of ppl won't be happy, understandably so, I just hope the performance is A LOT better then what we saw on the beta or the benchmark, if not, then yeah, I can see a lot of ppl giving it a bad review, which is probably a valid reason, the game has no reason to run like it did on beta while visually really not looking that impressive.

[matija123123]

❤️ニューハーフ님이 먼저 게시:

matija123123님이 먼저 게시:

Don't leave a negative review for a game that 90% of fans won't be able to play due to laziness and cost cutting.

Funny thing is, even if performance was +- ok, the game is a step down to me from World.

We saw 10% of the games content we literally don't know if it's better or worse than world itself.

When it comes to personal taste that's fine but It also does not mean game is objectively bad all of a sudden because it's not like the previous thing.

[DaBa]

Oh I will definitely be giving this a "not recommended" because of terrible performance, I genuinely would not recommend a game that runs this poorly to a wider audience of people. It's just not worth it if you aren't a MH fan and really want to play it, it's far better to just get World and Rise.

[matija123123]

Bacuda님이 먼저 게시:

If the game still runs or close to how it was in beta, a lot of ppl won't be happy, understandably so, I just hope the performance is A LOT better then what we saw on the beta or the benchmark, if not, then yeah, I can see a lot of ppl giving it a bad review, which is probably a valid reason, the game has no reason to run like it did on beta while visually really not looking that impressive.

Beta was using a old build benchmark was using a new build from what I heard.

[Bacuda]

matija123123님이 먼저 게시:

Bacuda님이 먼저 게시:

If the game still runs or close to how it was in beta, a lot of ppl won't be happy, understandably so, I just hope the performance is A LOT better then what we saw on the beta or the benchmark, if not, then yeah, I can see a lot of ppl giving it a bad review, which is probably a valid reason, the game has no reason to run like it did on beta while visually really not looking that impressive.

Beta was using a old build benchmark was using a new build from what I heard.

I know, but the beta and benchmark was really not that different, it was better ofc, but still pretty terrible.

[Tyrsky]

Benchmark was also a joke as it was mostly cutscenes and only a small percentage was gameplay. They didn't even fight a single monster in it.

[Spinning Toilet]

Jesse님이 먼저 게시:

All of these people spouting negativity over basically nothing are likely going to make this game be a "mixed" release.

Lets be mature and focus on the game as a whole and not the 15 hours of story or the performance. If you've ever played monster hunter you know the story is barely the tutorial and make sure your PC hardware has been updated in the past couple years before you cast judgement.

story being 15 hours is fine but the games performance is not a hardware thing the game is just shiddly optimised

[matija123123]

Bacuda님이 먼저 게시:

matija123123님이 먼저 게시:

Beta was using a old build benchmark was using a new build from what I heard.

I know, but the beta and benchmark was really not that different, it was better ofc, but still pretty terrible.

Sadly benchmark is the finished product and I doubt there will be some miraculous day 1 patch because they would have to change a lot of stuff to properly polish stuff.

Also benchmark used 2 fairly calm and simple cutscenes no combat and a lot of slow walking so you are probably getting few frames more than you will see when actually playing.

2 options now are either waiting for modding community to do Capcoms job or to wait for months in cope that they will fix stuff.

Dragon dogma 2 was a unfortunate disaster that I have seen as a accidental mistake but now with wilds I just realized that this is how it is with their games performance wise.

I am being a bit more negative than usual but that is also because this is a game I really care about.

[Snooze Juicer]

i hope it gets review bombed, ive always wanted to see what its like to be a call of duty fan

[Nyxtus]

Genuine question by why do you care if it gets review bombed or not? Like you, as an individual with no ties to Capcom - why do you care at all?

[Kamakura]

I didn't have any performance issues with the beta, but someone giving a negative review if the game runs poorly is kinda the opposite of doing it for petty reasons. I don't support review bombing, it's often for very petty, garbage, reasons, but if they meet the requirements and the game doesn't run well, then yeah, that's enough of a reason to give a negative review.

[Nousos]

If someone pays $70 and doesnt refund, they are allowed to dislike the game. What is wrong with that?

[TR1PLE 6]

Tyrsky님이 먼저 게시:

Benchmark was also a joke as it was mostly cutscenes and only a small percentage was gameplay. They didn't even fight a single monster in it.

Yeah, the cutscenes over-inflated the score. My 4070 + 9700X rig was getting about 40-45 FPS in the gameplay bit and because of the cutscenes sometimes running in the 100s, the average FPS was in the 70s and 'excellent'.

[Bacuda]

matija123123님이 먼저 게시:

Bacuda님이 먼저 게시:

I know, but the beta and benchmark was really not that different, it was better ofc, but still pretty terrible.

Sadly benchmark is the finished product and I doubt there will be some miraculous day 1 patch because they would have to change a lot of stuff to properly polish stuff.

Also benchmark used 2 fairly calm and simple cutscenes no combat and a lot of slow walking so you are probably getting few frames more than you will see when actually playing.

2 options now are either waiting for modding community to do Capcoms job or to wait for months in cope that they will fix stuff.

Dragon dogma 2 was a unfortunate disaster that I have seen as a accidental mistake but now with wilds I just realized that this is how it is with their games performance wise.

I am being a bit more negative than usual but that is also because this is a game I really care about.

You and me both, I love monster hunter, and I also don't expect it to be much better if any better at all then what was shown in the benchmark, but I still hope they did something to optimize it more since then.

The benchmark was really skewed if you go off the average fps you got at the end of it, 2/3 of it was pretty much cutscenes, if you just went off the middle part which was actual gameplay the performance was pretty bad, and that was in the desert, no combat, no other players, no denuvo, I can only imagine how it would run with all that added in a foresty area for example,
I just hope for the best because I really want this game to do well, but I am a little bit worried to say the least, specially because they also ask you to run framegen to reach 60 fps in the recommended specs, which is absolutely not what framegen is meant for, nor does it work like that, ppl that get 60 fps with framegen enabled will have a terrible experience.

[Combine54]

Are you a clown or something?
This is not Early Access - it is a full release. It must work fine on modern hardware or it will receive bad reviews - justified.