# Version 6.1.1 no longer reads my EnSight case files

**URL:** https://discourse.paraview.org/t/version-6-1-1-no-longer-reads-my-ensight-case-files/17583
**Category:** ParaView Support
**Tags:** vtk
**Created:** [May 26, 2026, 4:17pm UTC](https://discourse.paraview.org/t/version-6-1-1-no-longer-reads-my-ensight-case-files/17583 "2026-05-26T16:17:53Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![elynch](https://discourse.paraview.org/user_avatar/discourse.paraview.org/elynch/32/6418_2.png) [@elynch](https://discourse.paraview.org/u/elynch)
#### Post date: [May 26, 2026, 4:17pm UTC](https://discourse.paraview.org/t/version-6-1-1-no-longer-reads-my-ensight-case-files/17583/1 "2026-05-26T16:17:53Z")

</div>

[ensight\_case\_issue.zip](https://discourse.paraview.org/uploads/short-url/2jQRggAK6EtHmi0ryy6peFhZTFx.zip) (700.2 KB)

I’ve attached a dataset in EnSight Gold format. There are three versions of the case file. `original.case` is the format we have been writing for years and which ParaView has been able to parse successfully from at least version 4.3 up to 6.0.1. If I try to parse that same file in ParaView 6.1.0 or 6.1.1, I get an error:

```auto
vtkEnSightReader.cxx:1299 ERR| vtkEnSightGoldBinaryReader (0x3b00b90): Error with vtkEnSightReader: insufficient filename numbers!!!

```

If I reformat the file to put all the filename numbers on the same line, as in `filename_numbers_one_line.case`, I can read it successfully in version 6.1.1. I don’t think it should be required to put them all on the same line, since it hasn’t been required in any previous versions, and it’s not required for the time values below that.

I’ve also tried using the EnSightGoldCombinedReader plugin. With the plugin, reading original.case gives me the error:

```auto
EnSightDataSet.cxx:902 WARN| Parsing time section, found 4 steps, but only 0 time values

```

I found that if I make the E lowercase in the time values, as in `lowercase_exp.case`, I can read it successfully with the plugin. Case sensitivity looks like something introduced with the GetNumRegEx regular expression and not required by std::stod.

---

<div class="post-metadata">

### Author: ![cory.quammen](https://discourse.paraview.org/user_avatar/discourse.paraview.org/cory.quammen/32/11193_2.png) [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [May 28, 2026, 1:28pm UTC](https://discourse.paraview.org/t/version-6-1-1-no-longer-reads-my-ensight-case-files/17583/2 "2026-05-28T13:28:26Z")

</div>

Eric, thanks for your report and sample data. I will be taking a look at this and other EnSight reader issues reported in 6.1 ahead of the 6.2 release.

---

<div class="post-metadata">

### Author: ![cory.quammen](https://discourse.paraview.org/user_avatar/discourse.paraview.org/cory.quammen/32/11193_2.png) [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [May 28, 2026, 1:37pm UTC](https://discourse.paraview.org/t/version-6-1-1-no-longer-reads-my-ensight-case-files/17583/3 "2026-05-28T13:37:29Z")

</div>

I posted an issue here: [https://gitlab.kitware.com/paraview/paraview/-/work\_items/23294](https://gitlab.kitware.com/paraview/paraview/-/work_items/23294)