GPencil. Boundary strokes are visible in renders #80128

Closed
opened 2020-08-26 10:33:32 +02:00 by Tomasz Kaye · 12 comments

System Information
Operating system: Darwin-19.3.0-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro 580 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.5.5

Blender Version
Broken: version: 2.91.0 Alpha, branch: master, commit date: 2020-08-13 18:18, hash: 275f1039d2
Worked: 2.91.0 Alpha, branch: master, commit date: 2020-08-09 00:04, hash: b522e834ec

Short description of error
Boundary strokes created using Alt+LMB with the fill tool selected have a thickness and show up in renders. This applies to newly created boundary strokes as well as boundary strokes in .blend files created in earlier versions.

old version:
Screenshot 2020-08-26 at 10.25.27.png

broken version:
Screenshot 2020-08-26 at 10.25.49.png

Exact steps for others to reproduce the error

  • new > 2d animation
  • select fill tool, choose Solid Fill as the material
  • Holding alt, drag a line with the LMB
  • a visible stroke appears
**System Information** Operating system: Darwin-19.3.0-x86_64-i386-64bit 64 Bits Graphics card: AMD Radeon Pro 580 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.5.5 **Blender Version** Broken: version: 2.91.0 Alpha, branch: master, commit date: 2020-08-13 18:18, hash: `275f1039d2` Worked: 2.91.0 Alpha, branch: master, commit date: 2020-08-09 00:04, hash: `b522e834ec` **Short description of error** Boundary strokes created using Alt+LMB with the fill tool selected have a thickness and show up in renders. This applies to newly created boundary strokes as well as boundary strokes in .blend files created in earlier versions. old version: ![Screenshot 2020-08-26 at 10.25.27.png](https://archive.blender.org/developer/F8811738/Screenshot_2020-08-26_at_10.25.27.png) broken version: ![Screenshot 2020-08-26 at 10.25.49.png](https://archive.blender.org/developer/F8811740/Screenshot_2020-08-26_at_10.25.49.png) **Exact steps for others to reproduce the error** * new > 2d animation * select fill tool, choose Solid Fill as the material * Holding alt, drag a line with the LMB * a visible stroke appears
Author

Added subscriber: @info-27

Added subscriber: @info-27

Added subscribers: @pepe-school-land, @antoniov

Added subscribers: @pepe-school-land, @antoniov

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'

This is by design. By error, we removed the visibility of these strokes in 2.8x, but in older versions these strokes were visible. Talking with @pepe-school-land, we decided that must be visible in order to "know" what you are doing, so I recently fixed this issue.

If you need remove all these boundary strokes, there are Cleanup tools designed for that.

image.png

Maybe, we could add in the future an option to decide if you want or not to see these strokes, or hide only in render.

@pepe-school-land what do you think of hide them in render?

Edit: I missed to add this change to 2.91 release notes.

This is by design. By error, we removed the visibility of these strokes in 2.8x, but in older versions these strokes were visible. Talking with @pepe-school-land, we decided that must be visible in order to "know" what you are doing, so I recently fixed this issue. If you need remove all these boundary strokes, there are Cleanup tools designed for that. ![image.png](https://archive.blender.org/developer/F8811927/image.png) Maybe, we could add in the future an option to decide if you want or not to see these strokes, or hide only in render. @pepe-school-land what do you think of hide them in render? Edit: I missed to add this change to 2.91 release notes.

This is the commit that changed this: ebf5ff8afb

This is the commit that changed this: ebf5ff8afb9a
Author

Got it! i don't mind them being visible, can help avoid confusion. Though hidden in render seems like a good idea to me.

I wonder if it'd be possible to have them display in a visually distinctive way (e.g. brightly coloured stripes) to make it easy to quickly identify them, and not confuse them with regular strokes.

Got it! i don't mind them being visible, can help avoid confusion. Though hidden in render seems like a good idea to me. I wonder if it'd be possible to have them display in a visually distinctive way (e.g. brightly coloured stripes) to make it easy to quickly identify them, and not confuse them with regular strokes.

Added subscriber: @mendio

Added subscriber: @mendio

@info-27 I'm working in the change to hide in render, but I would like to hear @pepe-school-land and @mendio opinion first.

About different color... with the new engine this is complex due a limitation in the number of bits we are using in the GPU (we haven't room for more). Anyway, if you are using a material for fill not using the stroke color, you could use a bright color as stroke to know is a boundary. Of course, if I add the patch to hide in Render modes, then it would be better.

For example:

image.png

@info-27 I'm working in the change to hide in render, but I would like to hear @pepe-school-land and @mendio opinion first. About different color... with the new engine this is complex due a limitation in the number of bits we are using in the GPU (we haven't room for more). Anyway, if you are using a material for fill not using the stroke color, you could use a bright color as stroke to know is a boundary. Of course, if I add the patch to hide in Render modes, then it would be better. For example: ![image.png](https://archive.blender.org/developer/F8812067/image.png)

Ok for me 👍

Ok for me 👍

yes, it makes sense to me to hide the boundary lines in the rendered shading mode. It will also help to easily detect those lines when changing modes.

yes, it makes sense to me to hide the boundary lines in the rendered shading mode. It will also help to easily detect those lines when changing modes.

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Antonio Vazquez self-assigned this 2020-08-26 15:25:25 +02:00

Implemented the hide in render mode in commit 826bd46e66

Implemented the hide in render mode in commit 826bd46e661b
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
4 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#80128
No description provided.