# glitchy render in non conformal geometry

**URL:** https://discourse.paraview.org/t/glitchy-render-in-non-conformal-geometry/17704
**Category:** ParaView Support
**Created:** [August 28, 2026, 11:12am UTC](https://discourse.paraview.org/t/glitchy-render-in-non-conformal-geometry/17704 "2026-08-28T11:12:22Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![otaolafr](https://discourse.paraview.org/user_avatar/discourse.paraview.org/otaolafr/32/3595_2.png) [@otaolafr](https://discourse.paraview.org/u/otaolafr)
#### Post date: [August 28, 2026, 11:12am UTC](https://discourse.paraview.org/t/glitchy-render-in-non-conformal-geometry/17704/1 "2026-08-28T11:12:22Z")

</div>

Hello,  
i was doing a random test for other purposes and i found that the resulting render was quite glichy for this case of two boxes touching on the corner and merged together.

 ![image](https://discourse.paraview.org/uploads/default/original/3X/f/1/f110b31b6aed7e061107ec4cf9a2ad2106f46f48.png)  
here one can find the example [eg.pvsm](https://discourse.paraview.org/uploads/short-url/oTrpKPv7SHaTCcqK8OmlWjSh21h.pvsm) (575.5 KB)  
was not sure if it was worth repoting it.  
vr. 6.0.1

---

<div class="post-metadata">

### Author: ![Lucas\_Givord](https://discourse.paraview.org/user_avatar/discourse.paraview.org/lucas_givord/32/6851_2.png) [@Lucas\_Givord](https://discourse.paraview.org/u/Lucas_Givord)
#### Post date: [August 28, 2026, 11:31am UTC](https://discourse.paraview.org/t/glitchy-render-in-non-conformal-geometry/17704/2 "2026-08-28T11:31:55Z")

</div>

Hello,

yeah, definitively a normal issue.

I bet that it’s because the Box source has duplicate points, when we merge blocks, duplicate points are cleaned so the Normals array need to be computed once again.

Do you reproduce the error with a similar setup but with another source/dataset ?

---

<div class="post-metadata">

### Author: ![otaolafr](https://discourse.paraview.org/user_avatar/discourse.paraview.org/otaolafr/32/3595_2.png) [@otaolafr](https://discourse.paraview.org/u/otaolafr)
#### Post date: [August 28, 2026, 11:34am UTC](https://discourse.paraview.org/t/glitchy-render-in-non-conformal-geometry/17704/3 "2026-08-28T11:34:52Z")

</div>

I reported just because i thought it might be useful for others (know there is an issue). i came across it just playing around to test some things with connectivity filter but it is not something that i do in general, so no idea if it is reproductable with other source/dataset.

---

<div class="post-metadata">

### Author: ![Lucas\_Givord](https://discourse.paraview.org/user_avatar/discourse.paraview.org/lucas_givord/32/6851_2.png) [@Lucas\_Givord](https://discourse.paraview.org/u/Lucas_Givord)
#### Post date: [August 28, 2026, 11:53am UTC](https://discourse.paraview.org/t/glitchy-render-in-non-conformal-geometry/17704/4 "2026-08-28T11:53:08Z")

</div>

ok, I tried few things and it seems that I have right, the issue is caused by the points duplication in the Box source.

As I don’t see why we duplicate it and it forces potential user of this source to recompute a normal array later, I created an issue : [https://gitlab.kitware.com/paraview/paraview/-/work\_items/23376](https://gitlab.kitware.com/paraview/paraview/-/work_items/23376)

thanks for the report 🙂
