# Picture in picture bug in OSPRay Animation Export

**URL:** https://discourse.paraview.org/t/picture-in-picture-bug-in-ospray-animation-export/2180
**Category:** Development
**Created:** [July 8, 2019, 4:05pm UTC](https://discourse.paraview.org/t/picture-in-picture-bug-in-ospray-animation-export/2180 "2019-07-08T16:05:32Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![Dave\_DeMarle](https://discourse.paraview.org/user_avatar/discourse.paraview.org/dave_demarle/32/27_2.png) [@Dave\_DeMarle](https://discourse.paraview.org/u/Dave_DeMarle)
#### Post date: [July 11, 2019, 2:00pm UTC](https://discourse.paraview.org/t/picture-in-picture-bug-in-ospray-animation-export/2180/2 "2019-07-11T14:00:07Z")

</div>

I’ve seen/fixed similar problems in the past where the export was being done from the GUI and the exported image resolution was larger than the view, causing VTK/ParaView to go into stitching mode to make up the large images, which tripped up the accumulation mode we use for progressive refinement.

My guess is that this is happening again.

If you are building ParaView from source you can hardcode progressive refinement off as well here:  
[https://gitlab.kitware.com/vtk/vtk/blob/master/Rendering/RayTracing/vtkOSPRayRendererNode.cxx#L1170](https://gitlab.kitware.com/vtk/vtk/blob/master/Rendering/RayTracing/vtkOSPRayRendererNode.cxx#L1170).

Otherwise, please try a smaller image and let me know if this hides the problem.

---

_[View the full topic](https://discourse.paraview.org/t/picture-in-picture-bug-in-ospray-animation-export/2180)._