# LSDynaReader error: "Database has bad state size (0)" with SPH Double Precision files

**URL:** https://discourse.paraview.org/t/lsdynareader-error-database-has-bad-state-size-0-with-sph-double-precision-files/17466
**Category:** ParaView Support
**Created:** [March 8, 2026, 12:55pm UTC](https://discourse.paraview.org/t/lsdynareader-error-database-has-bad-state-size-0-with-sph-double-precision-files/17466 "2026-03-08T12:55:28Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Salvatore\_Russo](https://discourse.paraview.org/user_avatar/discourse.paraview.org/salvatore_russo/32/17522_2.png) [@Salvatore\_Russo](https://discourse.paraview.org/u/Salvatore_Russo)
#### Post date: [March 8, 2026, 12:55pm UTC](https://discourse.paraview.org/t/lsdynareader-error-database-has-bad-state-size-0-with-sph-double-precision-files/17466/1 "2026-03-08T12:55:28Z")

</div>

​Hi everyone,

​I am experiencing a persistent issue when trying to load LS-DYNA results in ParaView. Every time I select the base d3plot file and use the LSDynaReader, the following errors appear in the Output Messages:

​ERROR: In vtkLSDynaReader.cxx: Database has bad state size (0).

​ERROR: In vtkLSDynaReader.cxx: No valid time steps in the LS-Dyna database.

​Unknown Dimensionality 0 encountered.

​My environment:

​ParaView versions: Tested on both 5.13.0 and 6.1.0-RC1 (Windows 10/11).

​Data type: LS-DYNA simulation using SPH particles, written in Double Precision (DP).

​Validation: The files open and animate perfectly in LS-PrePost, so the database is healthy and complete.

​I have already tried to:

​Shorten the file path to avoid Windows character limits.

​Open only the base d3plot file (not the numbered ones).

​Check both the stable and the latest RC versions of ParaView.

​I found a similar discussion from December 2025 regarding crashes with discrete/eroded elements. It seems that when the simulation involves SPH or elements changing state, the reader fails to correctly map the memory offsets, especially in Double Precision.

​Is there a specific setting in the advanced properties of the reader that I should use? Or is this a known bug with the DP reader for SPH data?

​Thank you for your help!