Установить 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 (вьетнамский)
Українська (украинский)
Сообщить о проблеме с переводом
Правила обсуждений
Пожаловаться
Read the post you are quoting which causes 88500201 and not a direct game crash..
Just do what i did. Do a full clean re-install, but Make sure you Backup your current savefiles from the Userdata folder. This is the only way to ensure that your MHR experience will be smooth again.
Hm... I keep that on observation for now.
So far it happen only when I played on my TV screen (via HDMI) with controller and/or on prolonged playtime (2+ hours).
So far never happened when I played on the laptop directly (with M&K). Tested launching the game, load up save file, immediately quit, rinse and repeat 3 more times and never got the Crash Report popup.
It doesn't really bug me because it's only a slight annoyance at best but hopefully the issue can be fixed.
Edit : It happened when playing on laptop directly, so it rules out the "second monitor" and prolonged playtime possibility (last session only played 1 hour).
In this thread there are contradicting statements. So it is a little hard to determine the source of the issue yet.
Okay it also happened when I'm playing with laptop directly. So I guess it rule out the "second monitor" and prolonged playtime (only played 1 hour on my last session). I think I'll do another troubleshooting, I'll try doing single player session a few times and see how it goes (I think the issue happened mostly when I'm playing multiplayer session before quitting). Also will try closing the game via Steam instead quitting in-game.
Otherwise like I said, not a big deal, not like the game crashed while I'm playing anyway, just need to click on Cancel if the Crash Report Tool decided to pop up (and it's not like it happened all the time).
I'll try closing the game via Steam instead the in-game Quit button for the next couple session and see it the issue also happen.
We both have Sunbreak, we've only had minimal issues before TU4, we did not participate in the free armor thing, and we've yet to mod the game.
The most promising approach so far is the mentioned DLC trigger.
Zura janai, Katsura da! wrote it did not work for them.
Another player who tried that wrote it worked for them.
That is currently where I put my focus on. So if you did try the DLC trigger method, please tell me your results.
In addition to that I am interested in what screen mode you use + which graphics drivers you are using whether they need to be updated or not.
Again. Hard to tell due to the contradicting statements.
These two did the same thing and got different results, which indicates it is no game thing but probably some external issue, hence the suspicion fells upon Steam.
Just tested. the crashes report appears even quitting through the tittle screen, so it was a coincidence after all. I'll try your method again, it's possible I did something wrong, and then test some more.
Let me explain how this works. You claim that due to the update, it has been giving you this issue correct? This also applies to the OP post too if he's here. Let us go back to the beginning real quick. Note how you guys said it was due to the update. The only "Anomaly"(anomaly is something that is not ordinary or doesn't belong) is either the Update or Denuvo or possibly something you shouldn't suppose to have.(possibly the velkhana palamute layer or mods) Now you have to go through those steps each and individually and eliminate them.
We know that the palamute layer was hidden and supposedly everyone should be able to have it so thats no problem there. Capcom just wanted to play some time limited game with everyone with first-come-first-serve thing so we can rule this out.
Denuvo has already been a thing since the beginning of time(not literally, but you get what i mean) so we can put this on the sussy list on standby.
Now the next one is the Updates version. First you go around ask if people are having the same issue and if you get replies that are mixed, then well....it will come to conclusion is that half those people including you did something wrong.
This next one is obvious and its Mods. I already explained my part on how to fix crash issues if you fiddle with mods. I gave a reply to the japanese person in the thread above.
So now we come to an answer that it is Denuvo right? Nope. Because If those people who are playing the updates just fine, are Exactly using Denuvo just fine. So if you get people who told you that they don't have any issues with TU4, this implies that Denuvo is also safe and was Not the cause of the anomaly crash issue.
This is something between you and your PC specifically your own files. Perhaps your directory of where you installed your Rise game folder. So now we come to the other solutions that i have panned out in this thread and recommended to do a full sweep clean uninstall While Also Backing up your Save Data somewhere. Be sure to go into the Steam/Userdata folder and backed up the folder number 1446780 somewhere else on your PC. And then uninstall Rise from steam. Also go back to steam user data and delete that rise save data too(because you already backed up right?). From there, it is as simple as just re-installing the game, launch the game once normally do the method to regain your save data back.
If this doesn't work, then it is clear that something in your pc is interfering with Monster Hunter Rise. Double check your gpu settings like nvidia control panel or task manager for any sussy program in the background running. Let me know how it goes.