winebox64/winlator v10.3

Winlator 10.3 (Beta) Early Access

on GitHub

Winlator 10.3 (Beta) WB64 - Updated Features would be:

• Asynchronous pipelining support has been updated.
• HUD scale and opacity options have been added.
• Two new configuration presets are available: Quality-X11 for improved graphics and Performance-X11 for better performance.
• ZINK_DEBUG has been updated with additional options, including gpl and nofbfetch.
• WINE Fsync has been added alongside WINE Esync, resulting in improved performance.
• Zink Descriptors now include a db Descriptor Buffer option to reduce descriptors update overhead.
• Updated Box64 v0.3.3 (Custom) is now available.
• Added DXVK v2.5.3+ has been updated and fixed.
• The loading screen is now way smoother and loads faster!
• Screen size resolution now supports up to 4K+ (4800x2160) in 20:9 aspect ratio.
• Updated FrameRate options now include 5, 10, 15, 20, 25, 30, 35, 40, 55, 60, and many more.
• Bugs from v10.0 are fixed, and the latest DXVK version now works.

Winlator 10.0 (Beta) - What's new?

• Added native GLIBC for better I/O performance
• Minor improvements to Vortek
• Improved internal Registry Editor (Speeds up container startup)
• Added option to open Android browser from Wine
• Added option to use Android clipboard on Wine
• Added option to capture pointer on external mouse
• Added some network stuff on Wine (Fixes some games startup)
• Implemented direct rendering on XServer and Vulkan WSI X11 (Turnip)

⚠️

Results can vary based on the device used, environmental conditions, and other factors, such as simultaneous processing, and different processor capabilities.

*If you experience errors or crashes, try changing DXVK, Graphics driver or Box64.

Why does glibc run slower than Proot on some Android devices?

1. glibc vs. Android’s bionic libc
Android uses bionic libc, which is lightweight and optimized for mobile devices.
Running glibc on Android often requires additional compatibility layers, like proot + glibc rootfs, which might introduce performance overhead.
2. Syscall Translation Overhead
Proot uses syscall translation, which can be slow in general.
However, on Android, some glibc syscalls may not be well-optimized or may rely on emulation layers, making native glibc performance worse.
3. Filesystem Overhead
Proot uses overlay filesystems, which can sometimes optimize game data access.
A direct glibc setup might suffer from filesystem incompatibilities on Android.
4. Memory & CPU Constraints
Android optimizes bionic for low-memory usage.
Running glibc-based games might trigger higher RAM usage, leading to CPU throttling or inefficient memory access.
5. Native vs. Emulated Execution
Proot can sometimes optimize syscall handling by redirecting them efficiently.
glibc-based games might not be fully optimized for Android’s kernel, leading to bottlenecks.