# Mapper and PolyData Have Different Bounds

**URL:** https://discourse.vtk.org/t/mapper-and-polydata-have-different-bounds/9839
**Category:** Support
**Created:** [November 17, 2022, 2:39am UTC](https://discourse.vtk.org/t/mapper-and-polydata-have-different-bounds/9839 "2022-11-17T02:39:07Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![wmm](https://discourse.vtk.org/letter_avatar_proxy/v4/letter/w/779978/32.png) [@wmm](https://discourse.vtk.org/u/wmm)
#### Post date: [November 17, 2022, 2:39am UTC](https://discourse.vtk.org/t/mapper-and-polydata-have-different-bounds/9839/1 "2022-11-17T02:39:07Z")

</div>

I have a vtkPolyData object controlled by a vtkActor and a vtkPolyDataMapper. In the VTK 8.x version of my app I could transform the polydata, store it back in mapper, and the bounds of the actor, mapper, and polydata would all be automatically updated and all have the same values.

In the VTK 9.1.0 version of the app, the bounds of the actor and mapper do not get updated the transformation, causing havoc later in the app. Of course I am calling Modified() and Update() all of the place as I have been doing for years.

My current workaround is to use the polydata bounds instead of the actor bounds in the broken code.

However, I does anybody know how to keep the bounds of all of these objects in sync?