Please use this thread going forward: [NKSP] Action won't queue for Resume Knitting | EA Forums - 4943777
Knitting just stopped working after the Lovestruck update and installation. I did do a no mods/clean install to test and it still happens. On a new game, I can perform knitting actions but seems like once it is saved for the first time, it breaks. I go back in and it just doesn't work. Sims won't perform actions. The exception occurs immediately upon load of world.
Report says:
Exception in Unknown timeline: Exception running Element (AttributeError: type object '[PickerRow]knitting_Picker_Resume' has no attribute 'context'), CategoryID: interaction:8631
Better Exceptions says with 10% confidence it could be related to display_name. Whatever that means.
Any help here?
Edit: Update to add Sims 4 PC, all the big packs, most of the little packs.
I have that too. (Sigh.)
"Resume Knitting Project..." and "Frog Knitting Project..." are not working anymore, no matter the type of project. No action is queued, nothing happens. New knitting projects work most of the time, but you have to complete them in one go.
I have the same message in my lastException.txt as the OP (PC, mods deactivated).
I just noticed there already is a thread for this problem:
Some hero please merge these threads...
Just wanted to add that this is what I get as well~ also only occurring since the latest patch.
@PleaseNoUsername wrote:Report says:
Exception in Unknown timeline: Exception running Element (AttributeError: type object '[PickerRow]knitting_Picker_Resume' has no attribute 'context'), CategoryID: interaction:8631
If I start a new project, it will work; but, if I don't finish it, I can't resume, getting the above error (and cannot frog)
I want to add myself as well to this bug report of not being able to resume started knitting projects. I am unable to "frog" started projects as well.
I have the same problem too, and it occurred after the lovestruck update. I can't resume already started projects, nor can i ''frog'' in progress knitting project. I can start new ones and finish it, but it's really frustrating that if i start a project, my sim HAS to finish it, or else it'll be stuck in the ''resume knitting project'' option and i can't do anything with it at all.
At this point, it's starting to get ridiculous to how much is breaking. Knitting is breaking, paying bills is broken and who knows what more is an issue at this point. I know there is an issue with if sims is uploaded to the gallery wearing crafted jewelry from Crystal Creation. It will generate an error if you have MCCC, and apparently, if you have uploaded sims to the gallery, and downloading them, it will generate a LE exception. This is a HUGE problem if someone uploads a sim to the gallery and share it so it can show up in other people's cupids corner. What a mess!
Got a little sidetracked, but anyhow, this knitting issue is not very fun. I really hope this is fixed soon and i for sure hope for a fix for the other issues i've seen reported that i also have in my game (Paying bills for example!)
Well, it's been a month and I still can't play a game I paid money for.
Product: The Sims 4
Platform:PC
Which language are you playing the game in? English
How often does the bug occur? Every time (100%)
What is your current game version number? 1.108.335.1020
What expansions, game packs, and stuff packs do you have installed? All of them.
Steps: How can we find the bug ourselves? Have a sim start knitting, cancel the interaction, then try to resume the project.
What happens when the bug occurs? Sims will not resume a knitting project nor frog the project.
What do you expect to see? Sims to finish the knitting project.
Have you installed any customization with the game, e.g. Custom Content or Mods? Yes.
Did this issue appear after a specific patch or change you made to your system? Yes
Please describe the patch or change you made. I downloaded Lovestruck and updated my game to the newest version.
I've tried knitting on chairs, beds, or just clicking the knitting basket in the sim's inventory. Nothing works. There's no routing issues or canceled interactions in the queue, they just don't do anything at all.
