# vtkrenderedareaselector with one vtkAssembly for the renderer

**URL:** https://discourse.vtk.org/t/vtkrenderedareaselector-with-one-vtkassembly-for-the-renderer/6163
**Category:** Support
**Created:** [July 9, 2021, 6:06pm UTC](https://discourse.vtk.org/t/vtkrenderedareaselector-with-one-vtkassembly-for-the-renderer/6163 "2021-07-09T18:06:50Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Bill\_McGrory](https://discourse.vtk.org/user_avatar/discourse.vtk.org/bill_mcgrory/32/3654_2.png) [@Bill\_McGrory](https://discourse.vtk.org/u/Bill_McGrory)
#### Post date: [July 9, 2021, 6:06pm UTC](https://discourse.vtk.org/t/vtkrenderedareaselector-with-one-vtkassembly-for-the-renderer/6163/1 "2021-07-09T18:06:50Z")

</div>

I have an application that I am porting an earlier version of VTK (5.2) to use the latest supported version. The legacy app has a single renderer with a single vtkAssembly that builds a nested structure of actors. Picking is implemented through the vtkRenderedAreaPicker, and with the legacy version, I could use the GetProp3Ds from an area pick to select the child props that were picked from that single vtkAssembly.

However, when I migrated to the newest version which now uses the vtkHardwareSelector, the top level vtkAssembly is returned, not the lowest level. Am I missing something?  
Is there a way to get at the actual child prop that was picked without adding all the children as props to the renderer?  
TIA  
Bill