PERFORMANCE TIPS
If you want to improve your game performance stability then you must do some sacrifices. Are you ready? Before doing anything please read this below information and make your own decision and take it with a grain of salt.
***if you haven't tried these graphic card tips (Nvidia)(AMD) yet be sure to give it a try.
***if you haven't tried these graphic card tips (Nvidia)(AMD) yet be sure to give it a try.
Step 1 : Uninstall unnecessary Mods, Keep it cleans (whether it's a Wearable Mods or Studio Mods). if you're using BR you are cluttered with mods and i'm pretty sure you don't want them to eat your space and slow your load times. so you can try to find them by their author's folders. Easy way of locating is to find the Original mods and see folder's structures. it's a hassle but it's worth it especially if you have low specs.
Step 2 : Have too much Character cards, easy step just take them out keep the ones you're using.
Step 3 : Disable unnecessary plugins to improve game performance. so here are the list of what each plugins do and you can consider if you should disable them. (i will only pick the plugins that known to be performance eater only). To disable : change it to XXX.dll.disabled to disable it don't delete it entirely you can put it in another folder if you don't want it your plugins folder, you might need them again sometime if you feel like it. you can find mods shortcuts in : Userdata/modprefs.ini.
you can see your FPS by enable it in setting once you in the game.
1. Gamechanger.dll : POV(first person mode), Animations/Facial expressions Randomizer, Ass physics, Camlight etc... Shortcut : N
Alternative is using FPS Counter plugins with more information on screen
2. ProjectHighHeel.dll : DHH or High Heels plugin, Adjust character pose with FK or IK, Post processor in main game and studio. Shortcut : P ***you can disable it via Launcher (if you're on BR) or change ProjectHighHeel.dll to ProjectHighHeel.dll.disabled
Off
3. Disable DHH Post Processor : Since we're going to use PHIBL instead (Highly recommended because you can use both in main game & studio). disable it so the two post processor don't conflict with each other.
4. ShortcutsPHS.dll : This is a very useful studio post processor plugin yet underrated not many people use it and it's a bit complicate to new users. i always use it since PHIBL can't provide what i need. But Disable it will improve FPS a lot. Shortcut you can find it in Plugins\ShortcutsPHS\ShortcutsPHS.xml.
Step 4 : Disable preview thumbnails of mods to improve load times (whether you're using BR or not) the folder is in abdata. Now take thumnbnail_R folder out of the game maybe put somewhere that can be easily accessible because you gonna use this method instead of preview it inside the game. if you're fancy like me you can do this. but it's a lot of hassle (not for me, i don't have that much mods anyway, but if you're using BR which contain a lot of mods) also you can make your own preview of HS mods you installed since the HS Coordinate doesn't work for PH anyway (there is a workaround though. refer to Use HoneySelect mods inside Playhome on HS Wearable mods to PH, Step 4) and it won't show preview inside of the game, it's not supposed to because HS mods and PH mods are built differently. Studio mods don't have preview unlike HS2 or Ai.
Check out this tip from NX98304 : [ Bonemod & the issue with colliders ]
" I don't know how this info is useful to others, as I think not many people play with extensive bonemods - but - after 2 whole days of tracking and profiling KKABMX, I think I cracked the bonemod performance issue.
It has almost nothing to do with bone hierarchy, and it certainly has nothing to do with playing the character animation (say during a H position) + bonemod leading to recalculation of the bone transforms. They are being updated per frame during any animation - adding a bone modifier on top of that should be trivial, even if you do it 104 times (all the adjustable bones) per frame.
It has to do with Unity's internal interaction when you apply Transform.localScale, it will trigger an update to associated colliders/hitboxes. What's interesting is that even though updating hitboxes is somewhat heavier than just simply updating the Transform scale, even this is not the core issue.
Not all colliders will go haywire. I haven't nailed down the reason behind it, so there will be some bones that has scale modifier to slow down your FPS, but not all bones that has scale modifier."
TL;DR
The easiest solution so far is disabling ALL colliders. (search the bonemod menu for "hit_")
Further testing shows the most usual colliders to reduce size are:
hit_Foot_L/R02 (suggested scale: 0.1)
hit_Hand_L/R (0.2)
hit_ArmLow01_L/R (0.2)
hit_ArmUp00_L/R (0.5)
hit_LegLow01_L/R (0.2)
hit_LegUp00_L/R (0.2)
hit_sakura_head (0.6)
hit_Neck (0.6)
hit_Spine03 (0.7)
"Note, none of the colliders related were named with "cf_hit_xxxs..", always only start with "hit_"; Also start testing with the leaf bone's colliders seem to be most effective, e.g. Foot, Hand or Head. The suggested values differ based on how excessive your bonemod is, but you can start from my suggestions."
Other articles:
Comments
Post a Comment