heronarts / LXStudio

LXStudio Digital Lighting Workstation
http://lx.studio
Other
103 stars 4 forks source link

((LXStudio-IDE)) no UI visible at runtime - on mac OS Ventura #6

Open nargetdev opened 1 year ago

nargetdev commented 1 year ago

This just started happening today. No UI visible at runtime. Wonder if any others have seen this behavior?

May just be an intellij configuration thing...

My output at runtime:

[LX 2022/10/31 21:45:35] Initializing LXStudio version 0.4.1 with LX version 0.4.1
[LX 2022/10/31 21:45:36] Project loaded successfully from /Users/mswhiskers/007/ethfs/01__SRC/LX/LXStudio-IDE/Projects/Example.lxp
[LX 2022/10/31 21:45:37] LXEngine.ExecutorService starting...
mcslee commented 1 year ago

Hrm, would need to maybe see more about the full Java config and how you're starting this up.

Again, maybe reference the runtime configuration readme: https://github.com/heronarts/LXStudio-IDE#configure-your-runtime

Do you have the appropriate symlink set up and argument passed to the Java invocation to link the appropriate native libs for Processing? Specifically this flag -Djava.library.path=lib/processing-4.0b8/native (assuming native is a symlink pointing to the right version for your architecture/JVM).

nargetdev commented 1 year ago

Yea I do.

I think it might be on processing this time.. I'm getting the same behavior via LXStudio-P4 through the processing applet. No error whatsoever in either case, just no visible window.

parabolala commented 1 year ago

I'm experienceing the same issue. It started after I've upgraded to macOS Ventura. The window is invisible.

However when I open Mission Control, the window does show up in the tiny desktop preview on top:

Screenshot 2022-11-03 at 4 51 14 PM
mcslee commented 1 year ago

Hrm, bummer. Wouldn't be the first time there have been Mac/Processing compatibility issues. Processing 3 ended up unfortunately not working at all on modern macs...

@parabolala - are you able to also test the Processing IDE based version of LXStudio at https://github.com/heronarts/LXStudio-P4

Let me know if anything appears in the window when you run that way?

@nargetdev - are you also on macOS Ventura?

Weird that the preview does displays... definitely seems like some kind of graphics layer issue. Processing is still OpenGL-based which tends to cause problems since Apple has announced it's not going to be officially supported forever.

For context here - I am working on moving LX completely over to a new graphics layer which I hope to have available reasonably soon, I feel the project has reached the limits of using Processing as a full application graphics layer. Hopefully we can find a temporary solution for this.

parabolala commented 1 year ago

I get the same result for Processing-based LXStudio-P4

nargetdev commented 1 year ago

I'm experienceing the same issue. It started after I've upgraded to macOS Ventura. The window is invisible.

Ahh nice catch @parabolala I also just upgraded to Ventura

nargetdev commented 1 year ago

For this reason I'd be interested in some docker builds with VNC frontend like noVNC

docker run -d -p 5901:5901 -p 6901:6901 consol/centos-xfce-vnc

==[then_visit]==> http://localhost:6901

Useful if your host is elsewhere on the network, or even in the cloud.

mcslee commented 1 year ago

Confirming that this is a known issue with Processing/Ventura. https://github.com/processing/processing4/issues/544

Looks like there's a possible quick hack-fix for it. I don't have Ventura, so I can't test, but this doesn't seem to break anything on Monterey.

LXStudio-IDE - on the ventura branch: https://github.com/heronarts/LXStudio-IDE/commit/719ac892012887ca082f1a5529e22014a0d00b9a

LXStudio-P4 - on the ventura branch https://github.com/heronarts/LXStudio-P4/commit/85302e55057cd320ed2d0834b445e43417602564

Try replicating that GLProfile initialization call in your projects. Maybe this gets things running for now? Hopefully a future Ventura-compatible release of Processing will render this unnecessary in the long-term.

mcslee commented 1 year ago

Also confirming it looks like this has been resolved and will be available whenever Processing 4.0.2 gets released: https://github.com/processing/processing4/commit/9e3522ad2a2b786b0f70d899b3b67b8f6f0bf1c3

So the hack shouldn't be needed for long. Closing this issue out, but please feel free to chime in with further comments or test reports if you give this a whirl.

parabolala commented 1 year ago

Can confirm the branch ventura of LXStudio-IDE (719ac89) fixes the issue. Thanks

nargetdev commented 1 year ago

Same. Well played @mcslee

Also P.S. just downloaded Eclipse and had a much better experience (build on first try w/out modification)

oveddan commented 1 year ago

Confirming that this is a known issue with Processing/Ventura. processing/processing4#544

Looks like there's a possible quick hack-fix for it. I don't have Ventura, so I can't test, but this doesn't seem to break anything on Monterey.

LXStudio-IDE - on the ventura branch: heronarts/LXStudio-IDE@719ac89

LXStudio-P4 - on the ventura branch heronarts/LXStudio-P4@85302e5

Try replicating that GLProfile initialization call in your projects. Maybe this gets things running for now? Hopefully a future Ventura-compatible release of Processing will render this unnecessary in the long-term.

I had the same issue on Ventura and this solved it, thanks for the fix

mcslee commented 1 year ago

Re-titling and re-opening this for the sake of visibility/discoverability on the issues page, since it still seems to impact some people's Ventura installs.

philihp commented 1 year ago

Thanks for that. I also encountered this on Ventura, and the above branch patch resolved the issue.

schott12521 commented 11 months ago

Is there a fix for getting LXStudio-IDE to run on macOS Sonoma? I seem to be getting the same error where the program is running, but there is not a visible window rendered. Processing is setup and working separately.

Edit: I got it to work by updating the Processing lib and adding this same "hack" - https://github.com/heronarts/LXStudio-IDE/pull/3

I can see the UI now at least :)!