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!

Solved Tech Tree wont go away

ketrack

New Member
Messages
8
I have this issue where no matter where I am when I hit the left trigger on my controller the tech tree shows up. How do I get rid of that? Also, what is recommended to be done when a new patch is installed? Should I be refreshing all of my plots?
 
This is not a mistake, it appears instantly when you interact without waiting when the game has just started. In order not to see this, you should wait a little when you open the game.(After opening the save game)
 
Last edited:
I just started getting this bug. It is not from interacting with things after the game just started. If I do the too fast interactions it gives the "wait 60 seconds message". What I am getting is the full-blown tech tree across my screen any time that I try and aim down my sights. Quite a nice thing to have to happen in the middle of a firefight. It is almost like the tech tree has hot keyed itself to my right mouse button with no way of getting rid of it. It will bring it up even if I am nowhere near a settlement. I really like SS but at this point I might just have to ditch it if I literally can't play the game without a tech tree screen covering my view.
 
much of a year later, after getting frustrated with the state of SS2, i decided to do an SS1 run.

figured, at least there would be bugs that it's possible for me to contend with, without all of the frustrations i'd been dealing with.

then i got this bug suddenly partway through a run: attempting to aim (with left trigger, as i play with gamepad) trying to bring up the tech tree screen no matter where i am. in settlement? attempts to bring up tech tree. out of settlement? attempts to bring up tech tree.

i have no idea what triggered this, as an earlier save (some time prior, due to being a survival run) doesn't exhibit the problem, but not knowing the cause of a failure like this just means it's going to happen again at some point even if i do roll back.

and why on earth is this flagged as solved, when there's no evidence of a solution in this thread?
 
Top