Yup, this is the performance level we can expect at release. Beta 2 is exactly the same as beta 1, so it'll run worse than the benchmark. They've added some new hunts though, so I'll be jumping in again for sure, plus last time I had a 3080 which wasn't ideal, so I'm really looking forward to seeing how the 5080 handles it.
*** Monster Hunter: Wilds Thread ***
- Thread starter jinxpad
- Start date
Yup, this is the performance level we can expect at release. Beta 2 is exactly the same as beta 1, so it'll run worse than the benchmark. They've added some new hunts though, so I'll be jumping in again for sure, plus last time I had a 3080 which wasn't ideal, so I'm really looking forward to seeing how the 5080 handles it.
7900 XT @ 3840 x 1600, highest settings, native resolution with no upscaling, RT off
Same again but with FSR Quality
Same again but with max RT and Frame Generation On
(Probably should have tested this with FG off, but I was expecting mega low RT FPS on the 7900 XT)
Personally can't argue too much with performance, though there were some insultingly low frame rates in certain scenes without the corresponding eye candy pay off. I wasn't impressed with the visuals overall personally.
Curious to see what others VRAM usage is - my 7900 XT hit 18 GB at one point.
Same again but with FSR Quality
Same again but with max RT and Frame Generation On
(Probably should have tested this with FG off, but I was expecting mega low RT FPS on the 7900 XT)
Personally can't argue too much with performance, though there were some insultingly low frame rates in certain scenes without the corresponding eye candy pay off. I wasn't impressed with the visuals overall personally.
Curious to see what others VRAM usage is - my 7900 XT hit 18 GB at one point.
Last edited:
Seems extremely CPU-heavy still, but I agree performance does seem slightly better than the first open beta.
I'm not seeing huge VRAM usage but it could be because I'm on older generation hardware (3090ti).
I think I'll still get it on PC as PS5 will be 30fps anyway.
I'm not seeing huge VRAM usage but it could be because I'm on older generation hardware (3090ti).
I think I'll still get it on PC as PS5 will be 30fps anyway.
Last edited:
Beta is open again today.
Just did Arkveld, what a great fight.
Be warned that this beta client is the same one from last year's gamescom build so it's like 9-12 months old and does not have all the recent optimization and performance improvements in the benchmark. It still works just fine with DLSS4 (preset k transformer) as you can tell by the DLSS indicator in my screenshot. Looks and runs fantastic
Just did Arkveld, what a great fight.
Be warned that this beta client is the same one from last year's gamescom build so it's like 9-12 months old and does not have all the recent optimization and performance improvements in the benchmark. It still works just fine with DLSS4 (preset k transformer) as you can tell by the DLSS indicator in my screenshot. Looks and runs fantastic
Last edited:
Glad Arkveld's good. I won't be fighting them myself and will save them for the full release (I didn't kill Rey Dau the first OBT too). I'll probably boot up either this or the final test to kill the fire chicken though.Beta is open again today.
Just did Arkveld, what a great fight.
Be warned that this beta client is the same one from last year's gamescom build so it's like 9-12 months old and does not have all the recent optimization and performance improvements in the benchmark. It still works just fine with DLSS4 (preset k transformer) as you can tell by the DLSS indicator in my screenshot. Looks and runs fantastic
Associate
- Joined
- 18 Mar 2007
- Posts
- 1,495
- Location
- Moon
Arkveld's animations and special effects all going off is a sensory overload. was taking it all in then got kerb stomped and sent back to base 
Idk how it's CPU heavy when it's heavily GPU & VRAM bottlenecked. The betas have issues with textures and such, having a fancy X3D CPU makes little to no difference for me.
Most of the settings in the benchmark tool have the handy bars to show system impact, almost none of them show any impact on CPU.
Short of getting a CPU benchmark roundup (like Hardware Unboxed did for Starfield), it's hard to tell how hard it hits CPU.
But it's sure as day, many folks (including myself) will need to upgrade to better GPUs to even run this at playable framerates.
Don't think that will help much ... even people with 9800X3D's are having performance issues. The problem is that this game is just badly optimised ; the RE engine isn't a good fit for open world games. We saw this with Dragon's Dogma 2 and it's going to be the same technical disaster here. I love the MH franchise, but no way I'm pre-ordering this one after the betas ... definitely a wait and see.
Last edited:
I thought the performance was OK but I've not played a Monster Hunter game in a while so struggled wirth the combat a bit.
I'm going to get this anyway, I didn't think I'd like monster hunter world but it grew on me when I finally figured it out.
I'm going to get this anyway, I didn't think I'd like monster hunter world but it grew on me when I finally figured it out.
I agree. From videos and trailers, visual fidelity looks like the previous Monster Hunter Worlds, but the performance is rubbish by comparison for similar level of visuals.
Also there was a supposed leak of the upcoming AMD GPU running this benchmark at 1080p Ultra with FSR & framegen (what terrible benchmark settings).
It got a score of 36102 at 211.71 FPS. How does that compare to other GPUs (I know it's a dumb comparison given the terrible settings)?
I got 194 FPS at those daft settings on a 5700X3D + 7900 XT. Someone else got 210 FPS on a 5800X3D + 7900 XTX.
Seems both of us had massive VRAM usage (mine 18 GB, his 20 GB). Sounds like NVidia users aren't seeing crazy VRAM usage I think? Suggests the November drivers us RDNA3'rs are on are janky at best for this benchmark. I assume the 9070 XT benchmark leaker will surely have a more up to date AMD driver.
Really can't infer anything about the 9070 XT from this leak in my opinion.
I think it's probably because FSR's framegen is a little more memory-intensive than nvidia's DLSS framegen which recently managed to cut its memory footprint by a fair amount with the new DLSS4 framegen model.