Main file of the mod updated for HD Pack compatibility. Disable, then delete the old file before installing the new version.
IF YOU'RE HAVING ISSUES WITH THE MOD
make sure you're on the newest version of both Fluffy and REFramework. That means getting REF NIGHTLY from github.
make sure you installed REF correctly. Only copy the ONE dll file you're supposed to, as per instructions
uninstalling the mod should be done via Fluffy. If, for some reason, Fluffy fails to remove the mod for you, you're supposed to delete the mod files from the game folder. Deleting them from Fluffy's backup folder does not remove the mod. You need to delete the .pak patch files from your game install folder. There will be several of them, becuse Fluffy adds empty dummy files ahead of the actual mod .pak. That is done to prevent conflicts in the future.
it is technically possible to install this mod manually, but that means that you will be on your own regarding conflict resolution with different mod files and future game updates. For that reason I will not be providing any kind of support for that situation. If you can't already do it yourself, you should not be attempting it. This is an issue specific to mods that affect textures, that's why you can't drag and drop this mod like you would other mods you might already have.
there is nothing in the mod that could crash your game. If installing it is giving you crashes, either your REF isn't working correctly or you installed it wrong. Every file that's edited by the mod is contained within the mod.
neither verifying the game or reinstalling it will clear additional files added by mods. Steam only knows to handle files that are meant to be in the game. If you reinstall your game you are not removing mods, and you are not removing REFramework. To do that you need to manually clear the corresponding files from your game's install folder.
Not the mod's fault, it's just textures. Either REF is loading it wrong or it's installed wrong. Sorry I can't be more helpful, but there is nothing in the mod I even could fix, it's just image files and it works perfectly fine on my end.
I don't know if I'm the only one, but I'm having problems with this particular mod, it gives me crashes, I tried it, since I don't use too many, they are related to GPU failures, but they started happening to me recently, I had been using it without problems since you released the fix for the HD textures.
Several people have had GPU driver problems with the mod on AMD hardware. Looks like something about how REFramework loads textures, or .pak files in general, but seems specific to AMD. Nothing I can do about it, sadly. Either keep updating REF and hope the next version fixes it or report the issue to REF devs.
The fix for the HD Textures doesn't seem to work, game mostly crashes on save load, sometimes during playtime, I'm on AMD. The error is a "DEVICE_HUNG".
Also, I doubt it's the mod's fault, but this mod cannot be removed, I disabled it on Fluffy, made sure the file was not on the folder, but the texture does not goes back to vanilla, and the game doesn't stop crashing, I was forced to reinstall and be careful to not enable it again. I would think it's a REFramework issue.
Update Fluffy as well as REF. Don't rely on Nexus pages, get actual nightly builds of REF. Sometimes Fluffy messes up its file handling and things need to be removed manually. Nothing you mentioned has anything to do with the mod. If a texture isn't reverted, then you didn't remove the file, simple as that. It cannot be loaded from thin air. Fluffy adds several dummy .pak files alongside the mod, you probably only removed some of them. DEVICE_HUNG is a GPU driver issue most likely, so I would look to either an issue with your drivers, REFramework or the game itself.
The crash is not my drivers fault, tho AMD has some problems on this game for sure, I only had this crash with the mod, nowhere else.
About removing, another comment talked about removing some .paks on the game's folder after uninstalling too, that would've done the trick I'm sure, I wasn't aware of this, bad of a mod manager but nothing to do with the mod.
Also I had the most up to date ReFramework, in fact even tried with an older version, always crashing. I even clean reinstalled my drivers, I spent like all morning on this issue.
I don't doubt it's an AMD issue, but many folks on the comments comment about crashes.
Finally! i've just reinstalled my gpu drivers, the game several times, and looking up the issue non stop for hours thinking it was my end, only now i realized it's this mod and it's not just me having this issue.
You said you "made sure the file was not on the folder". What it sounds like is that you deleted the file from Fluffy's BACKUP folder. Of course that wouldn't affect the mod files still being in your game. The .pak files in the game install folder you're talking about are the mod (plus dummy files added by Fluffy to handle version control).
I understand that I got the mod removal wrong, but this doesn't change the crashes when the mod was in fact installed.I don't think it was the backup folder, but as it was wrong anyway, it doesn't matter, I think we should focus on the crash that happens anyway. It may not be your mod, I completely believe if it's an AMD/REFramework issue, or something else, but as it happens with the mod, it's here I come to document the problem, we don't need to fight or get angry.
+1 this, since I've had the mod uninstalled i haven't had a single issue, idk why it's happening or what the true course is but all i do know is that if the mod isn't installed i don't get crashes
I'm sorry but there is literally nothing about this mod that could cause crashes outside of improper installation. Every changed reference points to a file within the mod. It's not touching anything that could break. I can't troubleshoot REF or Fluffy beyond listing what I know to be the correct way to install the mod. Maybe it's something with Fluffy messing up on your machine (Fluffy bug or permissions issue or any number of other things that I can't confidently speak about), maybe your version of REF is out of date (read: not the newest nightly off github. Newest full release may not work as it's considerably behind.) or you installed it improperly (copying more than just the dinput8.dll into your game folder can cause crashes, for instance). It might even be a bug within REF that makes it mess up on your hardware configuration. Or maybe you have resitual files messing things up in your game files, since I believe you both reinstalled the game and removed the .pak files manually at one point. If that's what it is, the only foolproof way to reset it would be to uninstall the game *and* then manually delete the leftover folder and whatever's in it. I'm not trying to disregard your issue, there's just nothing I can do about it on my end outside of reiterating the correct instructions. I've had several people test it with my supervision and they had no issues.
i'm not trying to be rude, i'm just pointing out a potential bug with your mod, let me just say this, i've been playing fine all day today with 0 issues, i've got around 7/8 mods installed, most requiring REF and FMM, and even with the new update out today all the mods are working fine, 0 crashes, i just installed your mod again to try it out, i tried both with FMM and manually, and both times the game crashed, once i uninstalled the mods and played, everything was totally fine, this has been my own experience, yes everything is installed correctly and up to date, otherwise the other mods most likely wouldn't be working, the only issue i have had so far when isolating it, is this mod, so clearly something is up, again, i'm not trying to be rude, i'm just trying to be helpful.
Mods requiring REF and FMM doesn't necessarily mean they're loading the same way, a bunch of mods that don't add textures (that's the reason for this mod having to go through .pak files rather than loose files) list those two as a requirement for ease of use. Again, there is nothing I could possibly fix with this mod to make it work for you, because it's a simple texture replacement. If it was really broken on one machine, it would be broken on all of them, and it isn't. I can't tell what your issue is, but you're going to have to go through channels for REF and/or Fluffy to learn more and fix it. Maybe try the MonHun modding discord.
Yeah had the same issue. Had most up-to-date REF and Fluffy and it just crashed, all my other mods work fine though. Gonna assume there's some weird issue happening with AMD cards because it seems everyone reporting this issue is using AMD with either most up-to-date drivers or damn near.
That is very suspicious. Your reports would probably be pretty valuable to the people making REF and/or Fluffy (feels like a REF issue if it is tied to AMD, Fluffy just manages files)
40+ mods installed crashed on loading into a game...disabled all mods didnt crash..okay so it's a mod. Literally enabled reframework, catlib and your mod..crashed.
Enabled all mods but your's and no crash.
It's 10000000% your mod, to be clear it's the HD version.
TaranTatsuuchi what version of the mod was you using? i just tried what you said worked for you and installed 24.12.1 driver but the game still crashes with the mod installed.
The mod .pak contains only materials and textures for those materials. It physically cannot work on some systems but crash others. If something's broken, that isn't the mod. Several people are having issues on AMD cards, might be something with texture loading on that. Unless you want to buy me an AMD card I can't test it anyway.
All AMD here. Managed to load my save for a little bit *but it stopped working. it helps to have a more cutting edge version of REFrameworks which is not currently on nexus mods(Nexus vers: 01105 vs GitHub vers: 01116)
Might be a good idea to put the link to the repository in the description for future troubleshooting as a solution to the crashes. I, along with many others probably, didn't notice the exact phrasing of your replies in the feedback tab
Do we have any updates on this? still getting DXGI_ERROR_DEVICE_HUNG crashes on ReFramework Nightly 01132, Hash (9fda64e7562388ba353faa83c658bb31410b9fed)
I've been getting the same issues too. At first I was getting a black screen at the main menu and then I updated everything and verified the files through steam, installed and the mod and managed to get the normal main menu but as soon as it finishes loading after character select it gives me the DEVICE_HUNG error. I'm on AMD too so this is probably something to do with REFramework or Fluffy. A shame really, the mod seems so good.
Sadly it's still down to REF to sort this out from the looks of things. I imagine if multiple people who actually have AMD hardware reported it to them they might prioritize it. I don't have AMD so I can't even reproduce the problem myself, it's all on you guys.
omg i love this mod, also is there any way you could make a mod like this for armor? like some pieces of armor have monster material/parts that for SOME REASON they dont let you dye. anyways thank you and keep up the good work!
In theory, yes, it's a simple texture edit and I've seen at least one modder working on something like that. I won't be doing that personally unless there's something that's very obviously an oopsie by Crapcom, because I don't like there being a discrepancy between how my hunter looks on my screen vs how others see them.
102 comments
IF YOU'RE HAVING ISSUES WITH THE MOD
Fluffy MM and Reframework are on they latest versions
RTX 4060
i5 12400
Also, I doubt it's the mod's fault, but this mod cannot be removed, I disabled it on Fluffy, made sure the file was not on the folder, but the texture does not goes back to vanilla, and the game doesn't stop crashing, I was forced to reinstall and be careful to not enable it again. I would think it's a REFramework issue.
About removing, another comment talked about removing some .paks on the game's folder after uninstalling too, that would've done the trick I'm sure, I wasn't aware of this, bad of a mod manager but nothing to do with the mod.
I even clean reinstalled my drivers, I spent like all morning on this issue.
I don't doubt it's an AMD issue, but many folks on the comments comment about crashes.
Rolled back to 24.12.1, which I was on before, and haven't had another crash.
Gonna assume there's some weird issue happening with AMD cards because it seems everyone reporting this issue is using AMD with either most up-to-date drivers or damn near.
Literally enabled reframework, catlib and your mod..crashed.
Enabled all mods but your's and no crash.
It's 10000000% your mod, to be clear it's the HD version.
link to GitHub repository: https://github.com/praydog/REFramework-nightly
Most resent release as of writing this: https://github.com/praydog/REFramework-nightly/releases/tag/nightly-01116-46739929424a60ff8e9b429fdf53d1233bb1f655
Might be a good idea to put the link to the repository in the description for future troubleshooting as a solution to the crashes. I, along with many others probably, didn't notice the exact phrasing of your replies in the feedback tab
EDITS: *I spoke too soon
I'm on AMD too so this is probably something to do with REFramework or Fluffy. A shame really, the mod seems so good.