P3D & P2D window not showing on MacOS Ventura

[processing-bot]

Created by: chrisgrizzly

Description

When using the P3D and P2D renderers, the window is not plotted on MacOS Ventura. With default size(), the window shows up correctly.

Expected Behavior

The window should show up when using P3D and P2D.

Current Behavior

The code will run, but no window rendered. From Mission Control on MacOS, a silhouette of the window could be seen, but the content is transparent. A thumbnail of the window is also shown at the top of Mission Control. See picture.

Steps to Reproduce

1. Install MacOS Ventura beta
2. Open example Topics>Textures>TextureCube
3. Run

Your Environment

• Processing version: 4.0.1 (August 9, 2022)
• Operating System and OS version: macOS 13.0 Beta (22A5331f)
• Other information:

[processing-bot]

Created by: kdjanz

Confirmed with most recent beta Version 13.0 Beta (22A5331f).
Neither 4.0.1 for ARM or Intel will display the output window.

It appears the new version of Metal 3 in Ventura is not connecting with the old OpenGL calls.

[processing-bot]

Created by: kdjanz

Just to confirm that everything works in Monterey as expected.

[processing-bot]

Created by: brad-miller

JDK 17 release notes
perhaps this might be of interest?

client-libs/2d
➜ JEP 382: New macOS Rendering Pipeline
The Java 2D API used by the Swing APIs for rendering, can now use the new Apple Metal accelerated rendering API for macOS.

This is currently disabled by default, so rendering still uses OpenGL APIs, which are deprecated by Apple but still available and supported.

To enable Metal, an application should specify its use by setting the system property:

-Dsun.java2d.metal=true

Use of Metal or OpenGL is transparent to applications since this is a difference of internal implementation and has no effect on Java APIs. The metal pipeline requires macOS 10.14.x or later. Attempts to set it on earlier releases will be ignored.

For further details, see JEP 382.

[processing-bot]

Created by: kdjanz

Confirmed to still be an issue with the most recent beta Version 13.0 Beta (22A5342f) (beta5)

I don't understand enough to attempt to implement, but perhaps that will help someone with deeper knowledge.

To enable Metal, an application should specify its use by setting the system property:
-Dsun.java2d.metal=true

I hope this can be fixed in the next release.

[processing-bot]

Created by: kdjanz

I tried adding the line

-Dsun.java2d.metal=true
to the file at "/Applications/Processing\ ARM.app/Contents/PlugIns/jdk-17.0.4+8/Contents/Home/conf/conf/management/management.properties" then saving and restarting Processing, but it did nothing - which is not surprising since I have no clue as to what I am really doing!

[processing-bot]

Created by: chrisgrizzly

Still an issues for the lated beta: Ventura 13.0 Beta (22A5352e). Hopefully this could be fixed before the official release of the OS, which is not far from now.

[processing-bot]

Created by: chrisgrizzly

Possible workaround

Use fullScreen(P3D); instead of size(640, 360, P3D);. This will correctly render in fullscreen.

Any other ideas on how to exit fullscreen and set a window size? If so, the workaround would be better.

[processing-bot]

Created by: benfry

Due to limited time, I'll have to wait until the Ventura release before taking a look at any of this, since I'm already supporting 3 versions of macOS across both Intel and Apple Silicon, and can't add an unreleased operating systems to the list.

With any luck, this may be fixed by Apple during the Ventura release process. It's definitely happened in the past (another reason I don't test with betas) though I'm not super optimistic.

Happy for any help on this one…

[processing-bot]

Created by: chrisgrizzly

The issue is still there on macOS Ventura Release Candidate, which is equivalent to the final release.

[processing-bot]

Created by: chrisgrizzly

The issue is persistent in MacOS Ventura officially released today.

[processing-bot]

Created by: jaegonlee

Another workaround(for m1 mac)

Add this code in PApplet.java(line 10146)

    if (present) {
      if (hideStop) {
        stopColor = 0;  // they'll get the hint
      }
      surface.placePresent(stopColor);
    } else {
      // start
      if (platform == MACOS) {
        try {
          final String td = "processing.core.ThinkDifferent";
          final Class<?> thinkDifferent = PApplet.class.getClassLoader().loadClass(td);
          thinkDifferent.getMethod("showMenuBar").invoke(null);
        } catch (Exception e) {
          e.printStackTrace();
        }
      }
      // end
      surface.placeWindow(location, editorLocation);
    }

Tested on macOS 13.0 (22A380) / macbook pro m1

[processing-bot]

Created by: jaegonlee

I found a simple workaround

I switched the order of the functions(initDisplay(), initGL()) in PSurfaceJOGL.java
from

  public void initFrame(PApplet sketch) {
    this.sketch = sketch;

    initIcons();
    initDisplay(); // 
    initGL(); // 
    initWindow();
    initListeners();
    initAnimator();
  }

to

  public void initFrame(PApplet sketch) {
    this.sketch = sketch;

    initIcons();
    initGL(); //
    initDisplay(); //
    initWindow();
    initListeners();
    initAnimator();
  }

Or add this code to the top of processing code.

import com.jogamp.opengl.GLProfile;
{
  GLProfile.initSingleton();
}

void setup() {
  size(1024, 768, P3D);
...

Tested on macOS 13.0 (22A380) / macbook pro m1

[processing-bot]

Created by: kdjanz

I downloaded source from GitHub and made the very simple changes in the last post from Jaegonlee. I rebuilt from scratch and the new binary works perfectly.

The only hiccup is that the new binary is Intel, so I end up having to run using Rosetta again on my M1 Mac Studio. That's fine until the official fix is made. Hopefully this can be fixed in the next release.

Thanks Jaegonlee!

[processing-bot]

Created by: benfry

Awesome, many many thanks @jaegonlee… 

That change is now incorporated and will be part of 4.0.2 when it's released.

[processing-bot]

Created by: retiutut

Thanks @jaegonlee @benfry! We have sent out a message to our Mac users to post-pone updating for this reason. Happy to hear that a fix was taken care of swiftly!