Update on the "issue". I think those two modules are conflicting with everything else.
What i did earlier this day is i just restored those two modules, entered the save i was playing, game froze completely. Alright, next i "cleaned" the save, entered the game but ui fix mod stopped working, i re-applied that mod, entered the game, now UI scaling is working again, but if i remember correctly at the start NRAAS StoryProgression modules (both) did not show at the start. I exited the game, re-added Resource cfg (apparently when some mods do not show, re-adding Resource cfg file from the rar re-enables mods to be discovered again). I played the save, it was working optimally (how it worked before adding StoryProgression modules) ErrorTrap maybe showed one error, but sims stories progressed (i think), normally. I decided to check World adventures regions. I went to every region, and after mod set everything up (maybe 3-5 minutes per region), i was able to play "optimally". But then i noticed bunch of script errors popping, though more or less game worked, those script errors were popping in every region of world adventures, i tried all three of them. Then what i noticed is some sims where doubled (two same sim with same name but with different outfit) but other sim with the same name and surname could not be interacted with, i noticed couple of others also with the exact the same issue, i managed to "fix" them, by deleting/purging that ones that are stuck because those sims just stand in place with no actions. After that i returned to my original town, game was working "optimally", i played a bit, and then went to my other family in other house just to play a bit more (because daughter of my character was pregnant and almost gonna get his grandson). I tried upgrading their house by shift click entering build/buy mod in their house, and then i got stuck in build/buy mod, and that was the end of my playthrough, game stuck, could not even exit the game, so i ended the process from the task manager. This never EVER happened before, so i am sure its mod conflict of some sorts. Here is the compilation of log xml list. I will check this thread tomorrow, because its 12am here now. https://www.mediafire.com/file/1d6oaye9 ... _3.7z/file

What is the source of this install? Origin? Disc? Something else?

Chain_Reaction post_id=100240 time=1710288639 user_id=2 wrote: What is the source of this install? Origin? Disc? Something else?

1.67 old EA launcher, so i patched that with mods launcher for "smooth patch", game runs via that launcher. So basically its like "something else". we do not need to take into account different versions of the game (i mean steam, origin or anything else), because game was working okey, i have this game installed on different kind of HW 10 year at least, i did not have those issues i described EVER. Its something about compatibility between those mods i have installed. I played a bit more after mentioned hard game crash in previous post. And now game is working fine in build/buy mode, i can get out and in again no issues, and no action lag issue, nor there is scripting issues. So some "event" maybe in the game is breaking the script, and then consequence is unpredictable. Basically point of my post is to find out (if possible) what is the issue, and how to avoid/fix IF it happens. If someone knows its fine, if not i cant conclude anything else except mod conflict with StoryProgression and 1 or both of those other mods.

LazyDuchess' patched launcher is for 1.69 Origin and EA App- the issue may be arising from making such manual changes to the Bin files. Hopefully you have backups, otherwise you may need to reinstall the game. Multiple NRaas mods are throwing errors in those logs with no obvious culprits in the loaded assemblies, but it also wouldn't hurt to temporarily remove all other mods just to see if the issue reoccurs.

I'm also not sure there is a legitimate way to obtain an online 1.67- we cannot offer support for versions of the game sourced outside of 1.69 Origin / EA App and 1.67 from Steam or retail disc. Happy to be wrong if there are still ancient versions of the EA download manager around, but my understanding was that a 1.69 update is impossible to avoid for digital installs.

gare87 wrote: ↑

March 12th, 2024, 8:21 pm

1.67 old EA launcher

But how were the game files acquired?

gare87 wrote: ↑

March 12th, 2024, 8:21 pm

we do not need to take into account different versions of the game (i mean steam, origin or anything else)

We do when things don't quite add up.

CardinalSims wrote: ↑

March 12th, 2024, 9:37 pm

LazyDuchess' patched launcher is for 1.69 Origin and EA App- the issue may be arising from making such manual changes to the Bin files. Hopefully you have backups, otherwise you may need to reinstall the game. Multiple NRaas mods are throwing errors in those logs with no obvious culprits in the loaded assemblies, but it also wouldn't hurt to temporarily remove all other mods just to see if the issue reoccurs.

I'm also not sure there is a legitimate way to obtain an online 1.67- we cannot offer support for versions of the game sourced outside of 1.69 Origin / EA App and 1.67 from Steam or retail disc. Happy to be wrong if there are still ancient versions of the EA download manager around, but my understanding was that a 1.69 update is impossible to avoid for digital installs.

I already wrote i installed older version of that mod and it clearly says 1.67, so its not for 1.69. I added older version exactly because somewhere is mentioned newer one may have incompatibility with some NRAAS mods. I also said i did remove smooth patch to try what gonna happen, and had that "action lag" issue, which was fixed when i removed StoryProgression both modules. For version, its simple, any bypass can be downloaded which is 1.67 version. Its the same thing for example as Elden ring bypass to be able to use mods.

Chain_Reaction wrote: ↑

March 12th, 2024, 10:00 pm

gare87 wrote: ↑

March 12th, 2024, 8:21 pm

1.67 old EA launcher

But how were the game files acquired?

gare87 wrote: ↑

March 12th, 2024, 8:21 pm

we do not need to take into account different versions of the game (i mean steam, origin or anything else)

We do when things don't quite add up.

Read previous posts. Long time ago was acquired via EA app. And i just stick to 1.67 launcher (i can just block update and/or add bypass launcher to avoid updating, i read 1.69 had lots of issues with lots of things, so i just stick with 1.67), and also game is launched via Smooth patch launcher.

gare87 wrote: ↑

March 13th, 2024, 9:03 am

Chain_Reaction wrote: ↑

March 12th, 2024, 10:00 pm

gare87 wrote: ↑

March 12th, 2024, 8:21 pm

1.67 old EA launcher

But how were the game files acquired?

gare87 wrote: ↑

March 12th, 2024, 8:21 pm

we do not need to take into account different versions of the game (i mean steam, origin or anything else)

We do when things don't quite add up.

Read previous posts. Long time ago was acquired via EA app. And i just stick to 1.67 launcher (i can just block update and/or add bypass launcher to avoid updating, i read 1.69 had lots of issues with lots of things, so i just stick with 1.67), and also game is launched via Smooth patch launcher.

Please do not tell me to read the previous post. If I'm still asking it means the previous post didn't add up. It still doesn't because I'm unsure how you properly patched a very old EA DM install to 1.67 given the install base converted to Origin mid series. I'm asking because the errors you have indicate the core code doesn't align with what is expected. I suspect some of the issues stem from this install you have. Nevertheless since you're confident and combative in your install and believe your other mods to be conflicting, and sure some of them may be as well, my only suggestion is to either use SP or them.

Chain_Reaction wrote: ↑

March 13th, 2024, 1:46 pm

Please do not tell me to read the previous post. If I'm still asking it means the previous post didn't add up. It still doesn't because I'm unsure how you properly patched a very old EA DM install to 1.67 given the install base converted to Origin mid series. I'm asking because the errors you have indicate the core code doesn't align with what is expected. I suspect some of the issues stem from this install you have. Nevertheless since you're confident and combative in your install and believe your other mods to be conflicting, and sure some of them may be as well, my only suggestion is to either use SP or them.

By just googling you can find patch for older version on different sources. One example of these are here
https://www.gamepressure.com/download.asp?ID=48580
Also by googling you can also find SmoothPatch for 1.67, so i put an effort to add those for the version i have. Also NRAAS is clearly stated mods are compatible with 1.67/1.69, its literally in description. I also said that we can take into account that "source" is "somewhere else", because that's how i can leave the game at 1.67 and avoid it updating to latest, which would probably produce more issues. If NRAAS mods gonna require some ultra mega latest special patch version i would not add them, which is not the case, because they clearly state 1.67/1.69. So if you do not have some other suggestion, just say so, its not a big deal.

Simply installing the 1.67 patch over top of a 1.69 install (which is the unavoidable default if the game was installed through Origin or the EA App) is not how this works, and absolutely how you end up with a game that has every mod capable of throwing script errors throwing them as seen in your logs.
1.69 is also fine, besides being a somewhat annoying DRM. Anything making it out to be some kind of evil unusable patch level is old drama- every digital install user here is getting by without issue.

Smooth Patch has also been updated to remove the incompatible parts; the most current version is fine- but it's definitely worth just setting it aside for now as throwing another third-party plugin in is not helpful at this stage.

It generally sounds like you've read a lot of misinformation about the game and made a lot of installation level changes that have simply broken your game. If you come here for help, most of the people here and most especially the developer know what they're talking about- it would help you to be more open minded to what they are saying is for a reason, rather than redirecting them back to your own statements.

You will need to resolve these issues or proceed at your own risk and play without SP as advised by Chain.