# surface with edges representation in 5.7
**URL:** https://discourse.paraview.org/t/surface-with-edges-representation-in-5-7/2769
**Category:** ParaView Support
**Created:** [October 15, 2019, 1:19pm UTC](https://discourse.paraview.org/t/surface-with-edges-representation-in-5-7/2769 "2019-10-15T13:19:02Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@gbug](https://discourse.paraview.org/u/gbug)
#### Post date: [October 15, 2019, 1:19pm UTC](https://discourse.paraview.org/t/surface-with-edges-representation-in-5-7/2769/1 "2019-10-15T13:19:02Z")
Hi!
I’ve noticed render problems with Surface with edges representation and unstructured meshes (vtu) in 5.7 (see screenshots):
Is it a known problem? Tried run with -dr option – didn’t help.
env: debian testing amd64 with KF5, PV downloaded from the site (py3.7).
---
### Author:  [@Kenichiro-Yoshimi](https://discourse.paraview.org/u/Kenichiro-Yoshimi)
#### Post date: [October 16, 2019, 12:14am UTC](https://discourse.paraview.org/t/surface-with-edges-representation-in-5-7/2769/2 "2019-10-16T00:14:12Z")
I have the same problem as described by Gena Bug. I’m using ParaView 5.7.0 on Windows 10 with an NVIDIA GeForce RTX 2080 Ti.
[chair.obj](https://discourse.paraview.org/uploads/short-url/oVXwJk7W7PbgZb5e9RBBzinDKyi.obj) (1.3 MB)
---
### Author:  [@wascott](https://discourse.paraview.org/u/wascott)
#### Post date: [October 16, 2019, 12:44am UTC](https://discourse.paraview.org/t/surface-with-edges-representation-in-5-7/2769/3 "2019-10-16T00:44:15Z")
Looks good to me. I checked software rendering (remote server) and Windows hardware rendering (NVIDIA Quadro M4000).
---
### Author:  [@Kenichiro-Yoshimi](https://discourse.paraview.org/u/Kenichiro-Yoshimi)
#### Post date: [October 16, 2019, 1:23am UTC](https://discourse.paraview.org/t/surface-with-edges-representation-in-5-7/2769/4 "2019-10-16T01:23:56Z")
Parallel projection mode seems to cause the crosshair artifact. Indeed, for perspective view it works well.
---
### Author:  [@wascott](https://discourse.paraview.org/u/wascott)
#### Post date: [October 16, 2019, 1:27am UTC](https://discourse.paraview.org/t/surface-with-edges-representation-in-5-7/2769/5 "2019-10-16T01:27:43Z")
Kyoshimi,
Well done. I have replicated the bug. i will write it up.
Alan
---
### Author:  [@wascott](https://discourse.paraview.org/u/wascott)
#### Post date: [October 16, 2019, 1:49am UTC](https://discourse.paraview.org/t/surface-with-edges-representation-in-5-7/2769/6 "2019-10-16T01:49:38Z")
Bug has been written up here: [https://gitlab.kitware.com/paraview/paraview/issues/19398](https://gitlab.kitware.com/paraview/paraview/issues/19398). I wrote it up for ParaView 5.8.0, but it very likely will slip to 5.9.0. 5.8.0 is both already full, and coming quickly (early winter).
---
### Author:  [@wascott](https://discourse.paraview.org/u/wascott)
#### Post date: [October 17, 2019, 2:14am UTC](https://discourse.paraview.org/t/surface-with-edges-representation-in-5-7/2769/7 "2019-10-17T02:14:19Z")
This can be worked around by going into Edit/ Settings/ Render View/ Line Offset Parameters, and changing -4 to a MUCH smaller number, such as -0.1.
---
### Author:  [@gbug](https://discourse.paraview.org/u/gbug)
#### Post date: [October 17, 2019, 10:02am UTC](https://discourse.paraview.org/t/surface-with-edges-representation-in-5-7/2769/8 "2019-10-17T10:02:44Z")
Thanks for the workaround, it really helps. However I should mention that in my case mesh in perspective projection looks better than in parallel:
---
### Author:  [@wascott](https://discourse.paraview.org/u/wascott)
#### Post date: [November 28, 2019, 3:05am UTC](https://discourse.paraview.org/t/surface-with-edges-representation-in-5-7/2769/9 "2019-11-28T03:05:02Z")
I wanted to mention that this is being worked in [https://gitlab.kitware.com/paraview/paraview/issues/19437/](https://gitlab.kitware.com/paraview/paraview/issues/19437/) It has become a big enough issue we will try to get it into 5.8, out this winter.