Import .pvd file into paraview and error occurred in 7.2.1 Running Paraview

[Maoyin_Luo]

I have followed this postprocess instruction of fluid_bed_dem_2d to output .RES and .pvd files but error occurred when I imported particle .pvd files into Paraview software, here are error files(Error.txt) and mfix bug report zip, could someone give me some help? Thank you! I thought if I can reset this fluid_bed_dem_2d tutorial in Mfix for I seemed to make some undesirable changes in this tutorial

fluid_bed_dem_2d_2026-06-21T152710.583024.zip (770.9 KB)

fluid_bed_dem_2d.mfx (9.7 KB)

Errors.txt (29.0 KB)

[jeff.dietiker]

There is an issue with the latest Paraview version (6.1), and Charles has a fix for it

.vtu/.vtp output >4 GB unreadable — 64-bit offsets needed - Potential Fix for MFIX-26*

Thanks Eric. We’ll do some testing and probably include your 64-bit patch in the next MFiX release (unscheduled at this time) Re: the Paraview 6.1 issue: Paraview doesn’t like the space character in front of the timestep value in the pvd file, they already have a fix for this (thanks for reporting the issue, it’s nice to see the open-source ecosystem working as intended): vtkPVDReader: Fix parsing of values (!7827) · Merge requests · ParaView / ParaView · GitLab We can also avoid creating …

You can also use previous versions of Paraview that accept the extra space in the timestep string.