@Matias Mendiola (mendio) What do you think?

I tested in Windows 10 and get this before maximize:

This report does not contain all the requested information, which is required for us to investigate the issue.

@Philipp Oeser (lichtwerk) I checked in 2.79 and is working equals. It looks there are some alpha cumulative effect. Not sure if this can be fixed, but it's weird to miss the texture and get a white box.

yes, I know, but what you want is a different tool that need a totally different approach.

We have doing all changes in a separate branch, not in master.

For me all is fine now and you can commit to master.

Thanks for your report, but this is not a bug, but a misunderstanding of how works the interpolation tools. The tool tries to move the point of the stroke to an interpolated position in the mid frame, but the start and end stroke must have the same number of points to get a good result or you will get what you show in your video... the end stroke has less points, so the additional points of the original stroke are discarded in the midle interpolated frame. This is not a morphing tool.

We have not implemented the F and Shift+F keys in this primitive and to be consistent with other primitives we need both.

@Charlie Jolly (charlie) We have missed the F and Shift+F keys in this primitive as we have in the other primitives. Could you implement it?

@William Reynish (billreynish) We will need a new tool icon for the poly line tool. The tool is to draw polygons clicking with the mouse.

I will do the cleanup of the old unused polyline code in gpencil.draw operator.

Thanks to you for taking the time to fill bug task.

@Piotr Nikov (piotrnikov) Do you think we can archive this task as we want to do a refactor of the grease pencil drawing engine?

In my PC I can move easily 1000 particles. My advice if you want use thousands is draw in GPencil what you want and then bake the result as texture and use this texture in a plane that you use in the particles.

Not now... maybe with the refactor of the engine (T66293) we get any idea, but grease pencil is not the best solution for particles because due the 2D nature inside the 3D environment needs a lot of tricks and it cannot be simply instantiated, so the performance will be slower than meshes for sure.

@Campbell Barton (campbellbarton) are you going to put this task as a 2.82 target?

@Campbell Barton (campbellbarton) what is the problem here? this is old code a I never had any warning in the compiler.

This is done by design and it's a limitation of the stencil used to remove the glitches in the geometry. Always the first pixel is on top. You can check this, disabling stencil in the material.

No totally sure, but I think you have proportional editing with random mode enabled, so when you move selected object any object inside the influence circle is moved.

This must be fixed already and we are unable to reproduce, so archive the task. We can open it again if needed.

The mouse / pen event management is the code of the old 2.7x and I suppose that to use the sub-pixel, you must use float instead of ints, so this would require refactoring all the code using sbuffer strokes and any function related to that, To use this data we will need time to change that I don't have (or don't want to use in this) ... I think there are other areas more important than this.

@s12a (s12a) you miss one point... all what you do in 2D is converted to 3D, so the limitation to pixels is not only due the device. I don't say it's not possible to do, but if we have to rewrite a lot of code, then it's out of scope now, and make comparison between Krita and Blender is not totally correct because their approach are totally different.. Grease Pencil is for animation, Krita is for drawing and painting pixels. I don't think we can get in Blender a tool for painting as Krita never.

And It is not entirely correct that no application uses conversion to curves. Disney Meander, used to create Paperman shortfilm, used these techniques to get a very smooth strokes converting the mouse/pen movement to curves. We tested to use raw data from the device and the UI gets unstable because we are not reading this data directly but using all Blender operator system, so add raw data to GHOST is not only for this, but for all UI also and this is not good idea.

This is what I'm doing. The arc ppoints are only created if the device is not able to provide it. In some OS's and/or deviced we get the "real" events data and don't need to create these missing points.

Adding the calculation of points of the missing arc, I get this (wip).

@LazyDodo (LazyDodo) I take the task to work in the Bezier idea inside grease pencil drawing operator, but you can investigate in the events system to check if we can improve in that area too.

It looks Clip Studio is doing the conversion to Bezier as Disney Meander does: https://www.disneyanimation.com/technology/innovations/meander

We have been testing several options and even MS-Paint has the same problem. I'm thinking that maybe the solution is not at event side, but to generate a Beziert in the segments to get a smooth transition. Using Beziert, we keep event system, don't overpopulate events and get the same result in all OS's. I need to think, but I have a rough idea already.

@LazyDodo (LazyDodo) I tested with these lines:

Maybe this give us some ideas: https://devblogs.microsoft.com/oldnewthing/20120314-00/?p=8103

@LazyDodo (LazyDodo) Sure!

I have been debug with Ghost and the events received in the operator.

You'll need to dive into GHOST

Test file, just open it and draw a curve very fast:

I have opened a more general task for this: T70765

Copied from @Brecht Van Lommel (brecht) mail:

Thanks for the report, but the issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors.

Internally, GP objects and annotations are the same and share the same code. By design, it's impossible to use annotations when you are drawing in grease pencil, so the system disable the GP object before enabling Annotations drawing and vice-versa. To get what you want the system would required a full redesign.

@Charlie Jolly (charlie) You did all perfect. My comment is because there was some misunderstanding this morning with the 2.81 branch and someone could think this commit was for 2.81 and this not the case. master branch is open, all bug fixing goes to blender-v2.81-release branch.

To clarify: This commit is for master branch only and to be included in 2.82. As this is not a critical issue we decided not include it in 2.81.

Looking at the image, the events are not received with this device. Try to test different Input Samples (including 0) and different Active Smooth and Post Processing Smooth. The feeling of the darwing depends a lot of you CPU/GPU configuration.

@Daniel Martinez Lara (pepeland) Try this patch with the pirate example.

Fixed in two commits:

Fixed in two commits:

It appears the bug has been fixed already.

Example joining the curves and then converting:

• Create one grease pencil object by curve

Testing the code, maybe the solution is create one GPencil object as curve and let the suer join the objects. In this way all will work as Blender does with all conversions.

In D6045#139099, @Antonio Vazquez (antoniov) wrote:

I have seen a problem with copying the transformation of the converted curve to GPencil object. If you convert one curve only, it works great, but if you select several curves, all of them are converted in the same grease pencil object and this is logic because we want all curves as strokes of the same object. The problem copying the transformation is that all curves are transformed with the first object and the original curves as transformed.
Original curves:

Converted to 4 strokes:

Not sure, but maybe the solution would be undo the transformation of the 2nd, 3rd, etc curve and use the original transformation of the first curve, but this could change the drawing if sencodary curves are transformed.
@Dalai Felinto (dfelinto) @Matias Mendiola (mendio) Ideas?

• Delete line copied by error in previous commit

I have been doing some tests and it was very easy to remove the converted objects, so we could include both changes in the same patch.

Remove original Curve object when converting to Strokes

@Dalai Felinto (dfelinto) I have talked with @Jeroen Bakker (jbakker) and he confirmed the right way to do the things is copying the rotation and scale because the matrix is recalculated using these values. I think we could apply this patch and make a different patch for removing the converted curve, as this is not related to this bug.

@Charlie Jolly (charlie) Do you agree this is a not supported feature, no?