Monster Hunter Wilds

Monster Hunter Wilds

Ver estatísticas:
Vertex explosions?
Just look at it go!
https://www.youtube.com/watch?v=hw9qR431Rhk
anyone else having this issue?
EDIT: For anyone who finds this thinking their GPU is dying/ unstable,
I was able to find a consistent spot to test lowering total power threshold and underclocking and found it had no effect. seems to purely be something wrong with the game. I underclocked -300MHz (well within the cards stable range) and saw no change. I also reduced power threshold down to 55% and saw now change.
for anyone who wants the spot to test it was right after the everforge fails to light if you run southwest just up to the bridge before the game stops you.

EDIT2: I have been using a new fix that has resulted in my not seeing any vertex explosions for approx 5 hours of gameplay.
in the config.ini located in the install folder, change AllowMeshShader=Enable to
AllowMeshShader=Disable. Not my find, someone else posted it on the master troubleshooting thread.
Última edição por OneFishSunfish; 2 de mar. às 7:17
< >
Exibindo comentários 1626 de 26
Grout Muncher 5 de mar. às 13:29 
in my experience medium mesh quality still has this issue, but only in one spot. There's a specific rock in the plains that still does this consistently. No matter where I am in the zone if I face towards that damn rock my screen becomes origami.
Escrito originalmente por Grout Muncher:
in my experience medium mesh quality still has this issue, but only in one spot. There's a specific rock in the plains that still does this consistently. No matter where I am in the zone if I face towards that damn rock my screen becomes origami.
if you disable mesh shader in the config does it stop?
Forcing DirectX11 in launch options properties fixes it completely for me. -force-d3d11 -dx11 in launch options. GPU seems to work a little harder in dx11 but i'll trade that over vertex explosion errors any day.
D. Flame 5 de abr. às 15:17 
Did this ever get fixed? Still happens in the benchmark and in Dragon's Dogma 2.
Escrito originalmente por D. Flame:
Did this ever get fixed? Still happens in the benchmark and in Dragon's Dogma 2.
i have yet to remove my posted fix but for you I will run some tests.
Glimmer 6 de abr. às 11:28 
Been in the game since release, unfortunately...
D. Flame 6 de abr. às 17:44 
Escrito originalmente por OneFishSunfish:
Escrito originalmente por D. Flame:
Did this ever get fixed? Still happens in the benchmark and in Dragon's Dogma 2.
i have yet to remove my posted fix but for you I will run some tests.
I tried your fix in the benchmark, and it did not work. I tried it in DD2, and it did not work:

DD2:
https://youtu.be/RBAjb4xqs5E
https://youtu.be/-1mxXApDAy0

And I don't own MHWds to test it, but I really don't want to buy it, get past the 2 hour mark, then run into the issue again.

It's kind of ridiculous that Capcom themselves have not patched the issue officially.
Escrito originalmente por D. Flame:
Escrito originalmente por OneFishSunfish:
i have yet to remove my posted fix but for you I will run some tests.
I tried your fix in the benchmark, and it did not work. I tried it in DD2, and it did not work:

DD2:
https://youtu.be/RBAjb4xqs5E
https://youtu.be/-1mxXApDAy0

And I don't own MHWds to test it, but I really don't want to buy it, get past the 2 hour mark, then run into the issue again.

It's kind of ridiculous that Capcom themselves have not patched the issue officially.
the config.ini change didn't do it for you?
D. Flame 7 de abr. às 12:35 
Escrito originalmente por OneFishSunfish:
Escrito originalmente por D. Flame:
I tried your fix in the benchmark, and it did not work. I tried it in DD2, and it did not work:

DD2:
https://youtu.be/RBAjb4xqs5E
https://youtu.be/-1mxXApDAy0

And I don't own MHWds to test it, but I really don't want to buy it, get past the 2 hour mark, then run into the issue again.

It's kind of ridiculous that Capcom themselves have not patched the issue officially.
the config.ini change didn't do it for you?
sadly not
Escrito originalmente por D. Flame:
Escrito originalmente por OneFishSunfish:
the config.ini change didn't do it for you?
sadly not
do they always happen in the same place?
if you wipe your directX shader cache and the shader cache in the games files do they persist in the same place as well?
D. Flame 23 de abr. às 13:24 
Escrito originalmente por OneFishSunfish:
Escrito originalmente por D. Flame:
sadly not
do they always happen in the same place?
if you wipe your directX shader cache and the shader cache in the games files do they persist in the same place as well?
I reinstalled the game on a fresh OS install, and it still did it in DD2. I can't test anymore since I uninstalled again to make room for games that I can and do play.
< >
Exibindo comentários 1626 de 26
Por página: 1530 50