DJ_Kovrik;n9699021 said:
Texture mods without cache files more likely will cause issues like blurry loading screens in dialogues and other glitches, so cache IS necessary. What means that wcc still necessary, at least until Wolven Kit release.
If you removed *some files* you can't say that things work okay
You've got just partially working mods. It's much easier to keep that mods not merged like
XshI0u said, just merge all other stuff. And btw ModKit creates TGA files for modders, the game does not load it actually. If you got tga for xbm file it means that wcc succeed with that particular file uncooking.
Things work okay as far as merging "non-merable" packs goes. At least I feel like I learned something from personal experimentation and I think those "Texture-Group-Export" packs are not 100%-unmergeable. When you get WCC errors, the whole "merged anyway" is not exactly so as
XshI0u pointed out. You can actually lose texture files from mods that were properly uncooked (Better Oaks, HDProject Reworked) when a "problematic" packs are uncooked along with them. I am not 100% certain that not uncooking does not yield the same result. I think it's worth finding out for sure if that is the case, but I don't know how to test it.
I have not had any blurry screens and performance has been significantly better when all those conflicting, problematic textures were removed and bundle files replaced texture cache files. Bundle files with textures in them are MUCH bigger than equivalent texture.cache files. They may very much bundle that texture cache, but with reduced compression, which may actually help performance - my hypothesis, no real way to test it yet. Unlike before, uncooking them produces 0 errors now regardless of whether I do so with Mod Merger or W3 Oven.
In my experience, merging any texture pack that results in WCC errors related to "texture-cache", "out out of memory", and "corrupt files" is more than likely to cause problems, even if they are not obvious, like UHDP pack supposedly "merging, regardless of errors" at the cost of losing textures from other texture packs If it wasn't for
XshI0u and comparing merged texture packs to their un-merged parts, I would never even know and yes, there IS harm in not knowing.
How do I turn these blob bundle files into texture packs? I have only issue with them - size. My Mods folder is now 14GB instead of 4-5GB...
EDIT: Custom-editing texture packs has other benefits too. For example, COMPILATION pack has some bugs, some not-so-great textures, etc. UHDP is far from perfect and some of its textures drastically lower performance. Its only best to keep the whole package if the whole package is working or if you like the whole thing
.
UHDP merging still causes errors sometimes, but its random and this time its related to some "[Error][Core] CRawFileWriter write error: requested XXX bytes, sent 0 bytes in file '' and sometimes Mod Merger/WCC freezes/hangs during Metadata creation, even if one is created and when that happens - W3 does not load. I wish there was more info about all these particular WCC errors and cases. For some of us, "Just merge and play" doesn't cut it. I mean you had to dig up info to know what you know now, didn't you?