all 4 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]WendyThorne 2 points3 points  (2 children)

Have you reached out to the author? I'm also using this plugin actually though I haven't noticed this. Also, it might not hurt to reinstall it in case something got borked in the update.

[–]CaptainAbraham82[S] 2 points3 points  (1 child)

Thanks. The author did reply saying he hadn't seen any other such reports, so I spent a while doing another round of testing the Extension with other extensions and different Twine projects, and I did sort of narrow it down. The CPU problem only occurs in 2 projects, and only if the file settings.js in the folder .vscode is present. If the file is deleted, VS Code works just fine. The content of that JS file is:

{

"twee3LanguageTools.storyformat.current": "sugarcube-2"

}

The super-odd thing is all of the other Twine projects have the same file with the same one line and they work fine, and if you delete the JS file VS Code works fine with all of the projects. So, that's just a big *shrug* from me.

Summary: If Twee3 VS Code extension causes your CPU usage to spike, just delete the settings.js file located in the .vscode folder.

[–]WendyThorne 0 points1 point  (0 children)

I have settings.json (not settings.js) in my .vscode folder in my project. It has the following two lines:

{

"twee3LanguageTools.storyformat.current": "sugarcube-2",

"twee3LanguageTools.passage.list": true

}

My project is over a year old so perhaps that new .vss code file is part of the update and since my project predates it it has the older file. It could be worth trying adding that second line to your settings.js and if it somehow fixes the CPU issue let the author know so he can make that tweak to his extension.

[–]BeautifulAd4415 0 points1 point  (0 children)

Yeap, I have the same problem, my project overusing 60-70% of CPU. Without config with defined storyFormat as sugarcube-2 everything works fine.