# P2D/P3D causes image flickering and disappearing from draw() loop?!

**URL:** <https://discourse.processing.org/t/p2d-p3d-causes-image-flickering-and-disappearing-from-draw-loop/36877>\
**Category:** Coding Questions\
**Created:** [May 13, 2022, 6:56pm UTC](https://discourse.processing.org/t/p2d-p3d-causes-image-flickering-and-disappearing-from-draw-loop/36877 "2022-05-13T18:56:25Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![glv](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/glv/32/18785_2.png) [@glv](https://discourse.processing.org/u/glv)\
**Post date:** [May 15, 2022, 1:07am UTC](https://discourse.processing.org/t/p2d-p3d-causes-image-flickering-and-disappearing-from-draw-loop/36877/3 "2022-05-15T01:07:28Z")

</div>

Hello,

This works fine on Windows 10.

Try updatding to the latest version Processing 4.0 beta 8.

Try adding _frameRate(30)_ to _setup()_.

Please report what happens after trying above.

Reference:

> [@Big Sur and new Macs](https://discourse.processing.org/t/big-sur-and-new-macs/25374):
>
> Hi all, Wondering if anyone willing to share initial experiences with Processing on the new Mac hardware and “Big Sur” OS11 (OSX 11? OSXI?) … For context, we have a number of semi-permanent and permanent installations that use Mac minis and run Processing/Java full-out, thousands of threads, 24/7 type things, and sometimes require external hardware like sound cards etc. Wondering what kind of change we should be prepared for if we start using the new silicon and operating system. Catalin…

`:)`

---

_[View the full topic](https://discourse.processing.org/t/p2d-p3d-causes-image-flickering-and-disappearing-from-draw-loop/36877)._
