# Intel UHD 620 + VTK + Qt bug with new drivers on windows

**URL:** https://discourse.vtk.org/t/intel-uhd-620-vtk-qt-bug-with-new-drivers-on-windows/1694
**Category:** Support
**Created:** [September 4, 2019, 1:55pm UTC](https://discourse.vtk.org/t/intel-uhd-620-vtk-qt-bug-with-new-drivers-on-windows/1694 "2019-09-04T13:55:36Z")
**Posts on this page:** 1
**Showing post:** 9

<div class="post-metadata">

### Author: ![lassoan](https://discourse.vtk.org/user_avatar/discourse.vtk.org/lassoan/32/50_2.png) [@lassoan](https://discourse.vtk.org/u/lassoan)
#### Post date: [September 5, 2019, 1:05pm UTC](https://discourse.vtk.org/t/intel-uhd-620-vtk-qt-bug-with-new-drivers-on-windows/1694/9 "2019-09-05T13:05:34Z")

</div>

> [@simonesneault](#):
>
> Yes, unfortunately migrating back to the QVTKOpenGLNativeWidget seems to be the correct solution. That’s a pain because it took us sooo much time to get all things right with the new QVTKOpenGLWidget when it came out a year ago.

Switching to OpenGL2 rendering backend was indeed a big change, but did you have to update anything to work specifically with QVTKOpenGLWidget? My understanding is that QVTKOpenGLWidget and QVTKOpenGLNativeWidget are drop-in replacements.

QVTKOpenGLWidget may have been developed later, but it is not better than QVTKOpenGLNativeWidget - it is only for very special cases: when stereo rendering is needed and your application can comply to a number of restrictions. The conclusion of lengthy discussions on this topic is that [QVTKOpenGLNativeWidget is what people should use by default](https://discourse.vtk.org/t/how-to-decide-between-qvtkopengl-native-widget/1070/4). Current class names misleading but not changed to prevent further frustration of application developers.

---

_[View the full topic](https://discourse.vtk.org/t/intel-uhd-620-vtk-qt-bug-with-new-drivers-on-windows/1694)._