When I was using the Loop Tools plugin, all the contents in the plugin didn’t work. For example, when using Gstretch in the Loop Tools plugin, the system prompted me that I didn’t recognize the marked lines. In fact, I had already drawn them. And all the operations are carried out in the editing mode. My specific operation is to create a vertex, then E squeezes out a point, then subdivides this line into 10 points, then T draws the Annotation line, and then in Gstretch, select Annotation. When I click Gstretch, it will prompt that I haven’t recognized the annotation line. The version I’m using is Blender4.4
I dont really understand your explanation. But in short, gstretch works on meshlines and just there. It needs to be just ONE chain of selected points. If you choose gstretch with an such active selection in editmode it should work.
Edit: Just read about annotations as guides. Yeah seems there was/is that option aswell, but there have been changes to annotations and greasepencil, looks like it no longer works with the new ones.
Edit2: Yeah the annotations indeed also changed. To make it work change the following two lines in the script.
line 55: strokes = bpy.data.grease_pencils[0].layers[bpy.data.grease_pencils[0].layers.active_index].active_frame.strokes
line 2893: layer = bpy.data.grease_pencils[0].layers[bpy.data.grease_pencils[0].layers.active_index]
@nickberckley : I saw you were taking the ownership. So maybe you want to include these fixes.
The Gpencil part likely needs updates too, but had no time to take a look on that.
There is talk from the devs about merging Loop Tools into main, one of the reasons is that it has not been updated for years so slowly things stop working the way they used to.
I can’t see a good reason for that.
Grease Pencil v3 changes, in 4.3, broke the Gstretch operator.
A ticket was filled, at that moment.
https://projects.blender.org/extensions/mesh_looptools/issues/4
So, the issue is not old.
According to comments, Nika will not fix the issue. But he could accept Debuk’s contribution.
One goal of Grease Pencil 3 is support of geometry nodes by Grease Pencil object.
The addon is about tools in Edit mode.
So, that could make sense to think about Node Tools to replace the add-on.
I have no opinion about the code.
But the tools, brought by the addon, are must-have to model, absent of Blender, by default.
The strength of the addon is to provide edge loop changes, keeping edges length proportions, giving same length to edges.
There is a very good reason, loop tools is one of the most used addons by all users (I think second of third). But it has not had any updates in years and will become more buggy every time there are breaking changes.
Sorry Norman, but it’s just trashtalking to say it would become more buggy every time. Looptools is a perfect usecase for an addon that was running stable for years. And now it needs some lines to fix it. Thats all. Instead there are lots of good reasons to keep addons what they are - little useful extensions outside of the mainbuild for a sleek fast blender core. As if addons would be just good if noone would use them.
The devs are trash talking?
Bugs are accumulating in Loop Tools, and do not seem to be getting attention of the developer of that addon. Nika has been looking at fixing it. There’s a large amount of math in them, so they are hard to understand and therefore fix. Wondering: could it be a good first issue to slowly rewrite those algorithms in C++ and have them in Blender?
If you want to talk with me stop reinterpreting my words that way. I can have a look at it later. I have no time to read into it now. Have to go right now.
So I read over it, but it was not explaining much though. And to be clear about that, no I dont make statements about peoples statements I didnt read or even hear about and if I read it correct its this is Nikas assessment alone and no global standpoint from the devs and I said it about you making arguments of things you, as I read now, know a single line about.
I cant relate to it being very buggy, runs pretty solid for me, anyway some bugs are accumulating and the statement that he is uncertain if he understands the math behind sounds still pretty different to your argument.
Indeed, there are 7 tickets about the addon.
Except the Gstretch issue, they are corresponding to rare use cases.
There are issues with Curve operator related to options or specific selections.
There is an issue with Circle operator related to a specific selection.
There are issues related to use of a mirror modifier ; that can be easily workaround by temporarily removing it.
Doesnt sound that much, I’ll have a look at it. Thanks for the notes on it.
When extensions platform was created for 4.2 release ; it was the occasion to get rid of maintenance of many add-ons.
There was an expectation, that they would last several releases, before accumulating issues.
But, with GP3 happening in 4.3, the breakage was instantaneous for add-ons using grease pencil.
My argument was that Blender changes and addons have to be maintained to change with it.
It is a bit much to expect the average Blender user, first to acknowledge a bug, then to work out 2 lines of code (or scan the internet for it) and then edit the loop tools script to get a function working.
All that to fix just one of the addons bugs “that are accumulating” (over time).
But don’t mind me, I just talk trash and have no idea of what I am on about.
I have no idea how you solve errors by scanning the internet, I just corrected the 2 lines of outdated code to fit the API changes and make the annotations guide work, but that’s not the point at all. I don’t expect you or your so called average user to be able to solve anything. That was never the point and I never said that. When APIs change, all tools that used what changed will fail. You can say it’s Blender’s fault because they changed the API, but that’s just as hyperbole. It’s just not true that the tool is in an increasingly bad state because of that, thats what I said and since then you try to drag me into a discussion about me being wrong and talking mean about whoever. So could you simply stop that?
(Besides that, it was only about whether it makes sense to move sufficiently well solved functionality of an addon to blender core or not, but I no longer feel like wanting to discuss that with you)
Well, yeah…
Even though issue itself is very easy to fix, code of this add-on is absolute hot garbage.
(another post)
Fix for this is actually just changing couple of lines, just where main
strokesand other related variables are defined, but the problem is that code is so awfully written that every possible error is suppressed, THE worst coding practice, so it’s impossible to debug live and see what’s going on.
I mean - i haven’t looked at the code, but Nika definitely isn’t happy with it. 
There are some news from my side, as I would still love to see the tool survive in its current form and had some sparetime this morning, I took a deeper look at the code.
Then started a code redesign, just as a proof of concept first, but all went pretty fine and smooth, the tool is honestly pretty nice to rework. I am finished with it now, I have it all restructured and its all again running fine and smooth. What changed is just behind the scenes, the tools work as before. I meanwhile started switching the code to the new grease pencil tool.
Worked on it some more, grease pencil v3 support is now also integrated and working, what means that the tool will then be v4.3++ only.
Also brought back deletion of annotations and curves.
Changed several try excepts to print exception messages again
Fixed some other minor important stuff
Overall its taking shape. Will have a look at the mirroring now.
@zeauro: Do you know whats the idea of the project option in gstretch? Wanted to try it out in 4.2 but didnt get the old gstretch working with that version.
Edit: Just tested the circle error. Either it was never a bug or it is no longer a bug. Works fine
Thank you for your work and sorry for the misunderstanding.
The next reported bug is also no bug , but a feature request. It was about making the tool work on pure edge chains. But its explicitly exlcluded/prevented in the curve tools initial checks to be just an edge and lots of other parts of the tool make usage of the vertices valences and bmeshs loops There is no quick way to add that. The tools is simply not meant to work based on just that data.
