Ersh
patreon
Precision rework test
🕑 Added 2022-11-10 03:07:59 +0000 UTCHey,
It seems I'm done with the main rework, and my limited testing surprisingly resulted in no issues.
Active ragdoll is now only added for a short while on hit, any collisions are done on a duplicated skeleton that should not interfere with the game physics. It literally only collides with the Precision attack collision layer. Hopefully no more strange collisions during animations, no more load screen lockups, no more weirdness with frozen enemies etc.
I need some real gameplay testing done (because there's no way I didn't miss something) while I finish up other features and bugfixes.
I think the attack reach AI fix is included and functional, but has not been finalized yet. I haven't touched that part of the code for a while, I'm going to focus on it now while waiting for any bugs to surface.
Please report any weirdness and remaining issues. Bugs not related to the ragdoll, that have been reported on the Nexus, haven't been touched yet.
ACCURACY needs an update to be compatible, please remove Accuracy's dll while testing for now.
In other news, I'll be between jobs for a while, so I should have more energy to dedicate to modding!
Have a great day!
EDIT: New version, fixed some stuff. There are a few small new additions you might (not) notice, like a small cooldown per hit material; that should limit the annoying rapid hit sounds on walls etc. when there's a bunch of separate refs with the same material.
EDIT 2: Fixed creatures not hitting their attacks. Oops!
EDIT 3: Fixed a rare crash, fixed Dragonborn dragons not using the collisions from the .toml file (need to replace your current one. BTW that's apparently been a bug since forever), fixed the AI attack reach logic causing NPCs to prefer unarmed over short weapons. Also disabled the character bumper - this will let you get much closer to enemies. Let me know if you feel that it's a good change - I think it is.
EDIT 4: Fixed many things. Reworked recoil mechanics.
The current changelog:
- Significantly reworked the core of the mod. This should fix all the weird issues caused by active ragdoll at once, such as:
- Fixed load screen deadlocks
- Fixed frozen NPCs bugging out / not being hittable
- Fixed NPCs colliding with the player when they're not supposed to
- Fixed the player being frozen in race menu
- Fixed potential crashes
- Significantly reworked the weapon recoil mechanics. Now the recoil detection uses a completely separate collision which will make them more reliable than previously in some cases, and the collision is turned off shortly after the attack start (on the vanilla hitFrame) - so you won't get recoiled by hitting a wall at the end of your swing. Overall, they now make a lot more sense and are less annoying.
- Added a short cooldown per hit material so you don't get multiple hits when similar objects are close together. This significantly reduces situations like the tiresome rapid-hit sounds on wood/stone/metal. Movable and destructible objects are unaffected so you can still hit all the cabbages with one sweep.
- Added an option to disable character bumper. This lets you get closer to the enemy.
- Added an AI hook for the current weapon reach value. It will now use the calculated weapon length from this mod.
- The results of the weapon reach calculation are now cached instead of being recalculated every time
- Hitstops from NPC attacks are no longer applied to the player while in first person (caused bad camera locking). Hitstops from player attacks are unaffected by this change.
- Multiple received hitstops now have dimishing returns, as being hit by multiple actors at the same time could result in a stunlock of sorts which is not the purpose of this feature.
- Re-enabled attack water splashes that were mistakenly disabled at some point
- Fixed some rare cases where the weapon length calculation was returning incorrect results
- Fixed power bashes not being supported
- Fixed issues with the Slow Time shout
- Fixed the weird looking hit impulses on dragons
- Fixed DLC dragons not using attack definitions from the .toml config file
EDIT 5: Fixed a deadlock.
EDIT 6: Forwarded many changes from PLANCK's updates, added blending when adding and removing the active ragdoll and fixed multilple cosmetic issues. Impulses should look a lot better, especially when being bombarded by multiple attacks while attacking. Some tweaks to AI reach as well.
EDIT 7: Hopefully the last test version before release.
- Fixed incompatibility with plugins dynamically altering the skeleton
- Added weapon length overrides to the .toml file. You can use it to set a custom value for a weapon that is impossible to be calculated by the plugin (e.g. the mesh is just the handle, the rest is a dynamic VFX)
- The ragdoll is no longer added on impact to the player while in first person
- The AI hook now takes into account attack reach settings
- Hitstop/Hit reactions are no longer applied by hits skipped through the plugin API
Comments
Thanks! Will fix.
Daniel Mezentsev
1.9.7.7 was tested. Problem when fighting on the horse back you hit your horse, until it's eventually becomes hostile to you.
Kissshot7
Glad to help, and thank you for your efforts for maximum compatibility!
Oh thanks! I'm using a pretty general way of filtering out unwanted bones from the skeleton, the one from the mod must be set up differently from the ones I've tested. I'll see if anything can be done from my side.
Kissshot7
It conflicts with Mu Joint Fix by Arco748. If both are present, after the second time I load the save(also the reason I thought a new game fixes the issue), the skeleton will be duplicated only when the pelvis area is hit and not for other body parts, preventing attacks that didn't hit the pelvis area cause any damage.
Wait, what mod conflict? I do try to keep Precision compatible with everything.
Kissshot7
Ok, so it's actually a mod conflict with the 1.9.x Precision, since I know mod support is not your priority, I won't bother you with this, just wanna let you know there is no potential error causing the issue I mentioned yesterday!
Don't worry, I haven't done anything yet as I wasn't sure where to look. Maybe there's something wrong indeed, although your report was the first one with this issue. Hopefully that was a coincidence.
Kissshot7
And... I just start a new game and the issue's gone, so I'm guessing something is wrong with my ongoing save which is something I'd never expected since swapping back to the old version of precision works really well... Sorry for wasting your time if you have already taken the time to investigate. I will try to be more cautious next time I report anything.
Kissshot7
I think it's not, but I'll test more now. I'll back to you soon.
Hm okay. Not sure what's up then. Is that a particular animation?
Kissshot7
I usually play at 100~120 fps, and no, It didn't happen on relatively low framerates, since I rarely got fps drops.
Hmm. Does that happen on relatively low framerates?
Kissshot7
Well, I run into another issue now, sometimes the enemies are having a hard time trying to hit me. Like in a combo with 10 very fast-paced swings, they only hit me 2~4 times, and I'm pretty sure that every attack went through my body, but it happens extremely randomly, so I wasn't sure if it was a problem on my end only, and revert back to nexus version fixes this issue. Is there anyone having the same issue?
Beccamori
No freezes for me on 1.9.5 too thus far.
mpgeist
Same for me, no crashes tonight.
Kissshot7
It's indeed fixed now, thank you!
Yeah it should be fixed in 1.9.5, caught it today.
Kissshot7
I didn't know 1.9.5 dropped lol, thanks for reminding me brother <3
mpgeist
I was actually having this happen too, but I hadn't had time to go through logs or anything to try and figure it out. I'll try the new 1.9.5 version and see if that fixes it!
Kissshot7
Hi Ersh, It's me again. My game has frozen several times when using 1.9.4 version, I can't really figure out a specific reason as the freeze happened randomly, but it seems only happen the moment someone hit something in combat. I'm not sure if it's the issue in your plugin or if another skse plugin hooks the same function causes the conflict. But the issue's gone when I revert back to nexus version(1.1.8?). If there's any more info I can provide, please let me know!
Yeah, I will be focusing on that soon.
Kissshot7
Hey, Ersh! Thank you for the hard work and update, I presume 1.9.4 version is still not compitable with ACCURACY right?
