Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
MHW is a bit more taxing than DD2 was, but it's a good benchmark if you can/can't play MHW IMO. Both have built in features that can't be turned off. It's the reason some people's world textures didn't load in DD2.
nah DD2 is extremly much more taxing on CPU than Wilds.
I had like 20fps in the city of the game
In theory you should be fine, but the game during EA was found to be very demanding unless you are running current gen hardware so even the 10600k might not offer the best experience.
I didn't check at the playtest but MH:Worlds did rely heavy on cpu speed.
I asume MH:Wilds will be the same.
Can't really use fsr frame generation at that framerate, will be unplayable (still idk if it's supported for the 1080)