# no fields are rendered after opening OpenPMD file

**URL:** https://discourse.paraview.org/t/no-fields-are-rendered-after-opening-openpmd-file/15533
**Category:** ParaView Support
**Created:** [October 10, 2024, 6:42pm UTC](https://discourse.paraview.org/t/no-fields-are-rendered-after-opening-openpmd-file/15533 "2024-10-10T18:42:36Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![ayenpure](https://discourse.paraview.org/user_avatar/discourse.paraview.org/ayenpure/32/12961_2.png) [@ayenpure](https://discourse.paraview.org/u/ayenpure)
#### Post date: [October 31, 2024, 8:03pm UTC](https://discourse.paraview.org/t/no-fields-are-rendered-after-opening-openpmd-file/15533/6 "2024-10-31T20:03:37Z")

</div>

Issue identified: Since we did not fully support AMR grids using the openPMD reader, in the last iteration of updates we skipped all arrays whose variable names contain `_lvl`. This was done because the openPMD reader crashed when there were arrays with different shapes becase of different levels of refinement. As a side effect, the feature the data that was previously possible to load will break. If you’re interested I can send a python drop-in replacement to get around the issue until we implement full AMR support in the near future.

---

_[View the full topic](https://discourse.paraview.org/t/no-fields-are-rendered-after-opening-openpmd-file/15533)._