# Problems with Catalyst2 and Paraview Live Visualization

**URL:** https://discourse.paraview.org/t/problems-with-catalyst2-and-paraview-live-visualization/11401
**Category:** In Situ Support
**Created:** [February 14, 2023, 1:03pm UTC](https://discourse.paraview.org/t/problems-with-catalyst2-and-paraview-live-visualization/11401 "2023-02-14T13:03:12Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![Lucas\_Givord](https://discourse.paraview.org/user_avatar/discourse.paraview.org/lucas_givord/32/6851_2.png) [@Lucas\_Givord](https://discourse.paraview.org/u/Lucas_Givord)
#### Post date: [February 14, 2023, 2:27pm UTC](https://discourse.paraview.org/t/problems-with-catalyst2-and-paraview-live-visualization/11401/3 "2023-02-14T14:27:42Z")

</div>

Hello @SadBoySquad,

I quickly tested the same example with Catalyt2 and I have exactly like you.

Regarding the freeze issue, it would seem that it is due to the fact that the simulation is faster than the visualization pipeline, by consequent paraview has still not finished treating the step 1 that it already receives data for step2 and so on until the end of the simulation. To confirm that, I simply add a `time.sleep(1)` in the `catalyst_execute` in the `catalyst_pipeline.py` and I can have an interactive pipeline.

For the breakpoint issue, if you’re interested I opened last month an issue about it [https://gitlab.kitware.com/paraview/paraview/-/issues/21735](https://gitlab.kitware.com/paraview/paraview/-/issues/21735) 🙂

---

_[View the full topic](https://discourse.paraview.org/t/problems-with-catalyst2-and-paraview-live-visualization/11401)._