Read/Understand the LastException file and similar.

[ValquiriaLiraLima]

Hello from Brazil, Sorry my English.
I searched here on several topics and couldn't find anything related to my need. I would like to "learn to read" the files of LastException, LastCleanException (what is the difference between them, what is each?) as I see many people publishing them and others soon answering what the problems are. I would like to learn not to depend too much on others and also not to be too bothering people when asking for help and also to help other people here in my country who have similar difficulties. Could someone post here a full explanation of it as an example for example on the "Crinrict's Sims 4 Help Blog" website explaining what it is, what is it for and how to read it? It may be in English, I'll use a translator. I thank you very much for your attention and help. ❤️(=^_^=)❤️

[Scorpio]

Several mods check and report errors and dump LE files.

Could be game errors, mod errors, conflicts, duplicate versions, etc.

MCCC

WW

Basemental Drugs (I think)

Nisa's Wicked Perversions

 

Not something you can learn overnight or just by reading instructions IMO.

I have been studying them for a year + and I still miss things.

 

Some errors are fairly easy to read as they will list the mod name or file name abbreviations.

Over time you learn what abbreviations that some of the more common mods use like AEP and SoL for example

Certain errors you see over and over again are quite identical so you learn by memorizing a few of them.

 

95% of errors are from outdated mods, old game versions using new mod versions, mismatched mods, duplicate mods, 2 mods using the same resources, 2 different versions of same mod, etc.

5% are from improper mod install locations, game bugs, not clearing the localthumbcache when adding, removing, or updating mods or the game itself.

Probably more I just can't recall ATM.   

 

Then there are the silent bugs that don't produce any LE's.

Just hanging out on LL and reading threads you can learn quite a bit too. 

[ValquiriaLiraLima]

Just now, Scorpio said:

Several mods check and report errors and dump LE files.

Could be game errors, mod errors, conflicts, duplicate versions, etc.

MCCC

WW

Basemental Drugs (I think)

Nisa's Wicked Perversions

 

Not something you can learn overnight or just by reading instructions IMO.

I have been studying them for a year + and I still miss things.

 

Some errors are fairly easy to read as they will list the mod name or file name abbreviations.

Over time you learn what abbreviations that some of the more common mods use like AEP and SoL for example

Certain errors you see over and over again are quite identical so you learn by memorizing a few of them.

 

95% of errors are from outdated mods, old game versions using new mod versions, mismatched mods, duplicate mods, 2 mods using the same resources, 2 different versions of same mod, etc.

5% are from improper mod install locations, game bugs, not clearing the localthumbcache when adding, removing, or updating mods or the game itself.

Probably more I just can't recall ATM.   

 

Then there are the silent bugs that don't produce any LE's.

Just hanging out on LL and reading threads you can learn quite a bit too. 

Thankfully, I will commit myself to learn a little more.
(=^_^=)

[Crashdown117]

The only "good" advice I can give is this: Learn it by using real examples.

 

Now for some theory (don't worry, I'll keep it simple):

There are a few types of files around, mainly "lastException.txt" and its "cousins", but also files created by big mods like WickedWhims and Nisa's Wicked Perversions. From my experience "lastException" is the most helpful, so I never really bothered with "lastCrash", "lastCleanException" or other files like those. Exception files created by mods are often helpful to the creators of those mods and may look "prettier" (they are easier to read), but "lastException.txt" usually includes all available information.

What you will find in all those files is an overview over what "happened" when the error occurred - functions that were called, files involved, and so on. It is like a photograph and the big difference is the perspective, from which it was taken. For example "lastException" is created by the game (which "sees everything"), while "someMod_Exception" would be created by a mod (which may be limited to the context of what the mod does). In my opinion, you don't really need to know more about the details and differences - at least, of you just want to fix an issue with the game every now and then.

 

Finally, some "real" advice (although this is just how I tend to do it):

1) Get a good text editor, "Notepad++" would be my recommendation (it's free). It'll make reading a lastException (or any other exception file) much easier, because the different "types of text" get their own colors and lines will not depend on your editor's window size (which makes everything rather chaotic).

2) Know the difference between mod and game files. If it says "File "T:\InGame" and then something, you can ignore it and continue to the next "File:" entry. You can't do anything about "InGame" stuff, as it is part of the game files.

3) Know your mods. For example, "TURBODRIVER" hints at something related to WickedWhims. Finding and identifying mods can give you an idea about what caused the issue.

4) Pay attention to version numbers. In a lastException, all lines start with the same bits of information, including the game's edition (e.g. "ea.maxis.sims4_64.15.pc" for the regular Windows versions) and current version ("Local.Unknown.Unknown." followed by some numbers like "1.63" and then some). Likewise, mods often have their version number show up in the lastException (e.g. "E:\Python3_7_0\version_vault\LL\LL_2_7c\..." for Nisa's Wicked Perversions).

5) Put the pieces together. Do mods show up often in your lastException? Are any of them out of date? Have there been any big updates recently? What does the changelog of mod XYZ say? This is where it starts to get tedious.

6) Be ready to actually test your mods, if you can't find anything. This is really tedious, so it should only be a last resort.

 

But most importantly: Don't be afraid to ask for help. You don't "bother" anybody around here, we're not EA ? - people on this and other sites actually WANT to help you.

I learned all I know about exceptions by running into problems myself and then looking for solutions, so I know how frustrating it can be sometimes. And more help is always welcome.

 

I hope, this is somewhat helpful to you.

Cheers from Germany.

 

Links to the exceptions I used for my examples (these also include other exception files):

https://www.loverslab.com/topic/156771-wickedwhims_v161b-exception/

https://www.loverslab.com/topic/156700-nisas_last_exception/

 

 

EDIT: Some duplicates of what Scorpio already mentioned, I know. But it's past 1 a.m. and my typing is terribly slow, so I'll just leave everything as it is ?

[ValquiriaLiraLima]

1 hour ago, Crashdown117 said:

The only "good" advice I can give is this: Learn it by using real examples.

 

Now for some theory (don't worry, I'll keep it simple):

There are a few types of files around, mainly "lastException.txt" and its "cousins", but also files created by big mods like WickedWhims and Nisa's Wicked Perversions. From my experience "lastException" is the most helpful, so I never really bothered with "lastCrash", "lastCleanException" or other files like those. Exception files created by mods are often helpful to the creators of those mods and may look "prettier" (they are easier to read), but "lastException.txt" usually includes all available information.

What you will find in all those files is an overview over what "happened" when the error occurred - functions that were called, files involved, and so on. It is like a photograph and the big difference is the perspective, from which it was taken. For example "lastException" is created by the game (which "sees everything"), while "someMod_Exception" would be created by a mod (which may be limited to the context of what the mod does). In my opinion, you don't really need to know more about the details and differences - at least, of you just want to fix an issue with the game every now and then.

 

Finally, some "real" advice (although this is just how I tend to do it):

1) Get a good text editor, "Notepad++" would be my recommendation (it's free). It'll make reading a lastException (or any other exception file) much easier, because the different "types of text" get their own colors and lines will not depend on your editor's window size (which makes everything rather chaotic).

2) Know the difference between mod and game files. If it says "File "T:\InGame" and then something, you can ignore it and continue to the next "File:" entry. You can't do anything about "InGame" stuff, as it is part of the game files.

3) Know your mods. For example, "TURBODRIVER" hints at something related to WickedWhims. Finding and identifying mods can give you an idea about what caused the issue.

4) Pay attention to version numbers. In a lastException, all lines start with the same bits of information, including the game's edition (e.g. "ea.maxis.sims4_64.15.pc" for the regular Windows versions) and current version ("Local.Unknown.Unknown." followed by some numbers like "1.63" and then some). Likewise, mods often have their version number show up in the lastException (e.g. "E:\Python3_7_0\version_vault\LL\LL_2_7c\..." for Nisa's Wicked Perversions).

5) Put the pieces together. Do mods show up often in your lastException? Are any of them out of date? Have there been any big updates recently? What does the changelog of mod XYZ say? This is where it starts to get tedious.

6) Be ready to actually test your mods, if you can't find anything. This is really tedious, so it should only be a last resort.

 

But most importantly: Don't be afraid to ask for help. You don't "bother" anybody around here, we're not EA ? - people on this and other sites actually WANT to help you.

I learned all I know about exceptions by running into problems myself and then looking for solutions, so I know how frustrating it can be sometimes. And more help is always welcome.

 

I hope, this is somewhat helpful to you.

Cheers from Germany.

 

Links to the exceptions I used for my examples (these also include other exception files):

https://www.loverslab.com/topic/156771-wickedwhims_v161b-exception/

https://www.loverslab.com/topic/156700-nisas_last_exception/

 

 

EDIT: Some duplicates of what Scorpio already mentioned, I know. But it's past 1 a.m. and my typing is terribly slow, so I'll just leave everything as it is ?

I liked it, I liked it a lot. No problem repeating information, I really like it. I really stand in front of the LE texts reading them trying to understand and I feel stupid for not understanding. Some people look at an LE and already know what it is and I find it incredibly wonderful. I hope someday to be smart like all of you. Thank you also for your help.
(=^_^=)

Edit: I downloaded Notepad ++ and it really is a lot easier to read with the help of it. Thank you so much for the tip (you two make me feel like one of you). ?

[Crashdown117]

10 hours ago, ValquiriaLiraLima said:

Some people look at an LE and already know what it is and I find it incredibly wonderful. I hope someday to be smart like all of you.

That's just because a lot of the LEs are similar. Like Scorpio said, about 95% of the time it's outdated, broken or incompatible stuff - and these are often pretty easy to identify. Just look at some of the LEs he's handled recently and you'll begin to see a pattern (I did, back when I started, and I would not consider myself to be exceptionally smart).

 

10 hours ago, ValquiriaLiraLima said:

you two make me feel like one of you

You ARE one of "us" now ?