# Change in Critical Point Filter

**URL:** https://discourse.paraview.org/t/change-in-critical-point-filter/10309
**Category:** ParaView Support
**Created:** [September 13, 2022, 8:38pm UTC](https://discourse.paraview.org/t/change-in-critical-point-filter/10309 "2022-09-13T20:38:02Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![Charles\_Gueunet](https://discourse.paraview.org/user_avatar/discourse.paraview.org/charles_gueunet/32/40_2.png) [@Charles\_Gueunet](https://discourse.paraview.org/u/Charles_Gueunet)
#### Post date: [September 14, 2022, 7:35am UTC](https://discourse.paraview.org/t/change-in-critical-point-filter/10309/2 "2022-09-14T07:35:10Z")

</div>

Hello @Pravin_Poudel

As we saw in your [previous topic](https://discourse.paraview.org/t/vertex-identifier-field-option-not-present-in-ttktopologicalsimplification-filter-properties/10281), there is no need to explicitely give the offset field anymore in TTK. Providing a non-conforming array may indeed lead to error as the order of the vertices may not be strict anymore.

You may also use the [ttk-data](https://github.com/topology-tool-kit/ttk-data) repository. With the latest paraview and the provided TTK, I was able to load the `dragon.pvsm` state, which has been updated (contrary to the video).  
In this new version, there is no offset anymore:

 ![image](https://discourse.paraview.org/uploads/default/original/2X/b/bd9982a6af49709827b63c621a885f051ac2fbc5.jpeg)

Best,  
Charles

---

_[View the full topic](https://discourse.paraview.org/t/change-in-critical-point-filter/10309)._