Установить Steam
войти
|
язык
简体中文 (упрощенный китайский)
繁體中文 (традиционный китайский)
日本語 (японский)
한국어 (корейский)
ไทย (тайский)
Български (болгарский)
Čeština (чешский)
Dansk (датский)
Deutsch (немецкий)
English (английский)
Español - España (испанский)
Español - Latinoamérica (латиноам. испанский)
Ελληνικά (греческий)
Français (французский)
Italiano (итальянский)
Bahasa Indonesia (индонезийский)
Magyar (венгерский)
Nederlands (нидерландский)
Norsk (норвежский)
Polski (польский)
Português (португальский)
Português-Brasil (бразильский португальский)
Română (румынский)
Suomi (финский)
Svenska (шведский)
Türkçe (турецкий)
Tiếng Việt (вьетнамский)
Українська (украинский)
Сообщить о проблеме с переводом
Step 1: your cpu has to support AVX enable it in the bios
Step 2: delete or move "CrashReportDll" & "CrashReport" (THIS DIDNT WORK FOR ME UNTIL I ENABLED AVX)
I didn't do step 1 but deleting those 2 files and the game launched!
If a Cpu have only Avx but no Avx2 the game doesn't boot. I used an intel tool mod made to run the beta with my current cpu E5 1680v2 . The beta not sure for the full relise of the game require Avx2.
When I move the *mouse*, if the next input I hit is a *controller* face button, it will cycle through my inventory (as if I were holding L1 on the controller).
What's worse, it will do this regardless of the setting of Options -> Controller Button Configuration. That is, even if I don't have "cycle inventory" bound to L1+Square, this bug will cause Square to cycle the inventory after I move the mouse.
This bug makes it impossible for me to use SteamInput's gyroscope settings, or any other input method that emulates a mouse.
Please increase the gyro max sensitivity in the native gyro implementation. The current max is too low for experienced gyro users.
"20" sensitivity in game corresponds to about 4x true sensitivity (if I turn the controller 90 degrees in real life, I turn 360 degrees in game). Experienced gyro users can play at up to 12x or more, so the current max is at least 1/3 of what it should be.
- Link party kept getting disbanded before being able to invite to all enviroments
- Link party getting disbanded while trying to invite to all enviroments
- Without being in a Link party, if joining quest in lobbies with friends I get a communication error and kicked out of quest (communication error has occurred. EW_320cc // or Connection to session has been lost. S3091-0-0)
Moreover from lobby 60% of times I can successfully join quests of other players (not friends), while with friends the success rate is 0%.
They have no problem since they can join other players quests/other players can join them 100% of times.
My connection also is stable (have no problem playing other games like MH World or other online games) and I don't have any disconnection from the lobby.
One friend is playing from PC like me, another from PS5. I tried to play with them separately (with either one of them) and not all 3 together.
All search engines take "mhw" as Monster Hunter World. [1] Excellent. So please, settle Capcom's official abbreviation for Wilds.
Players' community is vital for games' popularity. A lack of good abbreviation can cause their inconvenience.
Today
* The search for "Wilds" almost exclusively hits Monster Hunter Wilds.
* "MHWI" is likely to show Iceborne.
Because the word "Wilds" can mean many other things, in my very personal opinion the official one should be something like "mhwilds" or "mhwl". On the other hand Capcom could suggest players to call it "Wilds".
(MHWL means "mean high water line", a special term for the river/sea level, but it must be ok.)
Thank you very much for reading.
[1]: Even Steam Store search shows World for mhw, which does not accept typo.
System Hardware:
-CPU: Ryzen 9 5900x
-GPU: RX 6700XT (Yes I know my GPU is under powered compared to my CPU)
-RAM: 32gb DDR5 3200mhz
Adrenaline settings:
-FSR disabled
-AMD Fluid Motion Frames 2 Enabled with AUTO on subsettings
-Radeon Anri-Lag Enabled
-Radeon Enhanced Sync Enabled (better than VSync/FreeSync alone)
-AMD FreeSync AMD optimized
There is probably some more that could be done with adjusting the Anti-Aliasing settings, but this led me to run the game at 1440p High/Ultra settings at a stable 60-70fps before doing any graphical adjustments in game (shadows, reflections, particles, etc.). Your mileage may vary of course. I hope this helps for anyone running a similar rig/GPU.
I do hope that this game is better optimized for AMD upon release, as even with these settings I saw other graphical issues such as pixelization/dithering artifacts when moving past objects and similar ringing artifacts at times around the various NPCs (though tuning my GPU settings helped a smidge).
PS: Requiring FSR/DLSS to run your game at a stable rate is unacceptable. Pure rasterization without AI based tricks is what you should be aiming for. Activating FSR made for a worse experience overall.
At 1440 high settings I was barely holding 55 fps in camp. Saw it drop as low as 45 while running around.
50ps at best in open world. Closer to 40fps in fights with monsters like Chatacabra.
Saw it dip to 30 in a fight with Rey Dau. 1% lows could be below that.
Absolutely insane how god-awful its performing on one of the top 10 strongest gpus and cpus on the market.
My PC specs Ran this game with ZERO issues.
Processor 12th Gen Intel(R) Core(TM) i7-12700
Video Card NVIDIA GeForce RTX 3060 Ti
Operating System Windows 11
RAM 64 GB
Video Card is Old but she still Bustin' it out....
High Surface Quality causes holes in the terrain and geometry bugs.
Ambient Occlusion causes dark flickering.
VRAM estimate is approx 20% lower than reality, giving a false sense of expectations and leading to instability and crashes when VRAM runs out.