Currently, jME relies by default on a small AWT launcher to configure some basic settings. In theory, it is fully optional, but in practice jME does not start with very sensible defaults, so it is effectively required, especially for examples.
AWT is still tied to X11, which means it requires the X11 compatibility layer for an engine that would otherwise be Wayland-native. The AWT event loop is also known to cause issues on macOS when used together with GLFW.
I propose changing the engine defaults to make the AWT launcher less essential.
- Frequency: 0 (auto)
- Width: 1440
- Height: 900
- Samples: 4
- Resizable: true
Currently, jME relies by default on a small AWT launcher to configure some basic settings. In theory, it is fully optional, but in practice jME does not start with very sensible defaults, so it is effectively required, especially for examples.
AWT is still tied to X11, which means it requires the X11 compatibility layer for an engine that would otherwise be Wayland-native. The AWT event loop is also known to cause issues on macOS when used together with GLFW.
I propose changing the engine defaults to make the AWT launcher less essential.