req Wuthering waves

[Scarecrow03]

42 minutes ago, IncogACC said:

 

Why does literally everyone just stop at saying "Mod broke" without providing any further explanation or screenshots?

Believe it or not, but there is actually more than 1 singular way that a mod can break and the various ways in which a mod can break will require various different solutions, not to mention that not all breaks are caused by updates and several seem to be caused by user error when trying to fix them which only leads to even more confusion.

Can you guess why I don't answer skill issue "mUh MoD bRoKe FiX iT fOr Me" posts anymore?

 

...Sorry, that was uncalled for.

 

When you say your mods are broken, I don't know what you mean by "broken."

Is it a texture loading issue?

Is it a mesh issue?

Is it to do with camera distance causing mods to unload or bug out?

 

Have you tried redownloading the mod and using the fixer on a fresh copy?

Did you tick the "Stable textures" option without knowing what it does? (Seemingly every clueless dumbass ends up doing this and wonders why their shit doesn't just work)

Did you use 2 different fix tools back to back?

 

The most likely case and cause is that you have texture issues which are caused by TSR conflicting with normal hash-based texture replacement and the solution is just to pick one method and use ONLY that instead of overlapping them. But without a screenshot or an explanation I can only guess at what your issue and solution is.

 

I might be in a slightly bad mood 'cus I just lost my 3rd 50/50 in a row after going to full pity and for the first time since the games release, I now have to skip a character I like

Im no expert but i dont try multiple fixes. I only use moonholder fix and before i tried the sable texture i made a copy of all the mods so i can revert back. I haven't tried downloading the mod again because they are really old from a year ago which i have been fixing with moonholder until now. Since 3.5  i got all mods to look like rebecca, i dont know why lucy is on the floor, she wasn't like that yesterday. So i kept waiting until version 3.6 arrived and i tested your mod and worked but mine still looks like rebecca even tho i used the moonholder fix without changing settings. Rover works on title screen but in game she has black skin. I understand your stress level so i didn't want to bother you much. I haven't done stupid sruff and everytime I try some i revert back because i have seen you talking about using multiple fixes and making it worse. So if my mods cant be fixed with moonholder i dont think i can go to each mod and edit something which i dont even know what would that be. In version 3.5 it was camera distance. Now even camera super close on LOD Bias on ultra doesnt load the mod correctly. I honestly believe its a stupid fix because they all stopped working at the same time as always which was fixed by moonholder in the past. The only thing i did different this time is that i used moonholder version 3.5.0 and then used 3.6.0, i didnt notice there was a 3.5.1 but i dont know if thats what caused all this

Edited 3 hours ago by Scarecrow03

[Scarecrow03]

1 hour ago, IncogACC said:

 

Why does literally everyone just stop at saying "Mod broke" without providing any further explanation or screenshots?

Believe it or not, but there is actually more than 1 singular way that a mod can break and the various ways in which a mod can break will require various different solutions, not to mention that not all breaks are caused by updates and several seem to be caused by user error when trying to fix them which only leads to even more confusion.

Can you guess why I don't answer skill issue "mUh MoD bRoKe FiX iT fOr Me" posts anymore?

 

...Sorry, that was uncalled for.

 

When you say your mods are broken, I don't know what you mean by "broken."

Is it a texture loading issue?

Is it a mesh issue?

Is it to do with camera distance causing mods to unload or bug out?

 

Have you tried redownloading the mod and using the fixer on a fresh copy?

Did you tick the "Stable textures" option without knowing what it does? (Seemingly every clueless dumbass ends up doing this and wonders why their shit doesn't just work)

Did you use 2 different fix tools back to back?

 

The most likely case and cause is that you have texture issues which are caused by TSR conflicting with normal hash-based texture replacement and the solution is just to pick one method and use ONLY that instead of overlapping them. But without a screenshot or an explanation I can only guess at what your issue and solution is.

 

I might be in a slightly bad mood 'cus I just lost my 3rd 50/50 in a row after going to full pity and for the first time since the games release, I now have to skip a character I like

The back of her leg and other colors are weird. I uploaded the file in case you want to detect where is the error. I tested your mornye mod you uploaded recently and it works. I dont know if i could copy the fix from your mod to mine. But like i said, im no expert so if its too complicated dont worry, i just keep downloading new fixed mods from you

Mornye_Ocean_Pixie_v1.3.3.7z

[Wicy]

anyone knows why this is happening on hiyuki 2nd lib ? 

i tried with empty "Mods" folder before but still same
 

 

 

[starmax123]

7 hours ago, IncogACC said:

Probably because of the overlap between TSR and hash-based texture replacement, pick one and disable the other.

 

That means either removing all the RabbitFX lines, or using notepad replace function with ctrl + h to change "this = Resource" to ";this = Resource"

I released it this way because there are plenty of people who refuse to use RabbitFX, so doing it this way stops them from being forced to while still leaving the framework there for people who do use TSR like me.

You are awesome, this fixed it for me!

[IncogACC]

1 hour ago, Scarecrow03 said:

The back of her leg and other colors are weird. I uploaded the file in case you want to detect where is the error. I tested your mornye mod you uploaded recently and it works. I dont know if i could copy the fix from your mod to mine. But like i said, im no expert so if its too complicated dont worry, i just keep downloading new fixed mods from you

Mornye_Ocean_Pixie_v1.3.3.7z 9.49 MB · 0 downloads

If the extent of what you're willing/able to do is using the Moonholder fix, then legit just redownload the mods and run them through the fix using the derivative hashes option.

I don't care how old the mod is, Moonholder fix has been around for a long time and it has hash memory, you're showing me a Rebecca mod and Moonholder fix has obviously existed much longer than she has so you're probably fine to use it for most of your mods even if they're ancient.

 

Everyone should read this so you dumb fucks in the back, listen up as well.

When using the Moonholder fix, you SHOULD be picking either derivative hashes or Stable textures, and you should be using a fresh copy of the mod.

Both of these options exist to deal with LoDs, texture LoDs that can no longer be forced via engine.ini due to Kuro locking down the options.

 

Derivative hashes adds extra TextureOverrides with lower LoD hashes in order to load all your textures regardless of which LoD is being used.

TSR bypasses the need for hashes entirely by loading directly into the slots, but TSR requires a modicum of brain power to not fuck up, so for like 99% of mod users who probably shit themselves at the idea of touching an .ini file, use the derivative hashes option. If you do that, then previously working mods will be fixed.