Edit mode, Clipping region, Visuals bug and editing vertices remain slow like when geometry is not hidden #62792

New Issue

noki paike · 2019-03-20T22:46:41+01:00

noki paike commented

2019-03-20 22:46:41 +01:00

System Information
Operating system: Windows-10-10.0.17763 64 Bits
Graphics card: AMD Radeon HD 7600M Series ATI Technologies Inc. 4.5.13417 Core Profile Context 0

Blender Version
Broken: version: 2.80 (sub 51), branch: master, commit date: 2019-03-20 16:33, hash: b6d1946c2e
Worked: (optional)

Short description of error
Edit mode, Clipping region, Visuals bug and editing vertices remain slow like when geometry is not hidden

Exact steps for others to reproduce the error

1 create a sphere and subdivide it many times until the model becomes heavy to edit
2 clipping region a part of the geometry and you will see the visual bug
3 try editing the non-hidden geometry and you will notice that it continues to be slow as if the rest of the geometry had not been hidden.

clipbug.blend

**System Information** Operating system: Windows-10-10.0.17763 64 Bits Graphics card: AMD Radeon HD 7600M Series ATI Technologies Inc. 4.5.13417 Core Profile Context 0 **Blender Version** Broken: version: 2.80 (sub 51), branch: master, commit date: 2019-03-20 16:33, hash: `b6d1946c2e` Worked: (optional) **Short description of error** Edit mode, Clipping region, Visuals bug and editing vertices remain slow like when geometry is not hidden **Exact steps for others to reproduce the error** - 1 create a sphere and subdivide it many times until the model becomes heavy to edit - 2 clipping region a part of the geometry and you will see the visual bug - 3 try editing the non-hidden geometry and you will notice that it continues to be slow as if the rest of the geometry had not been hidden. ![Screenshot (91).jpg](https://archive.blender.org/developer/F6857490/Screenshot__91_.jpg) [clipbug.blend](https://archive.blender.org/developer/F6857499/clipbug.blend)

noki paike commented

2019-03-20 22:46:41 +01:00

Added subscriber: @nokipaike

matc commented

2019-03-21 00:54:54 +01:00

Added subscriber: @matc

matc commented

2019-03-21 00:54:54 +01:00

Not sure if this is by design. But proportional editing appears to be able to change the mesh outside of the clipped region (Alt+B), unlike with hidden vertices (H, Alt+H).

To reproduce the visual bug, I had to hide (H) half of the sphere first, then clip (Alt+B) to a visible quarter. This lead the previously not hidden quarter to be partially visible outside of the clipped region.

Not sure if this is by design. But proportional editing appears to be able to change the mesh outside of the clipped region (Alt+B), unlike with hidden vertices (H, Alt+H). To reproduce the visual bug, I had to hide (H) half of the sphere first, then clip (Alt+B) to a visible quarter. This lead the previously not hidden quarter to be partially visible outside of the clipped region.

noki paike commented

2019-03-21 07:09:19 +01:00

in my case I just need to press Clipping region ...
but I think it's due to the fact that my gpu is part of the workarounds-gpu's

anyway, what matters to me much more is the fact that even with clipping region the geometry continues to be difficult to edit on heavy models ... and if it stays that way, this function is practically useless

in my case I just need to press Clipping region ... but I think it's due to the fact that my gpu is part of the workarounds-gpu's anyway, what matters to me much more is the fact that even with clipping region the geometry continues to be difficult to edit on heavy models ... and if it stays that way, this function is practically useless

Sebastian Parborg commented

2019-03-21 11:47:40 +01:00

Added subscriber: @ZedDB

Sebastian Parborg commented

2019-03-21 11:47:40 +01:00

I can't reproduce the visual bug with by just open the file, so I guess that part is a EOL GPU bug.

@matc what GPU do you have?

The clipping plane is not for speeding up mesh operators. It for speeding up drawing (or simply hiding objects) in the viewport by not rendering them.
So the only thing that is a bug here is the visual part.

I can't reproduce the visual bug with by just open the file, so I guess that part is a EOL GPU bug. @matc what GPU do you have? The clipping plane is not for speeding up mesh operators. It for speeding up drawing (or simply hiding objects) in the viewport by not rendering them. So the only thing that is a bug here is the visual part.

matc commented

2019-03-21 22:36:17 +01:00

The file does not have the bug for me by default either.

@ZedDB RX 580. I don't think its hardware related. It looks like there is a different shader used for the parts outside of a partially clipped mesh.

Hiding parts of the mesh is not the problem here. If there are no hidden parts the outline is still showing.

Edit mode:

Object mode:

Another thing I noticed is when moving a partially clipped object in Rendered mode. This is probably the only unintentional thing here.

The file does not have the bug for me by default either. @ZedDB RX 580. I don't think its hardware related. It looks like there is a different shader used for the parts outside of a partially clipped mesh. Hiding parts of the mesh is not the problem here. If there are no hidden parts the outline is still showing. Edit mode: ![clipped_hidden_edit_mode.PNG](https://archive.blender.org/developer/F6862263/clipped_hidden_edit_mode.PNG) Object mode: ![clipped_hidden_object_mode.PNG](https://archive.blender.org/developer/F6862264/clipped_hidden_object_mode.PNG) Another thing I noticed is when moving a partially clipped object in Rendered mode. This is probably the only unintentional thing here. ![clipped_rendered_object_mode.PNG](https://archive.blender.org/developer/F6862306/clipped_rendered_object_mode.PNG)

noki paike commented

2019-03-21 23:47:08 +01:00

Added subscribers: @fclem, @mano-wii

noki paike commented

2019-03-21 23:47:08 +01:00

In #62792#645509, @ZedDB wrote:
The clipping plane is not for speeding up mesh operators. It for speeding up drawing (or simply hiding objects) in the viewport by not rendering them.
So the only thing that is a bug here is the visual part.

ok i checked and the same thing happens on blender 2.79 ... but too bad ...
because if I select the piece of geometry that I am interested in editing, if I press the shortcut "p" to separate the geometry, that piece immediately becomes light as a feather ...
so I ask and I suggest you guys ..
@fclem
@mano-wii
it would be too complex conceptually a thing, if during "the phase of moving vertices" until the end of the operation:
to automatically separate a piece of geometry of a slightly larger area than the vertices being edited making it a separate object, and then make a "join" and a "merge vertex/remove doubles" at to finished editing operation"

> In #62792#645509, @ZedDB wrote: > The clipping plane is not for speeding up mesh operators. It for speeding up drawing (or simply hiding objects) in the viewport by not rendering them. > So the only thing that is a bug here is the visual part. ok i checked and the same thing happens on blender 2.79 ... but too bad ... because if I select the piece of geometry that I am interested in editing, **if I press the shortcut "p" to separate the geometry, that piece immediately becomes light as a feather ...** so I ask and I suggest you guys .. @fclem @mano-wii it would be too complex conceptually a thing, if during "the phase of moving vertices" until the end of the operation: **to automatically separate a piece of geometry of a slightly larger area than the vertices being edited making it a separate object, and then make a "join" and a "merge vertex/remove doubles" at to finished editing operation"**

noki paike commented

2019-03-22 00:13:36 +01:00

In #62792#645509, @ZedDB wrote:
I can't reproduce the visual bug with by just open the file, so I guess that part is a EOL GPU bug.

try to open the file with "load UI" option actived

> In #62792#645509, @ZedDB wrote: > I can't reproduce the visual bug with by just open the file, so I guess that part is a EOL GPU bug. try to open the file with "load UI" option actived

Sebastian Parborg commented

2019-03-25 13:05:13 +01:00

Still can't seem to reproduce this on my end.

matc commented

2019-03-25 15:54:22 +01:00

@ZedDB This has been fixed with 7454fa927b and 106551b9ad. Clipping does not look like it's implemented in a way that would enhance performance.

This would be the only remaining bug in this thread.

Steps to reproduce

Open default .blend
Switch to "Rendered" shading
Select a clipping region (size and position are irrelevant)
Rotate the viewport, the "Cube" appears to be producing some sort of traces when in motion.

@ZedDB This has been fixed with 7454fa927b80118 and 106551b9ad1f12. Clipping does not look like it's implemented in a way that would enhance performance. This would be the only remaining bug in this thread. ![clipped_rendered_object_mode.PNG](https://archive.blender.org/developer/F6862306/clipped_rendered_object_mode.PNG) **Steps to reproduce** - Open default .blend - Switch to "Rendered" shading - Select a clipping region (size and position are irrelevant) - Rotate the viewport, the "Cube" appears to be producing some sort of traces when in motion.

Sebastian Parborg commented

2019-03-25 16:20:27 +01:00

@matc I can not reproduce that either. So I'm guessing this is driver related.

@fclem can you reproduce these artifacts?

@matc I can not reproduce that either. So I'm guessing this is driver related. @fclem can you reproduce these artifacts?

matc commented

2019-03-25 16:43:48 +01:00

@ZedDB Does clipping work properly for you in Rendered?

Sebastian Parborg commented

2019-03-25 18:47:29 +01:00

@matc the rendered object is not clipped (known limitation), but I do not get the rendering artifacts you describe.

matc commented

2019-03-25 20:31:31 +01:00

On linux it looks good for me too.

noki paike commented

2019-03-26 09:19:08 +01:00

I downloaded the latest build blender-2.80-adfdae3fc2f4-win64
the bug has remained unchanged , at this point, I think it was only fixed for the **non-**workaround gpus

I downloaded the latest build blender-2.80-adfdae3fc2f4-win64 the bug has remained unchanged , at this point, I think it was only fixed for the **non-**workaround gpus ![Screenshot (105).jpg](https://archive.blender.org/developer/F6884753/Screenshot__105_.jpg)

matc commented

2019-04-01 21:20:49 +02:00

Without this line my artifacts disappear.

diff --git a/source/blender/draw/engines/eevee/shaders/lit_surface_vert.glsl b/source/blender/draw/engines/eevee/shaders/lit_surface_vert.glsl
index 141d3363a09..043a7b757f3 100644
--- a/source/blender/draw/engines/eevee/shaders/lit_surface_vert.glsl
+++ b/source/blender/draw/engines/eevee/shaders/lit_surface_vert.glsl
@@ -71,7 +71,6 @@ void main()
 #endif
 
 	/* Used for planar reflections */
-	gl_ClipDistance[0] = dot(vec4(worldPosition, 1.0), ClipPlanes[0]);
 
 #ifdef USE_ATTR
 	pass_attr(pos);

Without this line my artifacts disappear. ``` diff --git a/source/blender/draw/engines/eevee/shaders/lit_surface_vert.glsl b/source/blender/draw/engines/eevee/shaders/lit_surface_vert.glsl index 141d3363a09..043a7b757f3 100644 --- a/source/blender/draw/engines/eevee/shaders/lit_surface_vert.glsl +++ b/source/blender/draw/engines/eevee/shaders/lit_surface_vert.glsl @@ -71,7 +71,6 @@ void main() #endif /* Used for planar reflections */ - gl_ClipDistance[0] = dot(vec4(worldPosition, 1.0), ClipPlanes[0]); #ifdef USE_ATTR pass_attr(pos); ``` ![clipped_rendered_object_mode.PNG](https://archive.blender.org/developer/F6862306/clipped_rendered_object_mode.PNG)

Clément Foucault was assigned by Sebastian Parborg

2019-04-01 21:30:51 +02:00

blender-admin commented

2019-04-18 14:37:07 +02:00

This issue was referenced by f41ab375f3

This issue was referenced by f41ab375f38b0f828701f846fe33ec1d8ebd320e

Germano Cavalcante commented

2019-04-18 15:10:04 +02:00

Changed status from 'Open' to: 'Resolved'

Germano Cavalcante closed this issue

2019-04-18 15:10:04 +02:00

rogual commented

2022-11-22 13:05:25 +01:00

Added subscriber: @rogual

rogual commented

2022-11-22 13:05:25 +01:00

I'm seeing this as of commit a3877d8fe4 (Fri Nov 11 11:49:54 2022), and also on Blender 3.3.

My system:
MacBook Pro (2017)
MacOS Mojave 10.14.6
Intel Iris Plus Graphics 640 1536 MB

clipbug.mp4

I'm seeing this as of commit a3877d8fe4094c0502acdacfd15880da10260769 (Fri Nov 11 11:49:54 2022), and also on Blender 3.3. My system: MacBook Pro (2017) MacOS Mojave 10.14.6 Intel Iris Plus Graphics 640 1536 MB [clipbug.mp4](https://archive.blender.org/developer/F13960153/clipbug.mp4)

Sybren A. Stüvel referenced this issue

2024-04-29 11:19:27 +02:00

Anim: Per bone wire width for custom shapes #120176

Sign in to join this conversation.

6 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#62792

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Edit mode, Clipping region, Visuals bug and editing vertices remain slow like when geometry is not hidden #62792