Jump to content

Nemesis Unlimited Behavior Engine - CriticalLog "Global reset all: TRUE"


Recommended Posts

Posted

Hello, I'm very new to modding and have been following guides and it all worked great until last session where somehow I started getting this txt file when I ran Nemesis Engine.

 

It's called "CriticalLog" and simply states the date/time and "Global reset all: TRUE"

 

No idea what I did to break it, I feel like I followed everything fine and neither the guide nor other seems to have encountered the problem. I've tried disabling everything and clearing output etc but it still gives me the same Critical Log, I also updated to make sure I had c++ 2019+ installed but I didn't get this issue earlier so I kind of knew that wasn't the issue already. Apart from deleting everything and starting from scratch again, I'm not sure what to do as I'm down to only Nemesis active and it still gives me the Critical Log.

 

Any ideas or experienced modders know what I could have done to mess it up or why this has happened all of a sudden?

(I use MO2, SKSE works fine, everything seems to still work, just not animations and Nemesis itself, giving me the Critical Log.)

 

Thanks.

Posted (edited)

Looking at the source code, that string is printed from ClearGlobal(bool all) in generator_utility.cpp with generator_utility.h defining a default value of true for the all argument. Regardless of the value of all, it will always print something:

 

if (all)
{
    DebugLogging("Global reset all: TRUE");
    ...
}
else
{
    DebugLogging("Global reset all: FALSE");
}

 

So I'm going to wager a guess and say this has nothing to do with the issues you're seeing.

Edited by traison
Posted
1 hour ago, traison said:

Looking at the source code, that string is printed from ClearGlobal(bool all) in generator_utility.cpp with generator_utility.h defining a default value of true for the all argument. Regardless of the value of all, it will always print something:

 

if (all)
{
    DebugLogging("Global reset all: TRUE");
    ...
}
else
{
    DebugLogging("Global reset all: FALSE");
}

 

So I'm going to wager a guess and say this has nothing to do with the issues you're seeing.

So it's nothing to worry about, other than the fact that my animations aren't working right now, this should not be a dangerous log to get?

I've stopped altering and adding as I'm afraid I will break it further, I assumed a CriticalLog with something like that written in it would be bad / dangerous rather than just a safe output. Do I understand it right?  (I know next to nothing atm, only been modding for about 5 hours or so, I'm very new and trying to keep up.)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...