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!

Are they ever going to get around to fixing Hub of the Problem quest?

RekkitC15

New Member
Messages
28
I just got done loading a save about 11 times doing the 4 actions in varrying order before it finally got complete. Either he just sits there at the typewriter lookin computer on the table with the ASAM sensors or just fucks off and digs in the dirt. Probably the only thing I can think of that makes me just give up on the mod.
 
Did you go back to a save before accepting that quest?
What is happening? Where is it broken for you?
Have you posted your mods load order before?
 
Did you go back to a save before accepting that quest?
What is happening? Where is it broken for you?
Have you posted your mods load order before?
Yes. And no luck. He just fuckin stands there. I hit the big red button he says woo wee look at this, then goes back to that terminal. No matter what order i do the rest of the things, the vault tek notes, the holotape, the radio. It just wont work. Is there a console command that i can do to just skipp this shit?
 
Yes. And no luck. He just fuckin stands there. I hit the big red button he says woo wee look at this, then goes back to that terminal. No matter what order i do the rest of the things, the vault tek notes, the holotape, the radio. It just wont work. Is there a console command that i can do to just skipp this shit?

Okay, i understand you are frustrated...
There are 4 things to find in the sub-basement, you've listed 3 ? I guess the red button you are talking about is the ASAM Printer?
I haven't looked up the quest stage numbers for this one to set stage by console command.
Hopefully, someone else will be able to provide that for you.
 
Okay, i understand you are frustrated...
There are 4 things to find in the sub-basement, you've listed 3 ? I guess the red button you are talking about is the ASAM Printer?
I haven't looked up the quest stage numbers for this one to set stage by console command.
Hopefully, someone else will be able to provide that for you.
yeah all 4. i've looked it up and the recomended order is either red button, radio, notes, holotape, Or Red button, notes, radio, Holotape. neither work. nor is doing any in other order.
 
Sorry.. I did just do this quest a few days ago again, before the patch and the only issue I encountered was that my companion didn't exit the sub-basement with me.
Please check again tomorrow? Someone will know the console command to help you out :)
 
Try this console command:
cqf ss2_mqmaster SkipToQuest SS2_MQ08

That command has been listed on the wiki since Day 1:

As soon as we can work out and reproduce what's actually CAUSING all these problems with the quest (I have legit never had any of the problems people keep reporting with it myself) it can be fixed.
(Apologies, I've fallen out of the habit of checking the forums every 5 minutes for new posts )

EDIT: This new "Jake becomes unresponsive once he starts using that terminal" issue has been confirmed, logged as Bug #522 for reference.
 
Last edited by a moderator:
Try this console command:
cqf ss2_mqmaster SkipToQuest SS2_MQ08

That command has been listed on the wiki since Day 1:

As soon as we can work out and reproduce what's actually CAUSING all these problems with the quest (I have legit never had any of the problems people keep reporting with it myself) it can be fixed.
(Apologies, I've fallen out of the habit of checking the forums every 5 minutes for new posts )

EDIT: This new "Jake becomes unresponsive once he starts using that terminal" issue has been confirmed, logged as Bug #522 for reference.
Ok so day later and calmed down. Sorry for cussing and what not. I will try that and see what happens. My next question is how are you not able to replicate what others are experiencing? With so many people having the issue id think replicating it would be easy. I dont know anything at all about modding so forgive my ignorance on the subject.
 
Ok so day later and calmed down. Sorry for cussing and what not. I will try that and see what happens. My next question is how are you not able to replicate what others are experiencing? With so many people having the issue id think replicating it would be easy. I dont know anything at all about modding so forgive my ignorance on the subject.
With the different mods that everyone uses it's a bit hard. At least that is my reasoning for issues occurring and the dev team having a hard time narrowing down the cause. My thinking is that to try and re-create errors the devs would need to know every mod in use during the playthrough. And the mod versions in use. Ideally, they would also need to have similar hardware, OS version, driver versions, etc. That would get them as close to re-creating the errors as possible. After that we need to take into account the flakiness of the papyrus engine. The best that they could do would be to keep a setup using the most common hardware, software, and mods. Hub of The Problem has been a... well... problem for a while. Tracking down all the little things that make it wonky is a big task. I don't know how long you've been here with SS2, but you should have seen that quest at the beginning... It was WAY worse than now.

The best thing we can do to help is provide save files, logs, mod lists, load orders, and anything else I've failed to remember. That way we can give them every chance to run down these bugs. =)
 
You basically hit the nail square on the head there, ilmlp9147. I've played the entire questline through well over 20 times (probably 30), plus console-commanding to get to specific spots on top of that, and only ever had two of the issues with "Hub of the Problem" that people have reported myself - so I'm unable to confirm what's CAUSING the issues, thus can't put in a proper 'Bug Report' (there's a procedure in place for this) on what it is so the actual coders and such can fix it. Just saying "IT BROKE" isn't enough to create a solution out of.
My only theory for most of the other problems is possible mod conflict - but in practice the combination space for "mod load order" is effectively infinite, so...
 
Last edited by a moderator:
Top