the Sim Settlements forums!

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!

Resolved Yet Another "Won't Upgrade to Level 1"

ibanix

New Member
Messages
19
Sim Settlements: 3.0.2
RoTC: 3.0.0
Industrial Revolution: 2.1.7

Issue: Multiple settlements with
1) Happiness over 70
2) 100% Scrap (Involvement is set to 'Low')
3) Full bars of food/water/defense/power/housing/jobs
4) More than 10 days have passed

None have upgraded to Level 1.

Welcoming any suggestions.
 
SS and all expansions are now on V 3.0.3

Please update, refresh the settlement(s) and see if it fixes your issues.

Moreover running different versions of the main mod and the expansions is not supported, it will lead to erratic behaviour.
 
Cute, it was updated *two hours ago* on Nexus. What would you have posted if I had posted this morning?

By which I mean, prior to two hours ago, you would no choice but to run different versions together....
 
Cute, it was updated *two hours ago* on Nexus. What would you have posted if I had posted this morning?

The same; you are running mismatched (and in the case of the expansions sorely outdated) versions of SS, RotC and IR so I would have suggested that you update all the plugins first.

We cannot help someone that won't help himself/herself let alone the unnecessarily abrasive reply.
 
As of three hours ago, the latest versions of each were:

Sim Settlement (base): 3.0.2
RotC: 3.0.0

So.... are you saying that anyone using RoTC should not have been running a version of the base Sim Settlement over 3.0.0?

Additionally, it appears that IR wasn't updated from 2.1.7 to 3.0.0 until 29 Dec; and Nexus Mod Manager does not report that a new version is available (as with all the other mods I regularly update).

If you're going to immediately default to "you're out of date", then at least be consistent and publish in a way that allows people to actually stay updated? Because you know, we're not checking the nexus page manually every single day?
 
Last edited:
As of three hours ago, the latest versions of each were:

Sim Settlement (base): 3.0.2
RotC: 3.0.0

So.... are you saying that anyone using RoTC should not have been running a version of the base Sim Settlement over 3.0.0?

IR has seen several - published - iterations since 2.1.7

3.0.0 had a list of known bugs including the one you are reporting that should have been addressed in 3.0.3 hence suggesting that you update your plugins.

What I am saying is that you should update to the latest available versions in order to establish whether the problems you are experiencing have been resolved or not.

EDIT: You can find more information about 3.0.3 in KG's video should you be interested:

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.
 
There is no version on Nexus for IR that is greater than 2.1.7 and less than 3.0.0. Whatever flag or setting is necessary for Nexus Mod Manager to detect that IR is out of date, is not current working.
 
There is no version on Nexus for IR that is greater than 2.1.7 and less than 3.0.0. Whatever flag or setting is necessary for Nexus Mod Manager to detect that IR is out of date, is not current working.

There is 3.0 and 3.0.2

The issue here is that I want to help you and you want to be right.
 
If you're going to immediately default to "you're out of date", then at least be consistent and publish in a way that allows people to actually stay updated? Because you know, we're not checking the nexus page manually every single day?
We're trying our best ibanix, the number of posts and messages across all of the different platforms we've had in the past two weeks is very hard to keep up with - so some amount of screening has to happen. We're not trying to blow you off, we just don't have the manpower to get in depth immediately with each person.

The folks with the Support Team tag volunteered their time to help me out because I just can't get to every post myself.

Since you're on PC, if you enable Papyrus logging, there will be "City Ineligible Reason" entries in the log that will help us figure out why your cities aren't upgrading.
 
I am upgrading the versions.

As a software developer in my own area, I am disappointed by the way this is handled.
 
Thank you! I have enabled Papyrus logging and am on all the most current versions. Should I look for a particular line/text, or would you prefer an upload of the entire file?
 
Search for "City Upgrade Ineligible Reason", if you have multiple cities operating, you'll have to figure out which each message is for, as there's not an easy method to print out the actual settlement name.

To find out which city each reason refers to, run the console command:

prid XXXXXXXX replacing the X's with the 8 digit hex ID before the reason log entry

This will select the workbench in that settlement, if you have Better Console installed, it will probably show you where this is - otherwise you can run

player.moveto XXXXXXXX again, replacing the X's, which will teleport you to that workbench.
 
If I had to guess, it would be that not enough plots have been constructed or upgraded in that settlement. Now that I have the worst bugs taken care of, I'll be addressing usability, so a means of determining what else is lacking in each city is on my agenda so that going through all of these hoops with the logs is not necessary.
 
Real life took my last 24 hours, but I got back to look at this. After upgrading to version 3.0.3 on everything, I noticed my Tenpines Bluff planner's desk had gained the Upgrade City option, which worked correctly when used. This was odd because I had previously set for auto-upgrade. I checked and the option is now set to manual. Changed it back to auto and will be checking other settlements.
 
Real life took my last 24 hours, but I got back to look at this. After upgrading to version 3.0.3 on everything, I noticed my Tenpines Bluff planner's desk had gained the Upgrade City option, which worked correctly when used. This was odd because I had previously set for auto-upgrade. I checked and the option is now set to manual. Changed it back to auto and will be checking other settlements.
When you get a chance, snag 3.0.3b and run the Resaver fix described here. Absolutely nothing to do with the options or anything - but just trying to get the word out to anyone who has definitely grabbed 3.0.3 so they don't end up with the lag caused by the bug.
 
I am upgrading the versions.

As a software developer in my own area, I am disappointed by the way this is handled.
wow, did i miss the bit where your arm was twisted until you were forced to download this mod?

as a "software developer" you have no excuse for running mismatched versions of the various mods.
they are all updated and released pretty much simultaneously and updating them isn't exactly rocket science. if you utilize the notification facility on nexus, you will be notified when the mods are all updated, so how you got them out of sync, only you'll know. i would suggest as someone who has been in the software development industry for over 20 years, that it's sloppy upgrade processes on your end that have got your mods out of sync.

rather than arguing with the volunteers who are going out of their way to try and help you out of the mess you've created, so that they can get you on a stable release in order to provide further assistance (as a software developer, you should know this is standard), why not first ensure that your environment is in the correct and expected state for assistance to even begin? i mean, thats software 101....isnt it?
 
We prefer a friendly and open environment that makes all users feel welcome in this community. We also appreciate when people respect the efforts of volunteers doing their best to help. So if people on both sides of this discussion could play nicely with others that would be for the best. Thank you!
 
This thread is being Closed and moved to Archive. If the issue was not resolved or if you have a similar issue please check the forums for a report that is newer. If you cannot find one please create a new thread and mark it with the Bug tag.
Thank you
 
Top