# 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:** 2

<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 4, 2019, 3:09pm UTC](https://discourse.vtk.org/t/intel-uhd-620-vtk-qt-bug-with-new-drivers-on-windows/1694/2 "2019-09-04T15:09:14Z")

</div>

Setting up the surface format is not trivial. Simply calling `QSurfaceFormat::setDefaultFormat( QVTKOpenGLWidget::defaultFormat() );` is certainly not enough. We received many problem reports with various configurations (OS, graphics card, etc.) since the OpenGL2 backend switch and ended up with this initialization sequence, which seems to work well (for computers that are not older than about 5 years):

> <https://github.com/Slicer/Slicer/blob/f0e67a9a4e8de1181f805ab47bdfef012a6b4ef9/Libs/MRML/Widgets/qMRMLWidget.cxx#L78-L144>

---

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