Weird artifacts with Grease Pencil V2 #49018

Closed
opened 2016-08-05 09:09:33 +02:00 by Laura · 24 comments

System Information
MAC OS X 10.11
Graphics: AMD Radeon HD 6750M 512 MB
Blender Version
Blender 2.77 (Date: 2016-08-04 01:10 Hash: 14720e2)

Short description of error
When trying the new Grease Pencil using whatever stroke placement (except View) I get weird artifacts. (attached image)Captura de pantalla 2016-08-04 a las 21.18.43.png

Exact steps for others to reproduce the error
You dont have to do anything in special, it happens always.

**System Information** MAC OS X 10.11 Graphics: AMD Radeon HD 6750M 512 MB **Blender Version** Blender 2.77 (Date: 2016-08-04 01:10 Hash: 14720e2) **Short description of error** When trying the new Grease Pencil using whatever stroke placement (except View) I get weird artifacts. (attached image)![Captura de pantalla 2016-08-04 a las 21.18.43.png](https://archive.blender.org/developer/F333022/Captura_de_pantalla_2016-08-04_a_las_21.18.43.png) **Exact steps for others to reproduce the error** You dont have to do anything in special, it happens always.
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @laurasirco

Added subscriber: @laurasirco

#53067 was marked as duplicate of this issue

#53067 was marked as duplicate of this issue

Added subscribers: @antoniov, @mont29

Added subscribers: @antoniov, @mont29

I cannot really confirm that here from quick test… @antoniov Maybe you can check it too?

I cannot really confirm that here from quick test… @antoniov Maybe you can check it too?
Member

Added subscriber: @JoshuaLeung

Added subscriber: @JoshuaLeung
Member

View-aligned strokes should be ok because we manually tesselate and draw those, while 3d strokes are currently drawn using whatever your driver does.

I've heard of similar types of errors before, and IIRC last time it ended up being something on the OpenGL drivers side (since the test file in that case provided worked fine on my machine).

However, just in case there's something else going on, I'd like to clarify a few points:

  • Were all these strokes drawn using the same brush type? And did you try out any of the other settings on any of these strokes (in particular, any of the randomise/jitter stuff)?
  • What did you use to draw these strokes? A mouse or tablet?
  • Did using similar drawing settings with a build from before the GP v2 merge - so basically, anything from the past month or so up till 3-4 days ago (if you can get hold of one) - and drawing similar shaped curves do something similar?
  • Can you go into editmode and show us where the stroke points are located?
    ** And/or to make it easier to test, please upload a test file :)
View-aligned strokes should be ok because we manually tesselate and draw those, while 3d strokes are currently drawn using whatever your driver does. I've heard of similar types of errors before, and IIRC last time it ended up being something on the OpenGL drivers side (since the test file in that case provided worked fine on my machine). However, just in case there's something else going on, I'd like to clarify a few points: * Were **all** these strokes drawn using the same brush type? And did you try out any of the other settings on any of these strokes (in particular, any of the randomise/jitter stuff)? * What did you use to draw these strokes? A mouse or tablet? * Did using similar drawing settings with a build from before the GP v2 merge - so basically, anything from the past month or so up till 3-4 days ago (if you can get hold of one) - and drawing similar shaped curves do something similar? * Can you go into editmode and show us where the stroke points are located? ** And/or to make it easier to test, please upload a test file :)

We need the blend file to test if this is a problem, but I agree with aligorith about OpenGL driver.

One point to test is if the drawing was done with a tablet and be sure the pressure is working. I had some problems with this using a Wacom Intuous 3 (the driver suddenly loose the pressure) and the problem was not only in Blender but in Photoshop also.

Check the curves of the drawing brushes, maybe you have defined something weird.

We need the blend file to test if this is a problem, but I agree with aligorith about OpenGL driver. One point to test is if the drawing was done with a tablet and be sure the pressure is working. I had some problems with this using a Wacom Intuous 3 (the driver suddenly loose the pressure) and the problem was not only in Blender but in Photoshop also. Check the curves of the drawing brushes, maybe you have defined something weird.
Author

In #49018#384930, @JoshuaLeung wrote:
View-aligned strokes should be ok because we manually tesselate and draw those, while 3d strokes are currently drawn using whatever your driver does.

I've heard of similar types of errors before, and IIRC last time it ended up being something on the OpenGL drivers side (since the test file in that case provided worked fine on my machine).

However, just in case there's something else going on, I'd like to clarify a few points:

  • Were all these strokes drawn using the same brush type? And did you try out any of the other settings on any of these strokes (in particular, any of the randomise/jitter stuff)?
  • What did you use to draw these strokes? A mouse or tablet?
  • Did using similar drawing settings with a build from before the GP v2 merge - so basically, anything from the past month or so up till 3-4 days ago (if you can get hold of one) - and drawing similar shaped curves do something similar?
  • Can you go into editmode and show us where the stroke points are located?
    ** And/or to make it easier to test, please upload a test file :)

I had used different brush settings in the strokes y draw, but I did not touch any of the settings of them. I used a Wacom Cintiq to draw them. I can remember that in the old grease pencil got these kind of artifacts too, not only in this version.
I attach too a capture with all the strokes in edit mode selected, so you can see the points of the strokes seems to be well located: Captura de pantalla 2016-08-05 a las 18.20.41.png
I also attach the file: greasepencilraro.blend

> In #49018#384930, @JoshuaLeung wrote: > View-aligned strokes should be ok because we manually tesselate and draw those, while 3d strokes are currently drawn using whatever your driver does. > > I've heard of similar types of errors before, and IIRC last time it ended up being something on the OpenGL drivers side (since the test file in that case provided worked fine on my machine). > > However, just in case there's something else going on, I'd like to clarify a few points: > * Were **all** these strokes drawn using the same brush type? And did you try out any of the other settings on any of these strokes (in particular, any of the randomise/jitter stuff)? > * What did you use to draw these strokes? A mouse or tablet? > * Did using similar drawing settings with a build from before the GP v2 merge - so basically, anything from the past month or so up till 3-4 days ago (if you can get hold of one) - and drawing similar shaped curves do something similar? > * Can you go into editmode and show us where the stroke points are located? > ** And/or to make it easier to test, please upload a test file :) I had used different brush settings in the strokes y draw, but I did not touch any of the settings of them. I used a Wacom Cintiq to draw them. I can remember that in the old grease pencil got these kind of artifacts too, not only in this version. I attach too a capture with all the strokes in edit mode selected, so you can see the points of the strokes seems to be well located: ![Captura de pantalla 2016-08-05 a las 18.20.41.png](https://archive.blender.org/developer/F333180/Captura_de_pantalla_2016-08-05_a_las_18.20.41.png) I also attach the file: [greasepencilraro.blend](https://archive.blender.org/developer/F333179/greasepencilraro.blend)

I have tested and in my PC looks right.

I have seen only a small gap in some curves, but this is normal and can be solved drawing with a bigger subdivision level.

05-08-2016 18-44-32.jpg

You talk that this problem was before merge GPv2, so maybe you have any driver issue.

Try with Blender 2.76 to see if you get the same problem.

I have tested and in my PC looks right. I have seen only a small gap in some curves, but this is normal and can be solved drawing with a bigger subdivision level. ![05-08-2016 18-44-32.jpg](https://archive.blender.org/developer/F333189/05-08-2016_18-44-32.jpg) You talk that this problem was before merge GPv2, so maybe you have any driver issue. Try with Blender 2.76 to see if you get the same problem.

Added subscriber: @YAFU

Added subscriber: @YAFU

To see if it is a problem with the graphics tablet on your OS. Could you try if you have the same kind of problems in .blend files I had shared here?
https://developer.blender.org/T48204

You try drawing on the plane in texture paint mode. You could also try drawing curves in edit mode.

Edit:
By the way, at that time in my report I had said that I was not sure my problem with graphic tablet affected GP too. In fact GP wass affected too, just had to use bigger stroke px to be able to apreciate the problem.

To see if it is a problem with the graphics tablet on your OS. Could you try if you have the same kind of problems in .blend files I had shared here? https://developer.blender.org/T48204 You try drawing on the plane in texture paint mode. You could also try drawing curves in edit mode. Edit: By the way, at that time in my report I had said that I was not sure my problem with graphic tablet affected GP too. In fact GP wass affected too, just had to use bigger stroke px to be able to apreciate the problem.
Author

I just tested old Grease Pencil in 2.76 and still happens.
Captura de pantalla 2016-08-05 a las 19.23.16.png

I tested YAFU file and tried to paint in texture mode and everything seems OK, it only happens with grease pencil.
Captura de pantalla 2016-08-05 a las 19.19.25.png

I just tested old Grease Pencil in 2.76 and still happens. ![Captura de pantalla 2016-08-05 a las 19.23.16.png](https://archive.blender.org/developer/F333202/Captura_de_pantalla_2016-08-05_a_las_19.23.16.png) I tested YAFU file and tried to paint in texture mode and everything seems OK, it only happens with grease pencil. ![Captura de pantalla 2016-08-05 a las 19.19.25.png](https://archive.blender.org/developer/F333200/Captura_de_pantalla_2016-08-05_a_las_19.19.25.png)

GP is totally different of paint textures and uses different drawing routines.

GP is totally different of paint textures and uses different drawing routines.

Yes, but if this was a particular problem with the graphics tablet like this I had, then the problem should be present in texture paint, curve draw and GP (exactly like the problem I had). Sorry if I intruded on the report, I just requetsed the test to discard that this could be a general problem with the graphics tablet in Blender or system, because I had seen those similar artifacts that I had that time.

Yes, but if this was a particular problem with the graphics tablet like this I had, then the problem should be present in texture paint, curve draw and GP (exactly like the problem I had). Sorry if I intruded on the report, I just requetsed the test to discard that this could be a general problem with the graphics tablet in Blender or system, because I had seen those similar artifacts that I had that time.

So what now? This totally looks like GPU/Driver issue, if so nothing we can do on our end really. And we don’t even have softwaregl on OSX to validate driver issue iirc?

So what now? This totally looks like GPU/Driver issue, if so nothing we can do on our end really. And we don’t even have softwaregl on OSX to validate driver issue iirc?

Added subscriber: @Sergey

Added subscriber: @Sergey

AFAIK this is caused by ambiguity of lines rasterization in different OpenGL drivers: some of them might always ratserize caps either vertically or horizontally.

Wouldn't know of a quick solution, usually to deal with such things own triangulaiton is used. Drawing a circle in the joint point could also work around the problem.

AFAIK this is caused by ambiguity of lines rasterization in different OpenGL drivers: some of them might always ratserize caps either vertically or horizontally. Wouldn't know of a quick solution, usually to deal with such things own triangulaiton is used. Drawing a circle in the joint point could also work around the problem.

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Bastien Montagne self-assigned this 2016-09-02 08:53:35 +02:00

Added subscriber: @MikeErwin

Added subscriber: @MikeErwin

So let’s close this a OGL limitation (or driver bug) then… That kind of thing is also likely to be solvable with new viewport of 2.8 (and its geometry shaders), @MikeErwin?

So let’s close this a OGL limitation (or driver bug) then… That kind of thing is also likely to be solvable with new viewport of 2.8 (and its geometry shaders), @MikeErwin?
Member

Right, in 2.8 we'll have more control over how strokes are drawn. We'll make sure it's done beautifully!

@Sergey AFAIK non-smooth wide lines are specified to draw with horizontal or vertical caps depending on line slope. But smooth wide lines are supposed to be line-aligned rectangles? No matter the details we'll make it do what we prefer for 2.8.

Right, in 2.8 we'll have more control over how strokes are drawn. We'll make sure it's done beautifully! @Sergey AFAIK non-smooth wide lines are specified to draw with horizontal or vertical caps depending on line slope. But smooth wide lines are supposed to be line-aligned rectangles? No matter the details we'll make it do what we prefer for 2.8.
Member

Added subscribers: @Silver_Phabric, @FloridaJo, @mendio

Added subscribers: @Silver_Phabric, @FloridaJo, @mendio

Sounds great although I am using 2.79 for commercial purposes and the current WIP releases of 2.8 on the blender website are missing the GP tool updates.

Will this mean I have to wait too long for 2.8? Maybe I can get a test build or perhaps tweak some Open GL settings?

Sounds great although I am using 2.79 for commercial purposes and the current WIP releases of 2.8 on the blender website are missing the GP tool updates. Will this mean I have to wait too long for 2.8? Maybe I can get a test build or perhaps tweak some Open GL settings?
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
9 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#49018
No description provided.