Jakob K

> can you not just do a sibling in the sibling of the sibling and achieve the same thing That would be very very unintuitive. It should be `newLine()` ->...

Das ist kein Render"bug", es ist Teil der Performance Improvements von Optifine.

Hasn't the linked issue been caused by multiple threads being used for the *same* scene due to `Dispatchers.Unconfined` being the default context for `ImageComposeScene`? If yes, then this is not...

I have been using multiple scenes for a server-side GUI, where the server handles multiple users at once. The performance degraded severely now that everything has to use `MainUIDispatcher`.

Yes, I tried that as well - it results in the same deadlock between that single-thread and the AWT event queue.

Also, does this mean that using Compose to render into GLFW windows (for example using LWJGL) is unsupported now as well? (you have to use the glfw thread there, which...

The LWJGL thing mentioned in my last comment is something different though, no concurrent use of `ComposeScene`s, still not possible anymore due to the newly introduced requirement for `MainUIDispatcher`. Is...

In all shared code snippets in the linked issue there are always thousand concurrent scenes started on different threads. I am not sure how one scene on a single thread...

But I am not talking about multiple instances right now. Only a single scene, a single application, a single thread - so only one instance. The main issue is that...

Also, this is not an upstream issue, since upstream does not work with the AWT event queue and therefore cannot be the reason why it is required (except if somewhere...