Monster hunter crashes after the splash pages

[Fixinater]

So after the capcom logo and other logos during start up, the game crashes (metal gear sound plays just before) Any help would be most appreciated.

Special K log: https://pastebin.com/uauY018T
Crash log: https://pastebin.com/MmwrtXAL
Modules log: https://pastebin.com/EyDZARVi

[JBeckman]

Does it work without SpecialK and if so does it work with SpecialK if you rename d3d11_shaders.ini?

From what I'm hearing the last patch from yesterday broke compatibility with some systems which so far looks to be NVIDIA specific but it's being looked into by the developers.

It could also have strengthened and improved the various anti debug and cheat triggers and code for that which the game is using quite a number of these code areas.

I tested the game myself and it still worked but I noticed that 0.9.25.11 which I was using for the game seems to have stripped out the specific Monster Hunter World settings and profile focusing instead on Dragon Quest XI entirely so it's working as a generic SpecialK title now with no further enhancements.

[MonsterHunterWorld.CPU]
KillAntiDebugCode=true

That in DXGI.ini set to false if they have changed the code could also help if this part of the game was changed with the latest patch but I still need to look into that though it doesn't seem to have been altered notably thus far from my findings.

[Fixinater]

The game works without Special K just fine. Rename the ini to what? I'm sorry I'm being a newbie with this.

[JBeckman]

d3d11_shaders.ini renamed to anything else. d3d11_shaders_.ini for example.

One of the shader entries in it doesn't play nice with some of the game settings and that causes the game to break and possibly crash so that's a common solution although I'm not 100% sure which setting is interfering but I think it's the temporal anti-aliasing.

The shader would otherwise remove the dark corner outlines which is used for a vignette effect but it hits some other effects too including depth of field and temporal anti-aliasing.


For the debug setting in the config file that was used to work around the existing anti-tamper code the game which could otherwise interfere with a number of different systems.

The very first one is a integrity check just after the game starts up near the splash screen, usually you see the message here that it's looking for DLC and it queries the Steam API.

If that code gets activated the game will crash and that looks to be the case here but the problem then is finding what is causing this.


So that's why I suggested removing the shader modifications and also the anti-tamper code.
First by renaming d3d11_shaders.ini to just about anything else, secondly by disabling the setting in SpecialK via dxgi.ini for the anti tamper code itself by changing =True to =False here.


Kaldaien himself from some of his recent posts can't get into the game anymore either (Anti-tamper is being activated from something.) but that was before the patch yesterday which could have altered things even more.
(Pretty much stopping any further development for now until that gets resolved.)

It doesn't seem to be the ongoing issue with some systems not being able to start the game at all though since that would happen even with SpecialK.

[JBeckman]

Far as the whole anti debug and anti tamper code in the game itself goes there is last I read up about it 280 some separate checks in the game.

The majority of these concern item and data manipulation which SpecialK does not interfere with since it's anti-cheat related.

However a few of them concern Steam API, integrity, DLC content and more such as the check as the game is started for DLC licenses via Steam and ownership for this content and that's when the game gets into a crash routine until this can be resolved.

That's what one of the settings in SpecialK tries to alleviate but if the patch has changed this then it might get flagged instead, same with manipulating the game shaders or hooking into Steam API itself.


This setting can also be used in SpecialK's ini file which here it should be DXGI.ini

[Steam.Log]
Silent=true


This disables almost all Steam functionality and might bypass the error but without SpecialK being able to utilize it's various Steam related settings at all.



EDIT: And I see the game just updated again, must be a fix for the previous problem where it didn't work at all for some users.

[Fixinater]

Sorry, so many things happening at home. I can't find d3d11_shader.ini anywhere.

EDIT: I don't think I ever downloaded the Reshader.

[JBeckman]

Perhaps it was updated and some of the files were changed?
https://github.com/Kaldaien/SpecialK/releases

Yeah it's me being out of date with the development of this version of SpecialK. :)

While d3d11_shaders.ini can be used for the custom ReShade .dll it was also used to adjust shaders such as toggles for vignette and depth of field but I assume then that since this was reported as being problematic it must have been removed in some later release and is no longer a concern at all.


Well it removes the shaders from the equation at least leaving only the config file and something in that or at worst a compatibility issue with the patched version of the game and if Kaldaien can't get it working on his end that effectively ends further development and updates unless it's resolved probably from a future update to the game but that's a pretty big if with some of these custom protection codes unfortunately.


That only really leaves opening dxgi.ini and testing if disabled either the workaround for this or the Steam functionality could work.

[Steam.Log]
Silent=true

[MonsterHunterWorld.CPU]
KillAntiDebugCode=false


And if neither of those help then I'm not really sure what it could be other than something having changed with the game itself.

I'm going to have to see what else I can find if anything but it's starting to look like a bigger compatibility issue if nothing else is working and that could be problematic to resolve.

[Kaldaien]

Sheesh this thread is confusing. I thought it was one person talking to themselves.

Unfortunately, this is the same problem I have. It's caused by the NVIDIA driver and the game's anti-tamper. You can get through a few of the title screen images, but it's going to crash before the DLC checks.

[Fixinater]

Thanks for the help anyways, I'll probably turn Special K off for monster hunter. Maybe things will change for the mod in the future. Then, I'll try again.

[CoolSpirit]

not really a big thing, but had to uninstall specialK mod after the glitchy reshade (sometimes it works, sometimes it doesn't) so hopefully things will get smooth in the future, looking forward to it as well.

[JBeckman]

Originally posted by Kaldaien:

Sheesh this thread is confusing. I thought it was one person talking to themselves.

Unfortunately, this is the same problem I have. It's caused by the NVIDIA driver and the game's anti-tamper. You can get through a few of the title screen images, but it's going to crash before the DLC checks.

Wait wasn't that specific issue fixed by the current update?
Maybe not entirely, could be that it needs some specific NVIDIA driver too or some other thing due to how sensitive it seems this anti-tamper actually is for certain changes.

And yeah we both use the kitty slime from Slime Rancher so I guess from the avatars alone it looks a bit funny, I should see what else I can find there. :D


EDIT: That should be fine.