- Messages
- 1,511
So, to make this short and sweet, I have been working on the next round of released pre-builts for Nexus, showcasing the City Plan Contest winners and finalists. The round I am working on to release includes March and April - so Nordhagen, Coup Manor, Abernathy, etc...
I just completed the 1st 4 levels of batch 1, which captures all the past finalists I didn't get in, plus the new plans (of finalists) - I will do a new Winner's Circle when I have more months.
What I have found is that the time to build the pre-builts (at the vault door control panel - so player can bypass the pre-war) ... is the time to process each level, starting at the foundation to level 3 ... is 50% more at the foundation level and more than 2x at level 3 (4hrs and 46mins). File sizes of the saves are consistent with other releases, so not due to file bloat.
I am afraid I have hit a scripting limit? That's why I am asking here because a) need to overcome, b) is this even an issue... is 5hrs for a level 3 prebuilt - which is all city contest plans replacing the ROTC plan.
1) Do I need to cut settlements out? Example: Far Harbor
2) Do I start cutting out City Contest Winners/Finalists back in October..
3) Do I set % of settlements built that would over come this?
4) In Conqueror, are there settlements not so popular, not used, provide the least amount of help for the Conqueror play through
5) In Conqueror, are there settlements that have to be there for quests.
Seeing @kinggath playthrough on YouTube, I get why Greentop and Slog is next for food.
So, my first inclination is a) cut Far Harbor, b) cut Red Rocket, c) replace Contest files back with ROTC (lopping off the Contest City Plan list)... d) cut out Starlight, etc. etc. etc...
Unless there is a mechanic that would help, this is what I am going to do... or unless someone can validate for me that almost 5 hours is not a problem.
I don't want to release it because of fear it won't work and be problematice.
If anyone can provide insight / help / advice, would be greatly appreciated. More along the lines of "cut out x, y, z, 1, 2, 3 ... "
@kinggath @uituit @VersusXV @WetRats @Phil_T_Casual and any others ...
Thanks,
John
I just completed the 1st 4 levels of batch 1, which captures all the past finalists I didn't get in, plus the new plans (of finalists) - I will do a new Winner's Circle when I have more months.
What I have found is that the time to build the pre-builts (at the vault door control panel - so player can bypass the pre-war) ... is the time to process each level, starting at the foundation to level 3 ... is 50% more at the foundation level and more than 2x at level 3 (4hrs and 46mins). File sizes of the saves are consistent with other releases, so not due to file bloat.
I am afraid I have hit a scripting limit? That's why I am asking here because a) need to overcome, b) is this even an issue... is 5hrs for a level 3 prebuilt - which is all city contest plans replacing the ROTC plan.
1) Do I need to cut settlements out? Example: Far Harbor
2) Do I start cutting out City Contest Winners/Finalists back in October..
3) Do I set % of settlements built that would over come this?
4) In Conqueror, are there settlements not so popular, not used, provide the least amount of help for the Conqueror play through
5) In Conqueror, are there settlements that have to be there for quests.
Seeing @kinggath playthrough on YouTube, I get why Greentop and Slog is next for food.
So, my first inclination is a) cut Far Harbor, b) cut Red Rocket, c) replace Contest files back with ROTC (lopping off the Contest City Plan list)... d) cut out Starlight, etc. etc. etc...
Unless there is a mechanic that would help, this is what I am going to do... or unless someone can validate for me that almost 5 hours is not a problem.
I don't want to release it because of fear it won't work and be problematice.
If anyone can provide insight / help / advice, would be greatly appreciated. More along the lines of "cut out x, y, z, 1, 2, 3 ... "
@kinggath @uituit @VersusXV @WetRats @Phil_T_Casual and any others ...
Thanks,
John