# How to disable DirectX in JUCE 8?

**URL:** <https://forum.juce.com/t/how-to-disable-directx-in-juce-8/61822>\
**Category:** General JUCE discussion\
**Created:** [June 13, 2024, 6:19am UTC](https://forum.juce.com/t/how-to-disable-directx-in-juce-8/61822 "2024-06-13T06:19:35Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![Verbonaut](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/verbonaut/32/11824_2.png) [@Verbonaut](https://forum.juce.com/u/Verbonaut)\
**Post date:** [August 12, 2024, 4:55pm UTC](https://forum.juce.com/t/how-to-disable-directx-in-juce-8/61822/19 "2024-08-12T16:55:25Z")

</div>

We also have a group going into detail about what their problems are, there are plenty of examples of those on the forum. Personally it’s those I am taking notes from.

At time of posting literally the next post in the list is [this](https://forum.juce.com/t/juce-8-bug-with-long-menus-in-ableton-live/61973/12) about pop-up menus not working properly. A candidate fix is in development but not yet deployed. Why would people even experiment with Juce 8 when things like this are so prevalent? I prefer to upgrade frameworks when they appear to be relatively stable, and if major feature additions are the probable cause of issues coupled with an abrupt cessation of development of the prior major version, I think it is reasonable to ask for ways to ease into those major changes.

---

_[View the full topic](https://forum.juce.com/t/how-to-disable-directx-in-juce-8/61822)._
