You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is something that completely ruins newly created and previous lineart strokes in 80% of the time.
It would be better if Pencil2d at least did not alter the older line strokes that the artist is presumably already happy with. The auto glue behaviour should only affect the newly created line stroke.
I made a short video in order to illustrate where this automatic "merge" behavior simply ruins inking workflow. http://youtu.be/ArnFs9gC4r4
My request is to disable automerge completely by default
and/or let the artists disable it optionally with a tick box!
It makes inking work very frustrating and counter-productive.
The text was updated successfully, but these errors were encountered:
As of 2018 the vector engine has become beyond broken, since the original behavior described in this issue is no longer present (as merging was removed entirely) the engine needs a complete overhaul considering the newest changes made it almost unusable. Once this engine has been enhanced please check on this issue again to consider it as a feature request rather than a bugfix in order to have an optional merging behavior for vector control points on fills and strokes.
This is something that completely ruins newly created and previous lineart strokes in 80% of the time.
It would be better if Pencil2d at least did not alter the older line strokes that the artist is presumably already happy with. The auto glue behaviour should only affect the newly created line stroke.
I made a short video in order to illustrate where this automatic "merge" behavior simply ruins inking workflow.
http://youtu.be/ArnFs9gC4r4
My request is to disable automerge completely by default
and/or let the artists disable it optionally with a tick box!
It makes inking work very frustrating and counter-productive.
The text was updated successfully, but these errors were encountered: