# Paraview 6.0.1 3D interaction latency/wiggles
**URL:** https://discourse.paraview.org/t/paraview-6-0-1-3d-interaction-latency-wiggles/17265
**Category:** ParaView Support
**Created:** [October 27, 2025, 3:39pm UTC](https://discourse.paraview.org/t/paraview-6-0-1-3d-interaction-latency-wiggles/17265 "2025-10-27T15:39:12Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@edabor](https://discourse.paraview.org/u/edabor)
#### Post date: [October 27, 2025, 3:39pm UTC](https://discourse.paraview.org/t/paraview-6-0-1-3d-interaction-latency-wiggles/17265/1 "2025-10-27T15:39:13Z")
Hello,
First, I would like to thanks Kitware’s developer for providing such great tool.
When trying to upgrade to **6.0.1** , I noticed weird latency/wiggles of the meshed actor when interacting with a sphere source, which was not occurring with **5.11.** I attached on screenshot video for each version, trying my best to highlight the issue.
Trying with a colleague of mine laptop’s revealed that the issue was due to our graphics card being slightly different, as reported by the `Help -> About` We have exactly the same fields except:
| My laptop | His | |
| --- | --- | --- |
| OpenGL Renderer: NVIDIA GeForce RTX **3050** Ti Laptop GPU/PCIe/SSE2 | OpenGL Renderer: NVIDIA GeForce RTX **4050** Ti Laptop GPU/PCIe/SSE2 | |
Here is my full `Help -> About` report for **6.0.1:**
```yaml
Client Information:
Version: 6.0.1
VTK Version: 9.5.2
Qt Version: 6.9.0
vtkIdType size: 64bits
Embedded Python: On
Python Library Path: C:\Program Files\ParaView 6.0.1\bin\Lib
Python Library Version: 3.12.7 (tags/v3.12.7:0b05ead, Oct 1 2024, 03:06:41) [MSC v.1941 64 bit (AMD64)]
Python Numpy Support: On
Python Numpy Path: C:\Program Files\ParaView 6.0.1\bin\lib\site-packages\numpy
Python Numpy Version: 1.26.4
Python Matplotlib Support: On
Python Matplotlib Path: C:\Program Files\ParaView 6.0.1\bin\lib\site-packages\matplotlib
Python Matplotlib Version: 3.7.2
Python Testing: Off
MPI Enabled: Off
ParaView Build ID: superbuild 8c0f929966f005396802f3b2957c734a6c68b3c1 (!1292)
Disable Registry: Off
Test Directory:
Data Directory:
SMP Backend: TBB
SMP Max Number of Threads: 20
OpenGL Vendor: NVIDIA Corporation
OpenGL Version: 3.2.0 NVIDIA 576.83
OpenGL Renderer: NVIDIA GeForce RTX 3050 Ti Laptop GPU/PCIe/SSE2
Accelerated filters overrides available: No
Connection Information:
Remote Connection: No
```
For **5.11** :
```yaml
Client Information:
Version: 5.11.0
VTK Version: 9.2.20220823
Qt Version: 5.15.2
vtkIdType size: 64bits
Embedded Python: On
Python Library Path: C:\Program Files\ParaView 5.11.0\bin\lib
Python Library Version: 3.9.13 (tags/v3.9.13:6de2ca5, May 17 2022, 16:36:42) [MSC v.1929 64 bit (AMD64)]
Python Numpy Support: On
Python Numpy Path: C:\Program Files\ParaView 5.11.0\bin\Lib\site-packages\numpy
Python Numpy Version: 1.21.1
Python Matplotlib Support: On
Python Matplotlib Path: C:\Program Files\ParaView 5.11.0\bin\Lib\site-packages\matplotlib
Python Matplotlib Version: 3.2.1
Python Testing: Off
MPI Enabled: Off
ParaView Build ID: superbuild 296d2d1b237965dbf5059263bb6feac90417f250 (!1041)
Disable Registry: Off
Test Directory:
Data Directory:
SMP Backend: TBB
SMP Max Number of Threads: 20
OpenGL Vendor: Intel
OpenGL Version: 3.2.0 - Build 32.0.101.6881
OpenGL Renderer: Intel(R) Iris(R) Xe Graphics
Accelerated filters overrides available: No
Connection Information:
Remote Connection: No
```
Thanks in advance.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [October 28, 2025, 8:21am UTC](https://discourse.paraview.org/t/paraview-6-0-1-3d-interaction-latency-wiggles/17265/2 "2025-10-28T08:21:36Z")
> Intel(R) Iris(R) Xe Graphics
In 5.11 you are somehow NOT using your GPU.
Maybe try doing that in 6.0.1 ?
---
### Author:  [@edabor](https://discourse.paraview.org/u/edabor)
#### Post date: [October 28, 2025, 8:42am UTC](https://discourse.paraview.org/t/paraview-6-0-1-3d-interaction-latency-wiggles/17265/3 "2025-10-28T08:42:52Z")
Could you point me how to disable GPU usage in Paraview ?
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [October 28, 2025, 8:51am UTC](https://discourse.paraview.org/t/paraview-6-0-1-3d-interaction-latency-wiggles/17265/4 "2025-10-28T08:51:18Z")
This is not controlled by ParaView but by your system. Typically this should be done in NVidia Settings or Windows settings directly.
---
### Author:  [@edabor](https://discourse.paraview.org/u/edabor)
#### Post date: [October 28, 2025, 9:07am UTC](https://discourse.paraview.org/t/paraview-6-0-1-3d-interaction-latency-wiggles/17265/5 "2025-10-28T09:07:13Z")
Indeed, deactivating the NVIDIA GPU temporary fixed the issue, as Paraview 6.0 now reports using Intel(R) Iris(R) Xe Graphics.
Do you think issuing a bug report in gitlab Paraview could help being able to use the GPU ?
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [October 28, 2025, 9:12am UTC](https://discourse.paraview.org/t/paraview-6-0-1-3d-interaction-latency-wiggles/17265/6 "2025-10-28T09:12:43Z")
this is probably a nvidia driver issue, not a ParaView issue. Please update your nvidia driver.
---
### Author:  [@edabor](https://discourse.paraview.org/u/edabor)
#### Post date: [October 28, 2025, 12:59pm UTC](https://discourse.paraview.org/t/paraview-6-0-1-3d-interaction-latency-wiggles/17265/7 "2025-10-28T12:59:53Z")
~~Issue solved by updating nvidia drivers.~~
Actually, the issue only appears when having a second screen plugged, even after updating GPU drivers.
FYI: I’ve tried 2 different screens without any difference.
---
### Author:  [@edabor](https://discourse.paraview.org/u/edabor)
#### Post date: [October 28, 2025, 2:06pm UTC](https://discourse.paraview.org/t/paraview-6-0-1-3d-interaction-latency-wiggles/17265/8 "2025-10-28T14:06:40Z")
If that can help, it seems that the whole GUI is affected. See attached video.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [October 30, 2025, 6:43am UTC](https://discourse.paraview.org/t/paraview-6-0-1-3d-interaction-latency-wiggles/17265/9 "2025-10-30T06:43:59Z")
> [@edabor](#):
>
> the issue only appears when having a second screen plugged
That points even more to a driver issue. No idea how to fix it though.