# octree mesh loss of functionality in v5 paraview
**URL:** https://discourse.paraview.org/t/octree-mesh-loss-of-functionality-in-v5-paraview/689
**Category:** ParaView Support
**Created:** [October 6, 2018, 9:55pm UTC](https://discourse.paraview.org/t/octree-mesh-loss-of-functionality-in-v5-paraview/689 "2018-10-06T21:55:27Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@garcfd](https://discourse.paraview.org/u/garcfd)
#### Post date: [October 6, 2018, 9:55pm UTC](https://discourse.paraview.org/t/octree-mesh-loss-of-functionality-in-v5-paraview/689/1 "2018-10-06T21:55:27Z")
Using same demo octree mesh (unstructured vtk) as in my previous topic…
> **[octree.vtk](https://drive.google.com/file/d/1O4bxadtFyvLG9NWjSHeiS8AptYMc-hc8/view)**
>
> Google Drive file.
I notice that basic scalar visibility works fine in v3.98.1 and v4.3.1
but in version 5.1 the scalar values are initially shown as uniform
…and I have to then use “cell data to point data” to see anything useful.
How can I modify the octree mesh, to make it more compatible with v5 onwards?
and what changed between v4 and v5 to cause this issue for me? Thanks.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [October 8, 2018, 12:02pm UTC](https://discourse.paraview.org/t/octree-mesh-loss-of-functionality-in-v5-paraview/689/2 "2018-10-08T12:02:00Z")
This works perfectly in the current master as well as last release and last RC.
---
### Author:  [@garcfd](https://discourse.paraview.org/u/garcfd)
#### Post date: [October 8, 2018, 7:07pm UTC](https://discourse.paraview.org/t/octree-mesh-loss-of-functionality-in-v5-paraview/689/3 "2018-10-08T19:07:07Z")
thats perplexing - I have noticed the same issue on 2 different laptops.
The difficulty being that I cant get version 5.6 to run on either of them.
I have been testing with version 5.0 & 5.2
when you say works perfectly - can you see the different level colours immediately after import?
Thanks
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [October 9, 2018, 7:21am UTC](https://discourse.paraview.org/t/octree-mesh-loss-of-functionality-in-v5-paraview/689/4 "2018-10-09T07:21:46Z")
Yes indeed, when I open it, the “lev” array is visible directly.
It works perfectly in ParaView 5.2 as well.
---
### Author:  [@garcfd](https://discourse.paraview.org/u/garcfd)
#### Post date: [October 9, 2018, 10:51am UTC](https://discourse.paraview.org/t/octree-mesh-loss-of-functionality-in-v5-paraview/689/5 "2018-10-09T10:51:28Z")
thats wierd. I mean all I have to do is cell data to point data, and the contours appear.
so I wouldnt have associated that with a graphics driver problem
I would have though that its looking for point data, but getting cell data instead.
I think something must have changed in v5 onwards, that requires me to use the cell data to point data filter…?
---
### Author:  [@garcfd](https://discourse.paraview.org/u/garcfd)
#### Post date: [October 9, 2018, 2:16pm UTC](https://discourse.paraview.org/t/octree-mesh-loss-of-functionality-in-v5-paraview/689/6 "2018-10-09T14:16:47Z")
anyway I get this warning when I start up Paraview v5.2,0, so you are probably right - its down to the (my) graphics driver not being suitable or modern enough. Bummer!
---
### Author:  [@syedharoonalam](https://discourse.paraview.org/u/syedharoonalam)
#### Post date: [September 11, 2020, 5:00pm UTC](https://discourse.paraview.org/t/octree-mesh-loss-of-functionality-in-v5-paraview/689/7 "2020-09-11T17:00:19Z")
@garcfd @mwestphal Can you reshare the octree.vtk (unstructured vtk) file for me?
I needed to do some experiments to generate octree mesh. Thank you,
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [September 14, 2020, 8:02am UTC](https://discourse.paraview.org/t/octree-mesh-loss-of-functionality-in-v5-paraview/689/8 "2020-09-14T08:02:30Z")
I didn’t kept it.