AI related error in falloutnv_error.log

[LookoutPoint]

Hi,

in my falloutnv_error.log there is an entry:

AI: is assigned a linked reference and has none for a package
Sometime I get AI related crashes, so this is someting I want to investigate further.

 

Any ideas what this could be? Unfortunately no mod-index named.

Greetings

[dubiousintent]

An AI without a package is just going to "stand there". The "package" tells them what to do in response to certain "flagged" events. Highly unlikely it is going to cause a crash.

 

What makes you think you have AI related crashes? "NVAC - New Vegas AntiCrash" error log entries are described on the "Description" page. This an important log for "in-game" errors. Some are intended to assist mod authors; while others are there to help "you, the player" trying to resolve a problem. You are interested in the entries which are NOT automatically handled successfully by NVAC. Key entries to look for are the following "letter codes":
* "e" entries are Exceptions handled specifically by NVAC's targeted code changes
* "h" entries are exceptions identified Heuristically by NVAC's "global" exception handler, sometimes handled unsuccessfully.
* "m" entries are "Middle of nowhere" exceptions, sometimes handled unsuccessfully.
* "ñ" entries are Null instruction exceptions, sometimes handled unsuccessfully.
* "n" entries are Null pointer call exceptions, sometimes handled unsuccessfully.
* "o" entries are stack Overflow exceptions, usually handled unsuccessfully.
* "q" entries are program self-termination information; these are effectively crashes.
* "u" entries are Unhandled exceptions reported from the Unhandled Exception Filter; these are crashes (and the NVAC author wants to hear about them).
* "v" entries are unhandled exceptions reported by NVAC's "global" exception handler; these are crashes.
* "w" entries are informative, relaying exception information as it passes through New Vegas's final exception handler.
* "x" entries are critical errors in Windows exception data; these entries should never occur.
* ":" entries are output from OutputDebugString calls.
* ";" entries are output from the game's own error checking.
Other codes may be of interest, but are not things the player is likely to be able to resolve, They are useful for informing the author of the mod to aid them in fixing their plugin. In particular, pass along the
* "_" entries are informative, relaying that NVAC was loaded and the base address of various DLLs
* "!" entries are informative, relaying human-readable text for the user
entries.
Any error codes found in the log but not listed on the mod "Description" page should be reported to the NVAC comments page.

-Dubious-

[LookoutPoint]

Hi Dubious,
i understand that an AI without package / "a plan what to do" will not cause an instant crash.
Just never saw this entry in my log.

The story is:
My fnv setup runs very good almost without crashes (nvac "h" entries "sometimes handled unsuccessfully") are the only rare ones. I often check my nvac.log after a playsession. No errors at all.
I updated NV Tick Fix from 3.8.6 to 5.0 and then got freezes/hangs on some fasttravel. Not on all but maybe every 5th or so. I always get this nvac.log then and need to quit via taskmanager:
12232107 _ NewVegasAntiCrash FalloutNV.exe
12232107 _ 0AF60000 07050000 nvac.dll
12232107 _ 0A9F0000 05010040 nvse_1_4.dll
12232107 _ 77650000 0A0047BB ntdll.dll
12233201 f 008C79CB 00000102 FalloutNV.exe
12233221 f 008C79CB 00000102 FalloutNV.exe

So the only thing I changed was NVTF Update.
Thats why I commented my error on NVTF commentsection.

Carxt replies, that exepctions are not anywhere near NVTF and it seems to be an AI releated issue. (Thats is why I said it could be AI related.)
Unfortunately I'm not able to read this type of errorcode or know what 008C79CB 00000102 could be. That would be much easier for me and very handy.

And because he said it could be AI related I looked up all mods in fnvedit and investigasted my logs.
So I came about these errors "AI: is assigned a linked reference and has none for a package".

In the meantime I downgrade NVTF to 3.8.6 and had no single crash in my last 6 hours of gameplay. I did many quests, fasttravel etc.
I will upgrade to v5 again and see whether the freeze on fasttravel occurs or not.
Without knowing the above errorcode I thougt that it could be memory issus (e.g. clean ram on fasttravel, load things into ram) and NVTF interferrs with ENB or such.

Greetings

Edited May 22, 2020 by FalloutHog

[dubiousintent]

Hmm. Interesting. As I understand NVAC error coding, the first octet of "008C79CB 00000102" refers to the location in memory where the NVAC "f" ("Frozen") error occurred, and the second is the exception code "102", which is "MS speak" for "STATUS_TIMEOUT". That exception code would not surprise me as the result of a non-existent AI package call. (Nothing we as players can do about the memory location.)

 

What is REALLY interesting is that reverting to an older version of NVTF avoids the problem completely. That suggests something unintended crept into the newer code. (Something no programmer wants to hear.) If Carxt says the code doesn't go near that memory location, then my suspicion would be a bad pointer or mistyped address. But I'm sure that will be obvious to them as well. (Let's hope it's that obvious.) However, I note the following comment by Carxt:

 

Version 5 Released. ENB issues gone, crash issues gone.
In the middle of version 4's development, I realized NVTF had several underlying issues that could not be ignored.

 

 

So unintended consequences are a frequent result of a structural reorganization as implied.

 

What you can do is pinpoint a specific repeatable instance where the error occurs in one version of NVTF and not in the other. Being able to reliably repeat an error is key to determining the cause. Be sure to disable ENB, ENBoost, and anything of the sort before reporting it as a problem with NVTF.

 

An experiment you might try is to disable the NVTF.INI entry "bInlineCommonFunctions=" by setting it to "=0". Not that I have any expectation it is related, but it's a possibility.

 

-Dubious-

[LookoutPoint]

Hi dubiosintent,

 

thanks for the info with MS speak! That is really interesting. Not much I can do with it but it could be a hint when i get an error.

 

NVTF v6.1 is released and I will test it after writing this post. Lets see, what happens.

If there are still the same freezes I will do what you suggest me.

 

I will reply in this topic.

 

Off-topic: You have helped me many times in this forum and I just want to say: Thank you! :blush:

[LookoutPoint]

Just want to say no more crash / freeze with NVTF v6.1. Retested v5 after using v6.1 and v5 still freezes randomly.

v6.1 runs very good.

 

Thanks again for the MS-Speak info :)

[dubiousintent]

Translating MS "techno-babble" is an important part of tech support. (Even I have trouble sometimes.) Glad everything worked out and that NVTF 6.1 was the last bit needed.

 

You are welcome.

 

-Dubious-