# Known Problem? SKIA and OpenGL on Windows

**URL:** <https://iplug2.discourse.group/t/known-problem-skia-and-opengl-on-windows/570>\
**Category:** Windows\
**Created:** [16 February 2022 06:31 UTC](https://iplug2.discourse.group/t/known-problem-skia-and-opengl-on-windows/570 "2022-02-16T06:31:49Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ToneSpotter](https://yyz2.discourse-cdn.com/free1/user_avatar/iplug2.discourse.group/tonespotter/32/148_2.png) [@ToneSpotter](https://iplug2.discourse.group/u/ToneSpotter)\
**Post date:** [16 February 2022 06:31 UTC](https://iplug2.discourse.group/t/known-problem-skia-and-opengl-on-windows/570/1 "2022-02-16T06:31:49Z")

</div>

I’ve tried to switch SKIA to GL3 (as described in [03\_Switching\_graphics · iPlug2/iPlug2 Wiki · GitHub](https://github.com/iPlug2/iPlug2/wiki/03_Switching_graphics#using-gl3-on-windows) ). and tested it on Windows 10. On my main development computer all is fine (and part of the work is moved to the GPU), but on an (very new) gaming laptop (with a real graphic card) the plugins freeze my Studio One instance (haven’t tried other DAWs).

Are there known problems with SKIA + GL3 + Windows? Is this the reason, that the documented default mode for SKIA is `IGRAPHICS_CPU`?

---

<div class="post-metadata">

**Author:** ![ToneSpotter](https://yyz2.discourse-cdn.com/free1/user_avatar/iplug2.discourse.group/tonespotter/32/148_2.png) [@ToneSpotter](https://iplug2.discourse.group/u/ToneSpotter)\
**Post date:** [16 February 2022 07:10 UTC](https://iplug2.discourse.group/t/known-problem-skia-and-opengl-on-windows/570/2 "2022-02-16T07:10:36Z")

</div>

I forgot to write: same problem with GL2

---

<div class="post-metadata">

**Author:** ![olilarkin](https://yyz2.discourse-cdn.com/free1/user_avatar/iplug2.discourse.group/olilarkin/32/2_2.png) [@olilarkin](https://iplug2.discourse.group/u/olilarkin)\
**Post date:** [20 February 2022 20:25 UTC](https://iplug2.discourse.group/t/known-problem-skia-and-opengl-on-windows/570/3 "2022-02-20T20:25:06Z")

</div>

There is no known issue like this. If you can find out as much as possible and make an issue on github i’ll see if I can reproduce it.
