Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
"Exception: System.NullReferenceException: Object reference not set to an instance of an object"
NullRef exception means that the game is looking for something that should exist, but it doesn't find it in memory. Instead, it's finding a 'blank' or 'NULL' value where that variable should be. The significance of this when you find this exception is that, for example, if the game is looking for a number value, like how many apples you have in a stack, the game isn't finding the memory allocation to the number of apples in said stack. It's not finding zero apples, it's finding null.
IE, I ask: "How many apples do you have?" And query a memory address.
And the game responds with: "What's an apple?"
You don't have 'zero' apples, because you don't even know what an apple is.
Given that the errors thrown seem to be for generating world pawns, you may have a corrupted world pawn list, or something it's looking for is chain-reacting down the pawn generation system.
I note the following:
This is the first error seen being thrown just after 'ROCKETMAN' loads. The errors below that appear to be Ion-Son's associated gear. The thing that standards out with THIS error is that it's trying to Register Ion-Son, when Ion-Son is already registered. Which may be either you have an Evil Clone problem, or corrupted data.
I would start by pursuing two options:
1: Clear the world pawn list. There's a mod that does that, if it's up to date.
2: Remove 'ROCKETMAN'.
EDIT:
This mod, assuming this is the right link:
https://steamcommunity.com/sharedfiles/filedetails/?id=2559582557&searchtext=memory
If the link isn't right, it's called
"RuntimeGC"
It has various cleanup options, and might be useful to clean up the world pawn list. Start there.
Also, if you don't have it already, install 'ModManager' mod. It can identify if you have out of date mods or bad loading orders for certain mods.
https://steamcommunity.com/sharedfiles/filedetails/?id=1507748539&searchtext=modmanager
NullRef exceptions are one of those things you just sort of learn to watch for over the years. They are the debugger friendly version of CTD, or crash to desktop. Because once-upon-a-time the only response a program had to a finding a null value was to immediately close, as it would not know what to do with itself without the value it was looking for. Now programs are surprisingly robust enough in many cases to throw said error and step around it gracefully. The debug logger catches it, but the program keeps going.
Just knowing about NullRef exceptions will make you all the better at reading logs all over the place.
Keep in mind, error logs are MEANT to be understood so errors can be fixed. If you couldn't figure them out, they would be useless. Usually, the errors contain the likes of what the error is and where the error occurred in code. That's more useful to the coders themselves, but you can still use it to narrow down the problem for yourself.
And that's all I did when I sorted through the error log you posted.
First I skimmed the log, scrolling past all the loading messages until things started to look different, then I ran into the ROCKETMAN error. I read the message there, noting what I told you about Ion-Son. I read the errors that followed it, and realized it was just child errors to the first one (In Other Words: All the gear errors stem from the fact that the pawn itself was messed up.)
After that I scrolled further until I ran into the pawn generation errors...
When I read this error, I read the error message itself, but the big clue were the lines just above the line 'Error while generating pawn.'
This is what it was doing right before it threw the error. It was generating a set of world pawns.
Then I noticed this below the error:
Let me filter that down to what I SAW between the lines in that single error:
Does that not look like a problem building a family tree?
At that point, I figured this was going to be a world pawn problem, and I worked from memory that RuntimeGC would be good, because it fixed problems with the world pawn list becoming overloaded.
It's simple assumption and association with a hint of past lessons and remembering tidbits. In short, if you suspect A and B are related when it looks like it in an error log, chances are that they ARE.