Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
Now it is correct then... Dunno about before ^^
It would be nice if there was a way to verify in game the version that is running. (If there is already I apologize, I don’t know how to access that info) I got a good 15 hours into my last play through (a new play trough) and after Chapter 1 ended with the notifications about Chapter 2 upcoming I spent two hours building up my settlements waiting for it to trigger Chapter 2. I finally checked the Wiki and realized something had gone wrong. I didn’t upgrade via Vortex correctly I think…
Rebuilding and starting a new play through again tonight.
Nope I did
That just means Chapter 2 wasn't installed or wasn't enabled. You don't have to restart.It would be nice if there was a way to verify in game the version that is running. (If there is already I apologize, I don’t know how to access that info) I got a good 15 hours into my last play through (a new play trough) and after Chapter 1 ended with the notifications about Chapter 2 upcoming I spent two hours building up my settlements waiting for it to trigger Chapter 2. I finally checked the Wiki and realized something had gone wrong. I didn’t upgrade via Vortex correctly I think…
It would be nice if there was a way to verify in game the version that is running. (If there is already I apologize, I don’t know how to access that info) I got a good 15 hours into my last play through (a new play trough) and after Chapter 1 ended with the notifications about Chapter 2 upcoming I spent two hours building up my settlements waiting for it to trigger Chapter 2. I finally checked the Wiki and realized something had gone wrong. I didn’t upgrade via Vortex correctly I think…
I had been doing that for all the updates, but 1) I wasn't deleting the old one under the version column (not sure that actually needs to be done), I was updating all profiles, 2) I think something went wrong from my initial update to Chapter 2 as I never saw any of the in game changes with world repop and what not, I was just assuming I hadn't triggered the content yet thinking the content was more liniar. But after recalling King's let's play and he was experiencing the new content within chapter 1 quests it got me digging around. It's no biggie and seeing @kinggath post about checking the version number in game is good knowledge that's new to me.
You did the right steps, so the initial one might have failed. That can happen with every Mod Organisor. It is save to delete the older versions if you're satisfied with the current one. It are the archives of the mod who are kept. The mod itself got refreshed in Vortex. So you have at the moment a nice collection of archived (downloaded) SS2 versionsI had been doing that for all the updates, but 1) I wasn't deleting the old one under the version column (not sure that actually needs to be done), I was updating all profiles, 2) I think something went wrong from my initial update to Chapter 2 as I never saw any of the in game changes with world repop and what not, I was just assuming I hadn't triggered the content yet thinking the content was more liniar. But after recalling King's let's play and he was experiencing the new content within chapter 1 quests it got me digging around. It's no biggie and seeing @kinggath post about checking the version number in game is good knowledge that's new to me.
You can keep 'm but there is no need for it.
The long saves where an issue for me at start, that's before h.
I've played all versions since the release of 2.0.0 and never had that problem. Care to elaborate a little bit more?
It is not irregular in software development to use letters for hotfixes. Usually goes like this:
Yeah, sometimes you gotta go and delete stuff manually that Vortex misses.
Sure!
Kinggath tends to use the minor numbers for additional stuff added and the second number for larger changes or additions obviously chapter 2 is the large scale update meaning a need to the change to 2.0I've played all versions since the release of 2.0.0 and never had that problem. Care to elaborate a little bit more?
It is not irregular in software development to use letters for hotfixes. Usually goes like this:
If it was in early access, then the first number would be zero, i.e., before the first Major release.
- The first number is Major Release
- The second number is a Minor release, like the addition of a big feature
- The third number is when you have enough difference to justify a new number, but not enough to consider it a Minor release. In the case of SS2, imagine they add more leaders or something like that. It is new content but it isn't a new feature
- Finally, the letters are used to mark hotfixes.
As for the frequency of the updates, they were minor quests and QOL fixes that made a huge difference for the player base and it was important to release them as soon as they got fixed (therefore, hotfixing it). The problem discussed on this thread was the long save issue and yesterday the team got a fix, so they push it as fast as they could.
The change logs aren't posted in nexus. They never were for this mod. You can read them on the wiki or on this section on the forum. The latest release is 2.0.0m. You can read them all here if you want https://wiki.simsettlements2.com/en/getting-started/patch-notes
Hope that clarifies things a bit, if there is anything else you need, post it here and someone will do their best to reply to you
I’m not sure what the references are referencing any way you can elaborate on what is the issue as I generally use auto clean to run through and clean stuff and only use the full editor for patching or changes. Like what is it that is broken exactly cause the mod has worked as intended on my end besides the long saves.Sure!
So if I load mods in FO4Edit with an empty cache, meaning all the references get read too for errors, I get the following attached list of errors for 2.0.0k forwards (including 2.0.0m):
View attachment 15505
These errors are not present in 2.0.0h (I haven't tested i and j)
What comes to alphabets, they are used in software environment true, but not in modding environment, but you do you.
The reason I didn't test i and j are a result of bad version naming. How? Nexus doesn't list them alphabetically.
As in they don't support nor share the same software environment mentality.
Causing me to miss them when downloading older iterations when trying to get rid of broken reference records.
thanks, that turns out to be exactly the cause, alongside the howitzer's artillery reskinYou're problem is not per se long save related viewing your log. I would start with disabling the mod functional displays, it's bugged, it's abondend, despite that it is a great mod.
If it's not helping you, start a new thread with the crash log and your full list of mods.
Things can move fast in this thread and probaly most of the conversation won't be about addressing your specific problem.
I'm sure I find the thread if it goes up
I saw that as well, but when I dig into the record, none of that stuff mentioned in the error means anything to me - it's saying the responses are out of order, but they look fine to me - so not sure what it's reporting. That scene works fine still, I recorded it two days ago for the voice actors to put in their demo reels.
