# ParaView is using the wrong VTK clip?

**URL:** https://discourse.paraview.org/t/paraview-is-using-the-wrong-vtk-clip/17770
**Category:** ParaView Support
**Created:** [October 21, 2026, 3:23pm UTC](https://discourse.paraview.org/t/paraview-is-using-the-wrong-vtk-clip/17770 "2026-10-21T15:23:12Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Alexandre\_Minot](https://discourse.paraview.org/user_avatar/discourse.paraview.org/alexandre_minot/32/7132_2.png) [@Alexandre\_Minot](https://discourse.paraview.org/u/Alexandre_Minot)
#### Post date: [October 21, 2026, 3:23pm UTC](https://discourse.paraview.org/t/paraview-is-using-the-wrong-vtk-clip/17770/1 "2026-10-21T15:23:12Z")

</div>

Hello,

I’m getting the following warning when clipping a polygonal mesh:

```auto
Warning: In vtkTableBasedClipDataSet.cxx, line 1404
vtkTableBasedClipDataSet (0xc4378a0): Output points used by cells not supported by vtkTableBasedClipDataSet will appear twice. To avoid this, consider using vtkClipDataSet directly

```

Is ParaView using the wrong VTK clip?

I’m attaching the data. Loading it in ParaView and adding a clip filter triggers the warning. The warning is thrown by ParaView 6.1 and 6.2 but not by 6.0.

Many thanks,  
Alexandre

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [October 21, 2026, 3:27pm UTC](https://discourse.paraview.org/t/paraview-is-using-the-wrong-vtk-clip/17770/2 "2026-10-21T15:27:18Z")

</div>

Hi @Alexandre_Minot

Please share the whole dataset, only the .vtpc wont do.

---

<div class="post-metadata">

### Author: ![Alexandre\_Minot](https://discourse.paraview.org/user_avatar/discourse.paraview.org/alexandre_minot/32/7132_2.png) [@Alexandre\_Minot](https://discourse.paraview.org/u/Alexandre_Minot)
#### Post date: [October 21, 2026, 3:40pm UTC](https://discourse.paraview.org/t/paraview-is-using-the-wrong-vtk-clip/17770/3 "2026-10-21T15:40:53Z")

</div>

[cylinder\_data.vtkhdf](https://discourse.paraview.org/uploads/short-url/1WxtB8wBr8b8NecaQ7UpCfK28jT.vtkhdf) (1.3 MB)

Here we are, appologies.

---

<div class="post-metadata">

### Author: ![cory.quammen](https://discourse.paraview.org/user_avatar/discourse.paraview.org/cory.quammen/32/11193_2.png) [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [October 21, 2026, 5:34pm UTC](https://discourse.paraview.org/t/paraview-is-using-the-wrong-vtk-clip/17770/4 "2026-10-21T17:34:42Z")

</div>

ParaView is using the right clip which is performant - but the filter it is using can’t handle all cell types including polygons. For those cells, it defers clipping to the more general but slower vtkClipDataSet.

@spyridon97 you added this warning in [https://gitlab.kitware.com/vtk/vtk/-/merge\_requests/12532](https://gitlab.kitware.com/vtk/vtk/-/merge_requests/12532). For anyone processing polygonal datasets, which is becoming more common, this warning will appear every time. I think we should change it to a vtkDebugWarning as it is an informative message rather than indicating something is potentially going wrong.

---

<div class="post-metadata">

### Author: ![cory.quammen](https://discourse.paraview.org/user_avatar/discourse.paraview.org/cory.quammen/32/11193_2.png) [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [October 21, 2026, 5:49pm UTC](https://discourse.paraview.org/t/paraview-is-using-the-wrong-vtk-clip/17770/5 "2026-10-21T17:49:32Z")

</div>

@spyridon97 and I discussed this and we plan to change this warning to a vtkLog message at TRACE level so that it doesn’t appear in standard ParaView operation.