Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error(3024) Posted at 64% While running Engine Update through Vortex Tool #122

Closed
AnsionEsre opened this issue Dec 18, 2019 · 13 comments
Closed

Comments

@AnsionEsre
Copy link

Initializing engine update

ERROR(3024): Duplicated header has been detected in "animationdatasinglefile.txt". Please contact the template creator
Template: behavior templates__folder_managed_by_vortex
Project: <2>
Header: <3>

Failed to update engine
UpdateLog.txt

@ShikyoKira
Copy link
Owner

Vortex messes with the folders and animationdatasinglefile.txt. Try using MO2 instead for now. I will contact Vortex developers in near future regarding this matter

@AnsionEsre
Copy link
Author

So it is a problem with using Vortex?
I'm sorry but I guess I will not be using your tool then. I really did enjoy it, but I do not enjoy using MO2 or the bias it has in the community as the one tool.
I'll follow up in time to see if this has been corrected. Thank you for responding.

@Shavv
Copy link

Shavv commented Jan 7, 2020

Im having the same problem, and all my 2000+ mods are managed by Vortex. Going over would be such a pity as I would have to restart all over again.

A custom install also doesn't work since it doesn't recognize the mods in updating the engine.

@chibi4
Copy link

chibi4 commented Jan 9, 2020

I'm using v0.83bSE and got the same error at first. The program tries to interpret these __folder_managed_by_vortex files. It's a text file that reads "This directory was created by Vortex deployment and will be removed during purging if it's empty". Since they don't contain any meaningful information for Nemesis, an error occurs.
By deleting the "__folder_managed_by_vortex" file in Nemesis_Engine, the update continues until a different error - caused by another __folder_managed_by_vortex file in another sub-directory. Since I didn't have the patience to continue deleting each __folder_managed_by_vortex file in every folder, I simply manually copied the Nemesis_Engine folder into Skyrim's data directory. Now it updates as expected and the Engine runs fine as well.

It would be very helpful if your Nemesis Engine could be programmed to ignore these files. The "animationdatasinglefile.txt" file and any other files are not modified by Vortex.

@Shavv
Copy link

Shavv commented Jan 9, 2020

I'm using v0.83bSE and got the same error at first. The program tries to interpret these __folder_managed_by_vortex files. It's a text file that reads "This directory was created by Vortex deployment and will be removed during purging if it's empty". Since they don't contain any meaningful information for Nemesis, an error occurs.
By deleting the "__folder_managed_by_vortex" file in Nemesis_Engine, the update continues until a different error - caused by another __folder_managed_by_vortex file in another sub-directory. Since I didn't have the patience to continue deleting each __folder_managed_by_vortex file in every folder, I simply manually copied the Nemesis_Engine folder into Skyrim's data directory. Now it updates as expected and the Engine runs fine as well.

It would be very helpful if your Nemesis Engine could be programmed to ignore these files. The "animationdatasinglefile.txt" file and any other files are not modified by Vortex.

This is not do-able if you have mods that depend on it. For example: the dark souls animation mod that requires Nemesis to patch it out without being in the list as a standard. Some mods may appear later in the list and if you install this manually, this is not an option. This only works if you install nemesis manually and have no mod that isn't in the list, or have mods that are as a standard in the list for a patch.

So i don't recommend this.

@chibi4
Copy link

chibi4 commented Jan 9, 2020

I'm not sure if I completely understood you, but I tried with XPMSSE, Engarde and Combat Behavior Compulsion (SGC - SkySA) now. Installing the last one normally leads to errors again, but at least the option to manually copy the mod's Nemesis folder over exists. That adds a skysa folder under Data\Nemesis_Engine\mod so it's not unmanagable.

Then Nemesis runs. It's certainly not a nice long term solution but at least it works. (Didn't test ingame yet, but assume it works.)

ShikyoKira pushed a commit that referenced this issue Jan 11, 2020
@ShikyoKira
Copy link
Owner

Fixed in v0.83c

@mosharky
Copy link

I have this exact same problem using Nemesis on MO2, and I'm on the latest version of Nemesis. Any pointers?

Modlist: https://modwat.ch/u/Stootas/plugins

@aminomancer
Copy link

^ if you're using MO2 and getting this exact error message then it clearly means you used to use vortex. you must have installed this mod with vortex and then switched to MO2. you would need to go into the Nemesis_engine folder and search/find all files called _folder_managed_by_vortex and delete them. but i don't think you need to do this anymore in the first place? if you're actually using the latest version of nemesis then you shouldn't get this error at all, because it has an exception for these files and doesn't interpret them as templates. i have nemesis installed through vortex and my folders are full of these files and I don't get any errors running nemesis. I would suggest you uninstall Nemesis completely (delete the nemesis_engine folder) and reinstall the latest version through whichever mod manager you're currently using.

@VulcanTourist
Copy link

VulcanTourist commented Oct 10, 2020

This ticket marked as fixed in January 2020, but here it is October 2020, I've just installed v0.84 and removed everything related to FNIS, and I'm getting that exact same behavior and error from Nemesis, merely because my choice of mod manager happens to be Vortex?

Initializing engine update

ERROR(3024): Duplicated header has been detected in "animationdatasinglefile.txt". Please contact the template creator
Template: behavior templates\anim_object.txt.vortex_backup
Project: <2>
Header: <3>

Failed to update engine

I even tried deleting all the animation-related .txt files in Meshes, but that made no difference.

@mangoman2000
Copy link

mangoman2000 commented Oct 30, 2020

Initializing engine update

ERROR(3024): Duplicated header has been detected in "animationdatasinglefile.txt". Please contact the template creator
Template: behavior templates__folder_managed_by_vortex
Project: <2>
Header: <3>

Failed to update engine

Skyrim SE with SKSE64 and SKYUI and nemesis. Trying this after about 10 months, issue is still there.

Why not just put in a disclaimer and handle this error. Hasnt it been too long in the works?

If I try to click "Launch Nemesis Behavior Engine" I get the following:

Checking engine version
ERROR(6006): Missing latest engine files. Update engine to fix it

Failed to generate behavior

This is annoying as I am not using any of the mods for which this error is not being handled.

@RonYuma
Copy link

RonYuma commented Dec 31, 2020

just started to have this problem, first time installing nemesis

ERROR(3020): Invalid format for "animationdatasinglefile.txt" in InfoData section has been detected

I never used vortex before, always mo2, has this been fixed yet

@skftwins
Copy link

I was having this issue while using Vortex and tried a few things but I found a method that worked for me
Courtesy of RedditUser AMGarkin

1 month ago
When Vortex detects existing file in destination folder (which wasn't added by Vortex), it will make backup copy like that.

To solve this problem simply delete file \Data\Nemesis_Engine\behavior templates\behavior templates\anim_object.txt.vortex_backup or move this file somewhere else. You should do the same for all *.vortex_backup files inside of Nemesis_Engine folder.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants