# Strange effects with volume representation
**URL:** https://discourse.paraview.org/t/strange-effects-with-volume-representation/2951
**Category:** ParaView Support
**Created:** [November 11, 2019, 1:06pm UTC](https://discourse.paraview.org/t/strange-effects-with-volume-representation/2951 "2019-11-11T13:06:00Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@cobo](https://discourse.paraview.org/u/cobo)
#### Post date: [November 11, 2019, 1:06pm UTC](https://discourse.paraview.org/t/strange-effects-with-volume-representation/2951/1 "2019-11-11T13:06:00Z")
Just downloaded and installed Paraview 5.7 on two brand new Lenovo T590 notebooks, both with Interl UHD Graphics 620, but the one with Windows 10 (1903) and the other with Ubuntu 18.04.
On the Windows machine there seems to be a problem with the “Volume” representation:
It looks like the OpenGL graphics render view is taking over the entire main window of the application, so any widgets and controls are not showing and working any more properly.
Steps to reproduce: Source -\> Data Objects -\> Wavelet -\> Apply -\> switch to “Volume” representation.
The same procedure on the exactly same hardware, but with Ubuntu 18.04 works “as advertised”.
Any possible setting or whatever that can be applied to get this right again?
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [November 11, 2019, 3:19pm UTC](https://discourse.paraview.org/t/strange-effects-with-volume-representation/2951/2 "2019-11-11T15:19:07Z")
We are seeing this a lot with ParaView 5.7 running on Windows 10 and Intel graphics hardware. We do not have a solution yet, other than to use a discrete graphics card for rendering if it is available on the system.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [November 12, 2019, 9:17am UTC](https://discourse.paraview.org/t/strange-effects-with-volume-representation/2951/3 "2019-11-12T09:17:10Z")
For reference :
[https://gitlab.kitware.com/paraview/paraview/issues/19364](https://gitlab.kitware.com/paraview/paraview/issues/19364)
I’ve updated the issue with your data @cobo, but I miss your driver version, could you provide it ?
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [November 12, 2019, 9:50am UTC](https://discourse.paraview.org/t/strange-effects-with-volume-representation/2951/4 "2019-11-12T09:50:23Z")
@cobo : Only on volume ? All works fine apart volume rendering ?
---
### Author:  [@cobo](https://discourse.paraview.org/u/cobo)
#### Post date: [November 12, 2019, 11:59am UTC](https://discourse.paraview.org/t/strange-effects-with-volume-representation/2951/5 "2019-11-12T11:59:01Z")
I had seen some rendering errors in a surface view with edges: some edges were visible which are not supposed to be.
But now that I tried to find a reproducible case that is much easier than some large model I could reproduce that effect of “taking over the entire area” with another very simple procedure:
- From sources generate a box
- Change the color to “Normals”
- -\> done:
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [November 12, 2019, 12:15pm UTC](https://discourse.paraview.org/t/strange-effects-with-volume-representation/2951/6 "2019-11-12T12:15:14Z")
So it is the same issue.
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [November 12, 2019, 2:23pm UTC](https://discourse.paraview.org/t/strange-effects-with-volume-representation/2951/7 "2019-11-12T14:23:27Z")
The edges offset from surface is not Intel-related and is a known issue. See [https://gitlab.kitware.com/paraview/paraview/issues/19437](https://gitlab.kitware.com/paraview/paraview/issues/19437).