ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2019-03-05T10:45:48-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/6658Surface with edges bleeds through solids2019-03-05T10:45:48-05:00Kitware RobotSurface with edges bleeds through solids**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6658). Further discussion may take place here.**
---
XP, trunk.
Start ParaView.
Open can.
Surface with Edges
Hit the Z- Vi...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6658). Further discussion may take place here.**
---
XP, trunk.
Start ParaView.
Open can.
Surface with Edges
Hit the Z- View direction icon. (you are now looking at the bottom of the plate.)
Animate.
Notice that the can will bleed the edge lines through the bottom plate. This is not just a z-buffer precision problem - this should not happen. Happens when hardware rendered locally or remote render composited.
Probably not a drop dead error, but makes surface with edges useless for any presentations.
https://gitlab.kitware.com/paraview/paraview/-/issues/19723Surface with Edges creates extra edges2020-09-08T06:17:38-04:00Boonthanome NouanesengsySurface with Edges creates extra edgesWhen loading a parallel dataset and showing 'Surface With Edges', extra edges are present at cells which are at the border of data partitions. It looks like the edges are "going into" the mesh. These extra edges make it impossible for ou...When loading a parallel dataset and showing 'Surface With Edges', extra edges are present at cells which are at the border of data partitions. It looks like the edges are "going into" the mesh. These extra edges make it impossible for our users to really understand the structure of the mesh on the surface.
This is present in Paraview 5.6.2, but for some reason it's hard to create the right situation where it occurs. It surprisingly is most obvious in Paraview 5.8.0.
A screenshot of what the mesh should look like (I applied Merge Blocks to make this image):
![good](/uploads/74ced43c5aa7777063d2fd50c4024a1b/good.png)
A screenshot of what the data looks like when just loading it:
![bad](/uploads/da6050a2d288bd349ef9eb2dcd63a3ca/bad.png)
Notice the extra edges that seem to be going inside the mesh. The cells where it happens are at data partition boundaries.
If the mesh is even larger, the errors look even worse. There are many more extra edges. Below is a similar mesh, except that the number of cells were increased by 1000x. It looks like there are small fences along the data partitions.
![worst](/uploads/254d21b913c538e1a31217743b5470c5/worst.png)
Here is the dataset used for the first two images: [rti_small.tar.gz](/uploads/29a5e8f2acb6b79402c2a99c9ad96843/rti_small.tar.gz)
Camera angle file used for first two images: [viewpoint.pvcvbc](/uploads/0dd515cd6b9397c43dab4e1eeb84f0c9/viewpoint.pvcvbc)
I can't include the large mesh because it's about 12GB.
How to reproduce:
- use Paraview 5.8.0 (can use in serial)
- load the dataset
- rotate the mesh at an angle
- zoom into the mesh until you see the extra edges
- or you can download viewpoint.pvcvbc, load it with the 'Configure custom viewpoints' button, and click on the newly created Viewpoint
@patchett2002 @demarle5.8.1https://gitlab.kitware.com/paraview/paraview/-/issues/5677Surface With Edges representation has incorrect replace input behavior2019-03-05T10:47:22-05:00Kitware RobotSurface With Edges representation has incorrect replace input behavior**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5677). Further discussion may take place here.**
---
Some filters, such as contour, are supposed to replace their input if their...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5677). Further discussion may take place here.**
---
Some filters, such as contour, are supposed to replace their input if their source shows an opaque surface. This is behavior is specified by setting the replace_input of the Visibility hint tag to 2. That all works fine for surface representation, but not the new surface with edges representation. The surface with edges representation remains visible after the filter is first applied. Here is a simple replication:
1. Create a sphere source.
2. Create a clip filter and apply. Everything is working fine.
3. Delete the clip filter.
4. Change the representation of the sphere to Surface With Edges.
5. Create and apply another clip filter. This time it looks like nothing was done because the sphere was not properly hidden.https://gitlab.kitware.com/paraview/paraview/-/issues/15134Surface with edges should be sticky between filters2020-05-06T20:19:24-04:00Kitware RobotSurface with edges should be sticky between filters**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15134). Further discussion may take place here.**
---
Surface with edges should be sticky between filters.
Windows, 4.2.0, lo...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15134). Further discussion may take place here.**
---
Surface with edges should be sticky between filters.
Windows, 4.2.0, local server.
Open disk_out_ref.exo. Apply. Change representation to surface with edges.
Clip. Notice that surface with edges has changed to surface. This is a bug.
https://gitlab.kitware.com/paraview/paraview/-/issues/13793Surface with Edges showing spurious edges.2020-05-11T20:33:46-04:00Kitware RobotSurface with Edges showing spurious edges.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13793). Further discussion may take place here.**
---
Load the attached "test.hyb.case" file and render in "Surface With Edges" ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13793). Further discussion may take place here.**
---
Load the attached "test.hyb.case" file and render in "Surface With Edges" mode. You'll see random lines as shown in pv3_98.png. The issue is not present when rendering as Surface or Wireframe or with ParaView 3.14.
Utkarshhttps://gitlab.kitware.com/paraview/paraview/-/issues/13260surface-pick-on-multi-block2018-08-23T15:17:02-04:00Kitware Robotsurface-pick-on-multi-block**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13260). Further discussion may take place here.**
---
The surface picking is not working on multi-block.
Try to change the ce...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13260). Further discussion may take place here.**
---
The surface picking is not working on multi-block.
Try to change the center of rotation on can2.ex to highlight the bug.https://gitlab.kitware.com/paraview/paraview/-/issues/17088SurfaceLIC doesn't work when FXAA is enabled2017-04-24T15:00:31-04:00Utkarsh AyachitSurfaceLIC doesn't work when FXAA is enabled+ Start ParaView, load `SurfaceLIC` plugin
+ Open disk_out_ref.ex2, all variables, apply, render as representation = "Surface LIC". All's good.
+ Now enable `Use FXAA` from the Settings |Render View pane, and interact with the view. Th...+ Start ParaView, load `SurfaceLIC` plugin
+ Open disk_out_ref.ex2, all variables, apply, render as representation = "Surface LIC". All's good.
+ Now enable `Use FXAA` from the Settings |Render View pane, and interact with the view. The rendering will be messed up.5.3Allison Vacantialliepiper16@gmail.comAllison Vacantialliepiper16@gmail.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20002SurfaceLIC segfault with line or polyline cells2021-04-12T11:14:36-04:00Mathieu Westphal (Kitware)SurfaceLIC segfault with line or polyline cells
* run paraview
* Tools -> ManagePlugins -> SurfaceLIC
* Line Source/PolyLine source, Apply
* Random Vectors, Apply
* Select SurfaceLIC
* Segfault
```
( 23.781s) [paraview ] vtkShaderProgram.cxx:452 ERR| vtkShaderPro...
* run paraview
* Tools -> ManagePlugins -> SurfaceLIC
* Line Source/PolyLine source, Apply
* Random Vectors, Apply
* Select SurfaceLIC
* Segfault
```
( 23.781s) [paraview ] vtkShaderProgram.cxx:452 ERR| vtkShaderProgram (0x555560f1a940): 1: #version 150
2: #ifdef GL_ES
3: #ifdef GL_FRAGMENT_PRECISION_HIGH
4: precision highp float;
5: precision highp sampler2D;
6: precision highp sampler3D;
7: #else
8: precision mediump float;
9: precision mediump sampler2D;
10: precision mediump sampler3D;
11: #endif
12: #define texelFetchBuffer texelFetch
13: #define texture1D texture
14: #define texture2D texture
15: #define texture3D texture
16: #else // GL_ES
17: #define highp
18: #define mediump
19: #define lowp
20: #if __VERSION__ == 150
21: #define texelFetchBuffer texelFetch
22: #define texture1D texture
23: #define texture2D texture
24: #define texture3D texture
25: #endif
26: #endif // GL_ES
27: #define varying in
28:
29:
30: /*=========================================================================
31:
32: Program: Visualization Toolkit
33: Module: vtkPolyDataFS.glsl
34:
35: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen
36: All rights reserved.
37: See Copyright.txt or http://www.kitware.com/Copyright.htm for details.
38:
39: This software is distributed WITHOUT ANY WARRANTY; without even
40: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
41: PURPOSE. See the above copyright notice for more information.
42:
43: =========================================================================*/
44: // Template for the polydata mappers fragment shader
45:
46: uniform int PrimitiveIDOffset;
47:
48:
49:
50: // VC position of this fragment
51: //VTK::PositionVC::Dec
52:
53: // Camera prop
54: uniform int cameraParallel;
55:
56:
57: // optional color passed in from the vertex shader, vertexColor
58: uniform bool OverridesColor;
59: uniform float ambientIntensity; // the material ambient
60: uniform float diffuseIntensity; // the material diffuse
61: uniform float opacityUniform; // the fragment opacity
62: uniform vec3 ambientColorUniform; // ambient color
63: uniform vec3 diffuseColorUniform; // diffuse color
64:
65:
66: // optional surface normal declaration
67: //VTK::Normal::Dec
68:
69: // extra lighting parameters
70: uniform vec3 lightColor0;
71: uniform vec3 lightDirectionVC0; // normalized
72: uniform vec3 lightColor1;
73: uniform vec3 lightDirectionVC1; // normalized
74: uniform vec3 lightColor2;
75: uniform vec3 lightDirectionVC2; // normalized
76: uniform vec3 lightColor3;
77: uniform vec3 lightDirectionVC3; // normalized
78: uniform vec3 lightColor4;
79: uniform vec3 lightDirectionVC4; // normalized
80: 81:
82: // Texture maps
83: //VTK::TMap::Dec
84:
85: // Texture coordinates
86: uniform int uMaskOnSurface;
87: uniform mat3 normalMatrix;
88: in vec3 tcoordVCVSOutput;
89:
90: // picking support
91: //VTK::Picking::Dec
92:
93: // Depth Peeling Support
94: //VTK::DepthPeeling::Dec
95:
96: // clipping plane vars
97: //VTK::Clip::Dec
98:
99: // the output of this shader
100: out vec4 fragOutput0;
101: out vec4 fragOutput1;
102: out vec4 fragOutput2;
103:
104:
105: // Apple Bug
106: //VTK::PrimID::Dec
107:
108: // handle coincident offsets
109: uniform float cCValue;
110: uniform float cSValue;
111: uniform float cDValue;
112:
113: // Value raster
114: //VTK::ValuePass::Dec
115:
116: // surface with edges
117: //VTK::Edges::Dec
118:
119: void main()
120: {
121: // VC position of this fragment. This should not branch/return/discard.
122: //VTK::PositionVC::Impl
123:
124: // Place any calls that require uniform flow (e.g. dFdx) here.
125: //VTK::UniformFlow::Impl
126:
127: // Set gl_FragDepth here (gl_FragCoord.z by default)
128: float Zdc = gl_FragCoord.z*2.0 - 1.0;
129: float Z2 = -1.0*cDValue/(Zdc + cCValue) + cSValue;
130: float Zdc2 = -1.0*cCValue - cDValue/Z2;
131: gl_FragDepth = Zdc2*0.5 + 0.5;
132:
133:
134: // Early depth peeling abort:
135: //VTK::DepthPeeling::PreColor
136:
137: // Apple Bug
138: //VTK::PrimID::Impl
139:
140: //VTK::Clip::Impl
141:
142: //VTK::ValuePass::Impl
143:
144: vec3 ambientColor = ambientIntensity * ambientColorUniform;
145: vec3 diffuseColor = diffuseIntensity * diffuseColorUniform;
146: float opacity = opacityUniform;
147:
148: if (OverridesColor) {
149: ambientColor = ambientColorUniform * ambientIntensity;
150: diffuseColor = diffuseColorUniform * diffuseIntensity; }
151:
152:
153: //VTK::Edges::Impl
154:
155: // Generate the normal if we are not passed in one
156: //VTK::Normal::Impl
157:
158: fragOutput0 = vec4(ambientColor + diffuseColor, opacity);
159: //VTK::Light::Impl
160:
161:
162: vec3 tcoordLIC = normalMatrix * tcoordVCVSOutput;
163: vec3 normN = normalize(normalVCVSOutput);
164: float k = dot(tcoordLIC, normN);
165: tcoordLIC = (tcoordLIC - k*normN);
166: fragOutput1 = vec4(tcoordLIC.x, tcoordLIC.y, 0.0 , gl_FragCoord.z);
167: if (uMaskOnSurface == 0)
168: {
169: fragOutput2 = vec4(tcoordVCVSOutput, gl_FragCoord.z);
170: }
171: else
172: {
173: fragOutput2 = vec4(tcoordLIC.x, tcoordLIC.y, 0.0 , gl_FragCoord.z);
174: }
175:
176:
177: if (fragOutput0.a <= 0.0)
178: {
179: discard;
180: }
181:
182: //VTK::DepthPeeling::Impl
183:
184: //VTK::Picking::Impl
185:
186: // handle coincident offsets
187: //VTK::Coincident::Impl
188: }
( 23.796s) [paraview ] vtkShaderProgram.cxx:453 ERR| vtkShaderProgram (0x555560f1a940): 0(163) : error C1503: undefined variable "normalVCVSOutput"
Thread 1 "paraview" received signal SIGSEGV, Segmentation fault.
0x00007ffff45f0f5d in vtkOpenGLPolyDataMapper::UpdateShaders (this=0x555560f0ee90, cellBO=..., ren=0x55555d22e7e0, actor=0x55555e14c6c0) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/OpenGL2/vtkOpenGLPolyDataMapper.cxx:2374
2374 if (newShader != cellBO.Program || cellBO.Program->GetMTime() > cellBO.AttributeUpdateTime)
(gdb) bt
#0 0x00007ffff45f0f5d in vtkOpenGLPolyDataMapper::UpdateShaders (this=0x555560f0ee90, cellBO=..., ren=0x55555d22e7e0, actor=0x55555e14c6c0) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/OpenGL2/vtkOpenGLPolyDataMapper.cxx:2374
#1 0x00007ffff450da82 in vtkCompositeMapperHelper2::UpdateShaders (this=0x555560f0ee90, cellBO=..., ren=0x55555d22e7e0, act=0x55555e14c6c0) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/OpenGL2/vtkCompositePolyDataMapper2.cxx:172
#2 0x00007ffff450e3e2 in vtkCompositeMapperHelper2::DrawIBO (this=0x555560f0ee90, ren=0x55555d22e7e0, actor=0x55555e14c6c0, primType=1, CellBO=..., mode=1, pointSize=0) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/OpenGL2/vtkCompositePolyDataMapper2.cxx:319
#3 0x00007ffff450e8ee in vtkCompositeMapperHelper2::RenderPieceDraw (this=0x555560f0ee90, ren=0x55555d22e7e0, actor=0x55555e14c6c0) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/OpenGL2/vtkCompositePolyDataMapper2.cxx:410
#4 0x00007ffff450e31d in vtkCompositeMapperHelper2::RenderPiece (this=0x555560f0ee90, ren=0x55555d22e7e0, actor=0x55555e14c6c0) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/OpenGL2/vtkCompositePolyDataMapper2.cxx:303
#5 0x00007ffff4514f72 in vtkCompositePolyDataMapper2::Render (this=0x55555e141d60, ren=0x55555d22e7e0, actor=0x55555e14c6c0) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/OpenGL2/vtkCompositePolyDataMapper2.cxx:1816
#6 0x00007fffebbab2ab in vtkCompositeSurfaceLICMapper::Render (this=0x55555e141d60, ren=0x55555d22e7e0, actor=0x55555e14c6c0) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/LICOpenGL2/vtkCompositeSurfaceLICMapper.cxx:284
#7 0x00007ffff455f647 in vtkOpenGLActor::Render (this=0x55555e14c6c0, ren=0x55555d22e7e0, mapper=0x55555e141d60) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/OpenGL2/vtkOpenGLActor.cxx:104
#8 0x00007fffef441d74 in vtkPVLODActor::Render (this=0x55555de8b570, ren=0x55555d22e7e0) at /home/glow/work/paraview/paraviewThird/paraview/Remoting/Views/vtkPVLODActor.cxx:141
#9 0x00007fffef441f6d in vtkPVLODActor::RenderOpaqueGeometry (this=0x55555de8b570, vp=0x55555d22e7e0) at /home/glow/work/paraview/paraviewThird/paraview/Remoting/Views/vtkPVLODActor.cxx:172
#10 0x00007ffff40a0c01 in vtkRenderer::UpdateOpaquePolygonalGeometry (this=0x55555d22e7e0) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/Core/vtkRenderer.cxx:736
#11 0x00007ffff409fa0d in vtkRenderer::DeviceRenderOpaqueGeometry (this=0x55555d22e7e0) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/Core/vtkRenderer.cxx:436
#12 0x00007ffff4633788 in vtkOpenGLRenderer::DeviceRenderOpaqueGeometry (this=0x55555d22e7e0, fbo=0x0) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/OpenGL2/vtkOpenGLRenderer.cxx:494
#13 0x00007ffff4632c10 in vtkOpenGLRenderer::UpdateGeometry (this=0x55555d22e7e0, fbo=0x0) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/OpenGL2/vtkOpenGLRenderer.cxx:390
#14 0x00007ffff407f48e in vtkRenderPass::UpdateGeometry (this=0x55555d2ddf30, renderer=0x55555d22e7e0, fbo=0x0) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/Core/vtkRenderPass.cxx:93
#15 0x00007fffef409beb in vtkPVDefaultPass::Render (this=0x55555d2ddf30, render_state=0x7fffffffca80) at /home/glow/work/paraview/paraviewThird/paraview/Remoting/Views/vtkPVDefaultPass.cxx:43
#16 0x00007ffff450a815 in vtkCameraPass::Render (this=0x55555d2dd2b0, s=0x7fffffffca80) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/OpenGL2/vtkCameraPass.cxx:144
#17 0x00007ffff4631fa3 in vtkOpenGLRenderer::DeviceRender (this=0x55555d22e7e0) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/OpenGL2/vtkOpenGLRenderer.cxx:281
#18 0x00007ffff409f53e in vtkRenderer::Render (this=0x55555d22e7e0) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/Core/vtkRenderer.cxx:377
#19 0x00007ffff40b4866 in vtkRendererCollection::Render (this=0x555558207c80) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/Core/vtkRendererCollection.cxx:51
#20 0x00007ffff4082d44 in vtkRenderWindow::DoStereoRender (this=0x55555d59cd10) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/Core/vtkRenderWindow.cxx:337
#21 0x00007ffff4082b1d in vtkRenderWindow::Render (this=0x55555d59cd10) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/Core/vtkRenderWindow.cxx:297
#22 0x00007ffff462fef0 in vtkOpenGLRenderWindow::Render (this=0x55555d59cd10) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx:2067
#23 0x00007ffff4550d36 in vtkGenericOpenGLRenderWindow::Render (this=0x55555d59cd10) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/OpenGL2/vtkGenericOpenGLRenderWindow.cxx:218
#24 0x00007fffef475934 in vtkPVRenderView::Render (this=0x55555814f230, interactive=false, skip_rendering=false) at /home/glow/work/paraview/paraviewThird/paraview/Remoting/Views/vtkPVRenderView.cxx:1601
#25 0x00007fffef474994 in vtkPVRenderView::StillRender (this=0x55555814f230) at /home/glow/work/paraview/paraviewThird/paraview/Remoting/Views/vtkPVRenderView.cxx:1384
#26 0x00007fffefd4a325 in vtkPVRenderViewCommand (arlu=0x55555586ab50, ob=0x55555814f230, method=0x55555ebaf589 "StillRender", msg=..., resultStream=...) at CMakeFiles/vtkRemotingViewsCS/vtkPVRenderViewClientServer.cxx:242
#27 0x00007ffff4e39c83 in vtkClientServerInterpreter::CallCommandFunction (this=0x55555586ab50, cname=0x7fffef5a066e "vtkPVRenderView", ptr=0x55555814f230, method=0x55555ebaf589 "StillRender", msg=..., result=...)
at /home/glow/work/paraview/paraviewThird/paraview/Remoting/ClientServerStream/vtkClientServerInterpreter.cxx:809
#28 0x00007ffff4e38244 in vtkClientServerInterpreter::ProcessCommandInvoke (this=0x55555586ab50, css=..., midx=2) at /home/glow/work/paraview/paraviewThird/paraview/Remoting/ClientServerStream/vtkClientServerInterpreter.cxx:424
#29 0x00007ffff4e37754 in vtkClientServerInterpreter::ProcessOneMessage (this=0x55555586ab50, css=..., message=2) at /home/glow/work/paraview/paraviewThird/paraview/Remoting/ClientServerStream/vtkClientServerInterpreter.cxx:265
#30 0x00007ffff4e375db in vtkClientServerInterpreter::ProcessStream (this=0x55555586ab50, css=...) at /home/glow/work/paraview/paraviewThird/paraview/Remoting/ClientServerStream/vtkClientServerInterpreter.cxx:235
#31 0x00007ffff5881eb4 in vtkPVSessionCore::ExecuteStreamInternal (this=0x55555586bcf0, stream=..., ignore_errors=false) at /home/glow/work/paraview/paraviewThird/paraview/Remoting/ServerManager/vtkPVSessionCore.cxx:637
#32 0x00007ffff5881c7f in vtkPVSessionCore::ExecuteStream (this=0x55555586bcf0, location=16, stream=..., ignore_errors=false) at /home/glow/work/paraview/paraviewThird/paraview/Remoting/ServerManager/vtkPVSessionCore.cxx:607
#33 0x00007ffff587e214 in vtkPVSessionBase::ExecuteStream (this=0x555555cece70, location=16, stream=..., ignore_errors=false) at /home/glow/work/paraview/paraviewThird/paraview/Remoting/ServerManager/vtkPVSessionBase.cxx:165
#34 0x00007ffff59b41e4 in vtkSMProxy::ExecuteStream (this=0x55555c6044b0, stream=..., ignore_errors=false, location=16) at /home/glow/work/paraview/paraviewThird/paraview/Remoting/ServerManager/vtkSMProxy.cxx:2397
#35 0x00007fffef54ac0f in vtkSMViewProxy::StillRender (this=0x55555c6044b0) at /home/glow/work/paraview/paraviewThird/paraview/Remoting/Views/vtkSMViewProxy.cxx:428
#36 0x00007ffff6b52072 in pqView::forceRender (this=0x55555d2e9700) at /home/glow/work/paraview/paraviewThird/paraview/Qt/Core/pqView.cxx:245
#37 0x00007ffff6b51fbe in pqView::tryRender (this=0x55555d2e9700) at /home/glow/work/paraview/paraviewThird/paraview/Qt/Core/pqView.cxx:223
#38 0x00007ffff6a84578 in pqView::qt_static_metacall (_o=0x55555d2e9700, _c=QMetaObject::InvokeMetaMethod, _id=24, _a=0x7fffffffe310) at Qt/Core/pqCore_autogen/EWIEGA46WW/moc_pqView.cpp:203
#39 0x00007ffff5fad940 in ?? () from /usr/lib/libQt5Core.so.5
#40 0x00007ffff5fb197b in QTimer::timeout(QTimer::QPrivateSignal) () from /usr/lib/libQt5Core.so.5
#41 0x00007ffff5c7b1f1 in pqTimer::timerEvent (this=0x5555581cbc68, evt=0x7fffffffe4a0) at /home/glow/work/paraview/paraviewThird/paraview/ThirdParty/QtTesting/vtkqttesting/pqTimer.cxx:53
#42 0x00007ffff5fa2fef in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5
#43 0x00007ffff72ae6f2 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#44 0x00007ffff5f7669a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5
#45 0x00007ffff5fce595 in QTimerInfoList::activateTimers() () from /usr/lib/libQt5Core.so.5
#46 0x00007ffff5fcee42 in ?? () from /usr/lib/libQt5Core.so.5
#47 0x00007fffed81943c in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#48 0x00007fffed866fa9 in ?? () from /usr/lib/libglib-2.0.so.0
#49 0x00007fffed818221 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#50 0x00007ffff5fcf211 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#51 0x00007ffff5f7501c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#52 0x00007ffff5f7d4a4 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5
#53 0x0000555555562306 in main (argc=1, argv=0x5555556d4b50) at Clients/ParaView/paraview_main.cxx:138
```https://gitlab.kitware.com/paraview/paraview/-/issues/21165SurfaceLIC should only enable vector fields for the choice of "Vectors"2022-05-19T16:15:16-04:00Jean M. FavreSurfaceLIC should only enable vector fields for the choice of "Vectors"tested with PV 5.10
Steps to reproduce:
Create a FastUniformGrid with both DistanceSquaredScalars and Swirl Vectors enabled
Make a Slice, and use Surface LIC representation
The GUI enables *all* fields (scalar-fields and vector-field...tested with PV 5.10
Steps to reproduce:
Create a FastUniformGrid with both DistanceSquaredScalars and Swirl Vectors enabled
Make a Slice, and use Surface LIC representation
The GUI enables *all* fields (scalar-fields and vector-fields) as the choice for the Integrator:VectorsCory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19310SurfaceLIC: inconsistent results on low-resolution image data2019-09-17T03:01:39-04:00Lutz HofmannSurfaceLIC: inconsistent results on low-resolution image dataSurfaceLIC on very low resolution image data (e.g., 3x3x1) yields different results than after applying Resample To Image to a higher resolution (e.g., 99x99x1).
Stream Tracer, on the other hand, yields the same results on both resolutio...SurfaceLIC on very low resolution image data (e.g., 3x3x1) yields different results than after applying Resample To Image to a higher resolution (e.g., 99x99x1).
Stream Tracer, on the other hand, yields the same results on both resolutions, which is the behaviour, that I would expect from SurfaceLIC as well.
An example is shown below, with streamlines in black computed by Stream Tracer (they coincide on both resolutions) and critical points for context.
This issue is present in all ParaView versions, that I have tested (5.3.0, 5.6.0, 5.7.0-RC2).
# LIC on 3x3 image
![lowres](/uploads/04d94229d57f68191e80e4b99e034e19/lowres.png)
# LIC after resampling to 99x99
![highres](/uploads/9f8754cfa2a3526accc8490ce6b0af73/highres.png)
# Statefile and data
[surfacelic_bug.tar.gz](/uploads/72dce73038ef0d9ad00fdebb5792f6aa/surfacelic_bug.tar.gz)https://gitlab.kitware.com/paraview/paraview/-/issues/9926Surfaces and overlapping lines are displaced.2019-03-05T10:40:57-05:00Kitware RobotSurfaces and overlapping lines are displaced.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=9926). Further discussion may take place here.**
---
Here is a bug from the mail group - Benjamin Schindler [bschindler@inf.ethz...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=9926). Further discussion may take place here.**
---
Here is a bug from the mail group - Benjamin Schindler [bschindler@inf.ethz.ch]:
This is a known issue. This happens due to the coincident topology
resolution techniques employed to rendering surfaces with overlapping
lines correctly. We are working on a fix for this issue.
Utkarsh
>
> I have a very odd problem with paraview 3.6.1 (debug build directly from sources):
>
> When displaying different objects, they are not properly laid into space, probably due to projection problems. One way to very easily see this is to display a line and then use the spreadsheet view to select a vertex of that line. The purple dot which highlights the point is then not on the vertex itself, but at some offset which varies depending on the viewing direction. I took a screenshot (and taking the screenshot itself changed the position of the highlight it seemed) to illustrate the problem.
> This is extremely annoying as also datasets/lines are not properly laid into space so there is no way to tell how the two objects relate to each other. The same problem happens when selecting objects (see second screenshot)
> Is this a known issue/is there already a fix for this?
https://gitlab.kitware.com/paraview/paraview/-/issues/17089SurfacLIC messes up color legend labels2017-11-21T16:31:56-05:00Utkarsh AyachitSurfacLIC messes up color legend labelsThis was tested on Linux with
OpenGL version string: 4.5.0 NVIDIA 367.57
OpenGL shading language version string: 4.50 NVIDIA
* Start ParaVIew (builtin), load `Surface LIC` plugin
* Open `disk_out_ref.ex1` dataset. Apply...This was tested on Linux with
OpenGL version string: 4.5.0 NVIDIA 367.57
OpenGL shading language version string: 4.50 NVIDIA
* Start ParaVIew (builtin), load `Surface LIC` plugin
* Open `disk_out_ref.ex1` dataset. Apply. Note the labels on the scalar bar. ![image](/uploads/96f4aca2d182485d6ff20edf07b8faac/image.png)
* Change representation to "Surface LIC", now note the labels on the scalar bar. They are not rendering correctly.
![image](/uploads/408fed5520b1dc6565f0743c1654ec2f/image.png)5.3Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19807Switch from Gauss to Mean curvature no working2020-03-31T03:16:00-04:00Florian MaurinSwitch from Gauss to Mean curvature no workingTo reproduce:
* Source -> Sphere -> Apply
* Filter-> Curvature -> Apply (the default curvature displayed is Gaussian, and is working fine )
* Switch the curvature type to Mean, nothing is displayed, and the legend caption remain Gauss...To reproduce:
* Source -> Sphere -> Apply
* Filter-> Curvature -> Apply (the default curvature displayed is Gaussian, and is working fine )
* Switch the curvature type to Mean, nothing is displayed, and the legend caption remain Gauss_Curvature.
In filters_filtersgeneral.xml we have
```
<IntVectorProperty command="SetCurvatureType"
default_values="0"
name="CurvatureType"
number_of_elements="1">
<EnumerationDomain name="enum">
<Entry text="Gaussian"
value="0" />
<Entry text="Mean"
value="1" />
```
If we switch `default_values="0"` to `default_values="1"`, the opposite happen: the Mean curvature is working, but not the Gaussian.
So this is not a problem in the implementation of the Mean curvature.
In vtkCurvatures::GetGaussCurvature(vtkPolyData* output) we have something equivalent to:
```
gaussCurvature->SetName("Gauss_Curvature");
output->GetPointData()->AddArray(gaussCurvature);
output->GetPointData()->SetActiveScalars(gaussCurvature->GetName());
```
and in vtkCurvatures::GetMeanCurvature(vtkPolyData* output) we have something equivalent to:
```
meanCurvature->SetName("Mean_Curvature");
output->GetPointData()->AddArray(meanCurvature);
output->GetPointData()->SetActiveScalars(meanCurvature->GetName());
```
If both names `"Mean_Curvature"` and `"Gauss_Curvature"` are renamed with the same name as for instance `"Curvature"`, things are working fine.
So the problem would be that `SetActiveScalars` is not working correctly, or that the filter is not loading the active scalar. But I don't know where this happen.
Any thought?https://gitlab.kitware.com/paraview/paraview/-/issues/3704Switch to using the new time support2019-03-05T10:52:30-05:00Kitware RobotSwitch to using the new time support**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=3704). Further discussion may take place here.**
---
As the new time support is coming online, we need to switch to using it in ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=3704). Further discussion may take place here.**
---
As the new time support is coming online, we need to switch to using it in the properties and domains.https://gitlab.kitware.com/paraview/paraview/-/issues/5582Switching Attribute mode from Point Data to Cell Data (plot over line, plot p...2019-03-05T10:47:35-05:00Kitware RobotSwitching Attribute mode from Point Data to Cell Data (plot over line, plot point over time) causes crash**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5582). Further discussion may take place here.**
---
This exhibits on Windows, with a very recent Aug 27 4am check-out and build...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5582). Further discussion may take place here.**
---
This exhibits on Windows, with a very recent Aug 27 4am check-out and build using Visual Studio 2005:
-- Load a sample exodus file, e.g. disk_out_ref.exo
-- Turn on temp(erature)
-- Color by temp
-- Do a Plot Over Line filter
-- Make sure the line plot view window is selected, then change the Attribute Mode from Point Data to Cell Data.
-- ParaView3 crashes
https://gitlab.kitware.com/paraview/paraview/-/issues/19779Switching from 2D to 3D view causes graphic to disappear2020-03-19T10:43:35-04:00Nick ThompsonSwitching from 2D to 3D view causes graphic to disappear![ParaviewBug](/uploads/f052317126f7877a3c76ecf7da4885a4/ParaviewBug.mov)
Paraview info:
![Screen_Shot_2020-03-19_at_6.34.24_AM](/uploads/c4e57d0a6ddb8cfe70c47b4b79f9fe49/Screen_Shot_2020-03-19_at_6.34.24_AM.png)
Data to reproduce:
[...![ParaviewBug](/uploads/f052317126f7877a3c76ecf7da4885a4/ParaviewBug.mov)
Paraview info:
![Screen_Shot_2020-03-19_at_6.34.24_AM](/uploads/c4e57d0a6ddb8cfe70c47b4b79f9fe49/Screen_Shot_2020-03-19_at_6.34.24_AM.png)
Data to reproduce:
[euler_spiral.vtk](/uploads/5572c503dc25928976999a1b194f069b/euler_spiral.vtk)https://gitlab.kitware.com/paraview/paraview/-/issues/20348Switching on custom labels in Axes Grid/Data Axes Grid and enabling raytracin...2020-12-08T10:53:15-05:00Vigeesh GangadharanSwitching on custom labels in Axes Grid/Data Axes Grid and enabling raytracing results in a crash [v5.9.0-RC1]Setting Axes Grid/Data Axes Grid and enabling RayTracing works fine in both v5.8.0 and v5.9.0-RC1.<br>
As expected, the axes grid is not rendered in the final output (related: #19871), but it does not crash.
But, setting custom labels i...Setting Axes Grid/Data Axes Grid and enabling RayTracing works fine in both v5.8.0 and v5.9.0-RC1.<br>
As expected, the axes grid is not rendered in the final output (related: #19871), but it does not crash.
But, setting custom labels in Axes Grid/Data Axes Grid and switching on RayTracing results in a crash in v5.9.0-RC1.<br>
The same works without any problem in v5.8.0.
This issue occurs in Paraview GUI and can also be reproduced using a simple script.
**Code for reproduction**
```python
from paraview.simple import *
# Create a Cone
cone = Cone()
# Turn on the visibility of the object
Show(cone)
# Get the renderview
renderView = GetRenderView()
# Switch On/Off Raytracing
# Set this to 1 to reproduce the issue
renderView.EnableRayTracing = 1
# Switch on the axes grid
renderView.AxesGrid.Visibility = 1
# Switch custom label for x-axis
# Set this to 1 to reproduce the issue
renderView.AxesGrid.XAxisUseCustomLabels = 1
# Provide labels for the x-axis
renderView.AxesGrid.XAxisLabels = [0.1]
# Render the scene
Render()
# Save results
SaveScreenshot('test.png')
```
**Expected Output** (using v5.8.0)
RayTracing Off | RayTracing On
------ | ------
![5.8](/uploads/824e5504681e7209e30d71d0b4c35827/test_5.8.png) | ![test_5.8_enabled](/uploads/83897a3a008809455bf923901e7ba081/test_5.8_enabled.png)
**Actual Output** (using v5.9.0-RC1)
RayTracing Off | RayTracing On
------ | ------
![5.9](/uploads/40a474889c3fa864e2d1d946dc958aab/test_5.9.png) | Loguru caught a signal: SIGSEGV <br> Stack trace: <br> . <br> . <br> . <br> ( 0.750s) [paraview ] :0 FATL\| Signal: SIGSEGVhttps://gitlab.kitware.com/paraview/paraview/-/issues/6818Switching to "Solid Color" does not remove scalar bar2019-03-05T10:45:28-05:00Kitware RobotSwitching to "Solid Color" does not remove scalar bar**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6818). Further discussion may take place here.**
---
When nothing on the screen is colored by a variable, shouldn't the scalar b...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6818). Further discussion may take place here.**
---
When nothing on the screen is colored by a variable, shouldn't the scalar bar be hidden?https://gitlab.kitware.com/paraview/paraview/-/issues/4038Switching to selection mode causes crash.2019-03-05T10:51:43-05:00Kitware RobotSwitching to selection mode causes crash.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=4038). Further discussion may take place here.**
---
If there is not an active render module and you switch to selection mode th...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=4038). Further discussion may take place here.**
---
If there is not an active render module and you switch to selection mode the application crashes.
To reproduce:
Connect to built in server.
Split view vertically.
Delete selected view.
Switch to selection mode.
Other applications may not have an active render module all of the time. The selection manager should be able to handle NULL as the active render module.https://gitlab.kitware.com/paraview/paraview/-/issues/12146Switching to Surface LIC representation pops up bogus error message2019-03-05T10:37:57-05:00Kitware RobotSwitching to Surface LIC representation pops up bogus error message**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12146). Further discussion may take place here.**
---
The collaboration branch merge introduced the following regression:
Par...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12146). Further discussion may take place here.**
---
The collaboration branch merge introduced the following regression:
ParaView nightly build (pv commit 88dff25b1550de5cc78f124c956c80d977960326), local server, Linux 64-bit.
* Sources / Wavelet. Apply
* Filters / Random Vectors. Apply
* Display / Representation / Surface LIC
=> The following error message is raised:
ERROR: In /ParaView3.git/ParaViewCore/ClientServerCore/vtkGeometryRepresentation.cxx, line 436
vtkSurfaceLICRepresentation (0x4048cc0): Invalid type: 2
The Surface LIC seems to work nicely, nonetheless.
Does not happen with PV 3.10.1 and pre-collaboration-branch-merge versions.