Sorry, I can't help you there. I tried updating my VC redistributable as well as downloading the version of this plugin that is on this site, but everything worked as they should.
The OAR API has not changed in 6 months, and neither has the template OAR plugin made by Ersh. If you believe this plugin is making your game crash, I suggest you report to Ersh at OAR page. Can you give me a link to where PO3 says logging does not work? I have not added any logging to the plugin other that what was already in the OAR plugin template, but I can still take a look if what he says applies to this plugin.
Logging for older SKSE plugins will write logs to the wrong folder, creating "<My Games>\Skyrim.INI\SKSE" instead of the regular log folder, "<My Games>\Skyrim Special Edition\SKSE". I can't find an instance of PO3 saying it, but according to this STEP forum post it started happening with the 1170 update, but only with plugins that make use of "SKSE::Log::Log_directory()". Logging still works fine however, just gets placed in the wrong folder.
Sorry. There's a bit too much trouble to support the old version. The proper way to fix the logging for Underdog is to update the Underdog conditions to use the new version of detection plugin, and then publish those new conditions as a new mod into nexusmods.
Hello, anyway you can add the fix for us 1179 GOG users, would simply have to add GOG at the end like so: "Skyrim Special Edition GOG" Hope you see this and can make it, thanks.
@elpuertorro Are you referring to the version for UNDERDOG? Updating that is too much work for an outdated version of this mod. (As a modder, I would also refrain from using mods that are clearly not kept up to date.) If you are having trouble but still want to use UNDERDOG, please edit the condition files in UNDERDOG to work with the new version of this mod (and hopefully upload it to nexus for others).
If you are having trouble using the main version, can you tell me what problems you are encountering?
Does this mod work (or is it necessary) if you don't use the entire UNDERDOG set? I only use the UNDERDOG - Death Animations OAR mod, not the main mod itself.
This plugin is only required for UNDERDOG if you're using animations that require this plugin. The UNDERDOG FOMOD will tell you in the description if this plugin is needed or not for that animation to play.
Hello, recently updated both plugin files (I use Underdog and DFFMA) and OAR throws this error. Any ideas? I've tried redownloading everything and double checked all requirements. On MO2 the detection plugin version is indeed 2.1.2 and 1.3.1-v2 for the underdog version.
When I disable the 1.3.1-v2 version, I get this empty initialization error instead.
Thanks for the report. Apparently OAR did not recognize "...-old.dll" as a different filename. (??????) (I guess I should've confirmed it works...) I changed the filename to "..._old.dll" and now it seems to work.
Hi i'm trying to install this mod because Dynamic Feminine Female Modesty Animations OAR needs it, and it shows me this, i had this happen before with a mod, but not it just shows me that nothing is the problem, only legacy files a previous version of OAR said a similar error, but the dynamic animations that i want to add wants this plugin at least 2.0.0 so i'm using the latest one also of course the animations wont play
Are you also using UNDERDOG? If you use that as well, you need both the main file and the version 1.3.1. Also make sure that you have the latest version of OAR.
I've seen the error about plugins before, but that time it clearly stated the name of this plugin. That's why I think there is something else wrong with your installation. Try entering the author mode and confirm that Dynamic Feminine Female Modesty Animations OAR is the mod that give you that error. Also double check the requirements of OAR. The version of C++ redistributable might have changed or something.
The other error likely has nothing to do with this plugin. Try to check what mod causes that by using the author mode and looking at the legacy part. You can also use Everything or the data tab of MO2 to look for the folder "meshes\actors\character\animations\DynamicAnimationReplacer\_CustomConditions\2000000196" that is giving you the errors. I'm sure the author mode of OAR gives you the required details to fix the legacy error thing.
Your problems are most likely due to Dynamic Feminine Female Modesty Animations OAR updating a little less than a week ago. Have you recently updated that mod, or did you install it from scratch? The mod page says that old user configs do not work with the new version, so those might be causing your errors. Try removing the user configs which are likely in the override folder of MO2. If that doesn't help, try disabling that mod and see if the errors disappear. If the errors do disappear, I suggest you ask help on that forum instead.
For reference, I tried updating my DFFMA to 4.0, and everything worked correctly.
Since the author of UNDERDOG - Animations seems to be taking longer than expected updating their mod, I decided to reupload v1.3.1 with a different name to make the installation easier. This way you can easily use the v1.3.1 and v2.1.2 of this mod at the same time.
Are you doing something with FNIS? You crashlog is full of FNIS_RootBehavior. You are likely using some animation / behaviour mod that is not compatible with FNIS or your version of skyrim (like LE animations). At least the crash seems behaviour related. (Behaviour is the conditions in which certain animations start playing)
AFAIK, pandora behaviour engine does everything Nemesis and FNIS does, even creature behaviours and animations, so it should be used on modern load orders.
Great work - managed to get it all working with my numerous animation mods after substantial amount of research into what version of OAR DP I needed. Thanks for your contributions
I've been suffering from mysterious CTDs for the past month. The only new mods I installed around the time the CTDs started were Dynamic Feminine Female Modesty Animations and Open Animation Replacer - Detection Plugin. The CTDs went away when I disabled Dynamic Feminine Female Modesty Animations, but in the scenes where the CTDs occurred, female NPCs always looked like male NPCs, so I think this mod might be the cause. I think the NPCs shown in the log are the ones I saw before and after the CTDs, but I'm not sure, so I'm attaching the logs.
There is no way that this mod makes your female NPCs look like male NPCs. That would point towards DFMA giving male animations to females, or being otherwise badly configured. I suggest you turn on Animation log in OAR, selecting the target NPC on console, and looking what replacer is applied to the NPC to make it look male. The CTDs are also unlikely to be caused by this mod since yours is the first CTD report in a long time. The crashlog also doesn't list my code in it. One potential cause for a CTD are bad animation files. For example if an animation lasts 0 seconds, it would be repeated infintely in one second causing a crash.
It was a translation error on my part that female NPCs always looked like male NPCs. I'm sorry. To be precise, the CTD occurred when a male NPC was looking at a female NPC. In any case, from what you said, I feel that it is unlikely that this MOD is the cause.
Somehow, your latest plugin (v2.1.2) does not work with Underdog Animation (https://www.nexusmods.com/skyrimspecialedition/mods/51811).
"Major issue detected by Open Animation Replacer..." came the warning. The warning gone when I revert to plugin v1.3.1. Not sure about the long term impact as I was just about to start a new game, but it's worth checking.
For those who got issues with OAR showing an error on startup, you gotta change up some files in the mod.
Open to mod in your preferred file editor, and go to<mod>/meshes/actors/character/animations/DynamicAnimationReplacer/_CustomConditions/ Inside, you will find tons of folders. Open this FOLDER (not any files inside, the whole folder) in any editor that is able to do multi-file search & replacing (I use IntelliJ, tho if i'm not mistaken Visual Studio Code can also do it). Hit Ctrl+Shift+H (VS Code), Ctrl+Shift+R (Intellij) or whatever your text editor uses, and search for the sequence `IsDetectedBy`. It should appear in a lot of `user.json` files from those folders. in every of those files where it appears, you need to replace it with `DETECTED_BY`, which is the OAR equivalent. Just use the "replace all" button.
This process may look something similar to this:
In the end, save all those files, and you should be able to start your game.
NOTE: the amount of files you got depends on which/how many animations you selected during the install. I don't have all selected, so you may have more files than me in that image.
They didn't have any of the options toggled under IsDetectedBy? I'm pretty sure you won't get correct conditions with simply that change, and there will be trash left inside the file, like wrong "required version" or subconditions. I would advice doing changes inside OAR overlay in-game while having both of my plugin versions installed. Being able to use OAR overlay is also a really good skill to have for installing other animations.
Just download the old plugin version 1.3.1 and add "old" to the file name. Repack it and install it ontop of the new one so it uses both dll files and still benfit from the new one. ZERO ISSUES DOING THIS.
Oh man, I have been getting this for a WHILE, only now realized it was Underdog Animations. Guess it started when I updated to this last version of Detection Plugin. Since Underdog Animations let you pick whatever animations you want from the pack, does anyone know exactly the ones that cause the issue so I can just turn them off on FOMOD?
Hmm. That does look like my mod might be the culprit. I added one new download to the optional files. Install that and if the game crashes again, send me a new crashlog. The file adds some extra data to crashlog that I need.
Also, what were you doing when the crash occurred? Going through a door or something similar?
Since I got another bug report about that, I fixed it (hopefully, not like I can test it). For whatever reason when looking up player, player was not found which resulted in that crash. I have no idea how that can happen when you are simply walking, and it never happened to me either, but I guess I should have been more careful when coding that part. You can never be too careful when it's about Skyrim.
180 comments
I tried updating my VC redistributable as well as downloading the version of this plugin that is on this site, but everything worked as they should.
Can you give me a link to where PO3 says logging does not work? I have not added any logging to the plugin other that what was already in the OAR plugin template, but I can still take a look if what he says applies to this plugin.
I can't find an instance of PO3 saying it, but according to this STEP forum post it started happening with the 1170 update, but only with plugins that make use of "SKSE::Log::Log_directory()".
Logging still works fine however, just gets placed in the wrong folder.
SSE 1.6.1170 or MO2 Now Making Skyrim.INI Folder? - General Skyrim SE Support - Step Mods | Change The Game
The proper way to fix the logging for Underdog is to update the Underdog conditions to use the new version of detection plugin, and then publish those new conditions as a new mod into nexusmods.
"Skyrim Special Edition GOG"
Hope you see this and can make it, thanks.
Updating that is too much work for an outdated version of this mod. (As a modder, I would also refrain from using mods that are clearly not kept up to date.)
If you are having trouble but still want to use UNDERDOG, please edit the condition files in UNDERDOG to work with the new version of this mod (and hopefully upload it to nexus for others).
If you are having trouble using the main version, can you tell me what problems you are encountering?
When I disable the 1.3.1-v2 version, I get this empty initialization error instead.
Apparently OAR did not recognize "...-old.dll" as a different filename. (??????) (I guess I should've confirmed it works...)
I changed the filename to "..._old.dll" and now it seems to work.
a previous version of OAR said a similar error, but the dynamic animations that i want to add wants this plugin at least 2.0.0 so i'm using the latest one
also of course the animations wont play
Also make sure that you have the latest version of OAR.
I've seen the error about plugins before, but that time it clearly stated the name of this plugin. That's why I think there is something else wrong with your installation. Try entering the author mode and confirm that Dynamic Feminine Female Modesty Animations OAR is the mod that give you that error. Also double check the requirements of OAR. The version of C++ redistributable might have changed or something.
The other error likely has nothing to do with this plugin. Try to check what mod causes that by using the author mode and looking at the legacy part.
You can also use Everything or the data tab of MO2 to look for the folder "meshes\actors\character\animations\DynamicAnimationReplacer\_CustomConditions\2000000196" that is giving you the errors.
I'm sure the author mode of OAR gives you the required details to fix the legacy error thing.
Have you recently updated that mod, or did you install it from scratch?
The mod page says that old user configs do not work with the new version, so those might be causing your errors. Try removing the user configs which are likely in the override folder of MO2.
If that doesn't help, try disabling that mod and see if the errors disappear. If the errors do disappear, I suggest you ask help on that forum instead.
For reference, I tried updating my DFFMA to 4.0, and everything worked correctly.
The first thing that happened after I tried to load my last save was a CTD.
Have all the requirements installed for both mods.
Would you mind taking a look at my crash log and telling me what you think?
Link: https://gist.githubusercontent.com/SeriousConcept1134/a2399996714565154e3479cb9225ce56/raw/665b63c4137ee89e72d24025f7ffdafc5be1bdfb/crash-2025-01-22-18-12-52.log
Any input you could provide will be greatly appreciated! ❤️
Thanks in advance!
You are likely using some animation / behaviour mod that is not compatible with FNIS or your version of skyrim (like LE animations).
At least the crash seems behaviour related. (Behaviour is the conditions in which certain animations start playing)
AFAIK, pandora behaviour engine does everything Nemesis and FNIS does, even creature behaviours and animations, so it should be used on modern load orders.
But thank you for your input, I'll try and look into that.
https://pastebin.com/TWNmg8kN
The CTDs are also unlikely to be caused by this mod since yours is the first CTD report in a long time. The crashlog also doesn't list my code in it.
One potential cause for a CTD are bad animation files. For example if an animation lasts 0 seconds, it would be repeated infintely in one second causing a crash.
"Major issue detected by Open Animation Replacer..." came the warning. The warning gone when I revert to plugin v1.3.1. Not sure about the long term impact as I was just about to start a new game, but it's worth checking.
No damage has been done to your save. Read the stickies in Underdog if you wanna use it.
download the v1.3.1 of Open Animation Replacer - Detection Plugin from the files of this mod page, it should be right below the most updated file
For those who got issues with OAR showing an error on startup, you gotta change up some files in the mod.
Open to mod in your preferred file editor, and go to
<mod>/meshes/actors/character/animations/DynamicAnimationReplacer/_CustomConditions/
Inside, you will find tons of folders. Open this FOLDER (not any files inside, the whole folder) in any editor that is able to do multi-file search & replacing (I use IntelliJ, tho if i'm not mistaken Visual Studio Code can also do it).Hit Ctrl+Shift+H (VS Code), Ctrl+Shift+R (Intellij) or whatever your text editor uses, and search for the sequence `IsDetectedBy`. It should appear in a lot of `user.json` files from those folders.
in every of those files where it appears, you need to replace it with `DETECTED_BY`, which is the OAR equivalent. Just use the "replace all" button.
This process may look something similar to this:
In the end, save all those files, and you should be able to start your game.
NOTE: the amount of files you got depends on which/how many animations you selected during the install. I don't have all selected, so you may have more files than me in that image.
I'm pretty sure you won't get correct conditions with simply that change, and there will be trash left inside the file, like wrong "required version" or subconditions. I would advice doing changes inside OAR overlay in-game while having both of my plugin versions installed.
Being able to use OAR overlay is also a really good skill to have for installing other animations.
Skyrim SSE v1.5.97
CrashLoggerSSE v1-14-1-0 May 18 2024 23:00:58
Unhandled exception "EXCEPTION_ACCESS_VIOLATION" at 0x7FFFEF209B6B OpenAnimationReplacer-DetectionPlugin.dll+0019B6B cmp byte ptr [rax+0x1A], 0x3E
nothing else.
Edit: Actually found the log that contained the logs
I added one new download to the optional files. Install that and if the game crashes again, send me a new crashlog.
The file adds some extra data to crashlog that I need.
Also, what were you doing when the crash occurred? Going through a door or something similar?
For whatever reason when looking up player, player was not found which resulted in that crash.
I have no idea how that can happen when you are simply walking, and it never happened to me either, but I guess I should have been more careful when coding that part.
You can never be too careful when it's about Skyrim.