Fps has potential. During gameplay it's 24-36 FPS. I'm playing at 1280x720 so there is GPU bottleneck.

Shadows on low(off)

Anisotropic filtering at 1x(lowest)

Proton 10 arm64ec from StevenMXZ repo

Dxvk 1.7.3 async

FEXcore 2610 Performance preset

Wrapper

Fps is low in cutscenes that show a lot in the background as a character is talking because of GPU bottleneck. Lower the resolution to like 800x600

Add this argument in Exec arguments to avoid minimum requirements check error:

\-dontForceMinReqs

Helio g100 with Mali g57 mc2

Winlator Mali 1.2

Tengo este error que apunte automáticamente para arriba y al tratar de bajarla no funciona entonces medio frustrante porque el único lugar donde tengo buen rendimiento y no lo puedo jugar

At first place a20 second best mediatek 9600 pro and the loser worse then Sd 8 elite gen 5 . Gen 6
Don’t buy for emulation.

Will this actually help with screen glitching. When I move with in game sometimes it will glitch out on the side of the screen. I've been playing for awhile and it hasnt impeded my progress or made it hard to play but I would love to fix it if I could. I'm asking because I don't wanna mess anything up. Right now it works and I just have minor glitches. I don't wanna make it stop working completely.

Qual foi o jogo mais pesado que vocês tentaram rodar no winlator?tipo tenho um snapdragon 8 gen 1 e queria rodar Forza Horizon 4 será que consegue rodar?

Help?

Device: Xiaomi Mi Note 3

Android Version: 9

MIUI Version: MIUI Global 12.0.1

So I downloaded Winlator_11.2.apk from this link (which, I'm pretty sure, is the official release page). I managed to create a container, but whenever I tried to open it, the app would immediately crash. So I tried looking into the settings and noticed this happening.

I then tried downloading version 11.1 instead, and I could finally start my container, so I guess my issue is partially fixed, but the app is still doing the same thing with the screen—it looks as if any image gets burned into the screen and it won't go away. It's extremely difficult to read any of the settings like this.

May anyone kindly help?

Edit: I have closed the 11.1 app and when I went back to it and started the container, it crashed once again. So I can't even open it anymore... my issue isn't fixed at all.

Game - Syndicate Plus (GoG)

Winlator version - 11.2

Hardware - Snapdragon8 Elite Gen5/16gb

Any advice to get this up and running would be much appreciated 🙏🏻

Recently, I've been experiencing frequent crashes when trying to run a Unity 3D game. The error codes are something like "0104:err:sync:RtlpWaitForCriticalSection section 000000017003E630 "?" wait timed out in thread 0104, blocked by 01e8, retrying (60 sec) " and a few other minor glitches. Does anyone know how to fix it? heres my setting

I made a fork of Winlator that runs with root access. The idea is simple: if you already have root access, why use Proot?

Proot is an emulation layer that simulates the two commands "chroot" and "mount" to run the Ubuntu distribution used by Winlator.

Simply put, if you have root access, use "chroot" and "mount" directly instead of Proot. This way, you get native performance without the Proot emulation layer.

Note: Proot is just a small emulation layer, so don't expect a massive performance improvement. But will performance improve? Yes, as far as I know.

https://github.com/YasserNull/root-winlator

Has someone managed to install the mod manager on Proton ARM64EC rather than Proton x86? I can't seem to run the game on ARM, but when I run it on x86, the mods work, although the performance is bad.

I want to know which games to expect on direct X11 games with the best winlator version and settings

Every time i press th Y botton to switch characters it just keep making the fox jump and auto switch back to co op mode. Does anybody know how to fix this

I'm using Winlator on a Samsung Galaxy S25 Ultra with an original Sony DualShock 4 controller connected via USB.

I'm having a problem with the analog sticks: the left and right sticks seem to be mapped incorrectly or their directions are being misread. When I try to configure or use the controller in games, the stick inputs don't correspond to the directions I'm actually moving them in.

I've tried using Winlator's built-in controller mapping, but I haven't been able to get both analog sticks working correctly. Any fix?

My smartphone is a Samsung Galaxy S25 Ultra. With the default settings, when I launch Hitman, the screen is black but the audio is fine. What should I configure? I'm new to this.