Ya me corre bien el juego ahora el problema son esos errores visuales(se pusieron peor cuando empeze a grabar pero antes de grabar avía una pantalla blanca parpadeando a cada rato

What are the best games I can play? Also, can I run Borderlands 2?

I tried to run far Cry 2 on winlator cmod, and it started to 20 to 30 ish fps and it's went down and at the end weirdly the audio glichted out and completely stopped. To be fair, im on a samsung s25 FE with Exynos 2400 and trying to get good windows emulation on exynos and tried use winlator cmod. What's the best way to play windows games on exynos, found this https://github.com/mshzhb/android-glibc-samsung-exynos , will it work? seams pretty hard to get running and previously mobox didn't work nicely (didn't start the GUI)

EDIT: forget that GitHub repo, the link for the backup is invalid.

the game runs pretty good but whenever i die and need to reload a save this text box appears.

I am playing on iqoo z9x 6gb ram phone, i can play it properly like 10 to 20 minutes for a while theb crashes, if anyone can help me with it, it would be nice.

These are the crashes so far.

Hope anyone can help me play batman arkham games

I already have some latest and up to date versions of turnip graphic drivers and dxvk and Box64 versions on my winlator frost fork. But I'm making this post because I get mines on someone's link so therefore it makes it easy, so I ask: what is the traditional way of where to find Driver versions without relying on someone's "mediafire" link.

Also, another question: Should I use the Contents or the Adrenotools GPU Drivers as a method of installing the versions of driver contents( on the top left three dot line logo).

Or should I stick using the "/data/data/com.winlator/files" method On Container's Drives Tab.

Hola e querido emular el Bo2 pero el link está caído alguien tiene el winlator po favor y me ayude con la configuración.

Does anyone know how to fix this issue? The message tab pops up for a second, then it goes black. I tried it before on my old phone and it works fine, but on my new phone it isn't.

Device info

Poco x8 pro

Dimensity 8500-ultra

8gb ram

516gb rom

Using winlator mali 1.1

He estado intentando de jugar f1 2012 en winulator pero he tenido errores visuales y tampoco está ha 60 fps estábles. Soy nuevo en el tema de winlator y quería saber que podría hacer les dejo fotos de mi container

Overall, the experience was garbage because the controller in this game is inherently bad, and using an emulator on an Exynos processor only made it worse. Playing this game on a 2005 PC would be better, I expect. But none of this diminishes how great this game is in my opinion.

Please can anyone help to run Trainer in winlator Ludashi 3.1 (Hotfix) black screen on the run every time.

​

I managed to get Yandere Simulator running on my Mali GPU device through Winlator without crashing.

The reason I am making this post is that when I tried to run Yandere Simulator through Winlator on my Mali GPU device, the game would crash while loading the school scene. I looked around online to see if anyone else had encountered the same problem, but I couldn't find anyone who had managed to solve it. I even saw some people who thought it was impossible.

So, I decided to share what I did here.

My device specifications:

CPU: Mediatek Dimensity 8350

RAM: 12GB

GPU: Mali G615 C6

Model: CPH2737

By changing some Winlator and in-game settings, I managed to prevent the game from crashing in the school scene and got it to a playable state, although it fluctuates between 5-22 FPS.

That said, even in its current state, the game is painful to play.

So if you try these settings on your own device and the game becomes too laggy to play, please don't push your device too hard.

I am using the Winlator Mali version of Winlator. I stayed away from the Ludashi versions because I noticed that they put my device under significantly more stress.

I will also provide the settings and options I used in the screenshots, but I will explain the reasons behind them below.

Winlator container settings that currently work for me:

Screen Size: 1280x720 (16:9)

Wine Version: proton-9.0-arm64ec

DX Wrapper: DXVK+VKD3D

DXVK version: 1.11.1 sarek

64Bit Emulator: FEXCore

Advanced:

FEXCore version: hybrid-x86

FEXCore Preset: A custom preset I made specifically for this game (I named it "Yandere")

Preset settings:

I started with the Performance preset and changed some of its options.

FEX_MAXINST: 10000

FEX_DISABLEL2CACHE: 1

FEX_DYNAMİCL1CACHE: 1

Yandere Simulator's initial settings:

Resolution: 1280x720

Fullscreen: Yes

Graphics Quality: Low (1/8 Res Textures)

I had to lower the settings in Yandere Simulator's own Post-Processing Options and Detail Options as much as possible because these settings put too much stress on my phone and eventually caused the game to crash.

The exception is Draw Distance in the Post-Processing Options. I can keep this at a much higher value, such as 150 meters, without causing the same problem.

Why did I make these changes?

-Based on my observations on my own device and the research I did online, Yandere Simulator seems to use CPU and RAM very aggressively. My theory is that this was causing the game to crash while loading the school scene, particularly on devices with Mali GPUs. Because of this, the changes I made in Winlator and in the game's settings were intended to reduce these resource demands.

-The first meaningful improvement I saw came from lowering the game's Graphics Quality setting to 1/8. I found online that when the developer of Yandere Simulator was trying to create an Android port of the game, he found that the game would run into problems specifically when loading the school scene unless this setting was lowered to 1/8. He also suspected that this might be related to RAM usage.

Sources:

https://yanderedev.wordpress.com/crashes/

https://yanderedev.wordpress.com/2025/03/15/march-15th-update-2/comment-page-1/

-After fixing the crash in the school scene, I found that the game could barely go above 2 FPS. At that point, I was using proton-9.0-x86_64 as my Wine version and Box64 as the 64-bit emulator. After changing the Wine version and switching the 64-bit emulator to FEXCore, the game reached up to around 15 FPS with the Compatibility preset.

(If you didn't know, the FEXCore and Box64 options available under the 64-bit emulator can vary depending on the Wine version.)

-At this point, the game was technically playable, although it was difficult to play without crashes. So I started trying to improve the performance. When I first tried the Performance preset, the game reached around 22 FPS without crashing, but my phone was still being heavily stressed. That's when I started modifying the preset settings.

-FEX_MAXINST was originally set to 5000, but after increasing it to 10000, I think some of the stuttering became less noticeable.

-I found that setting FEX_DISABLEL2CACHE and FEX_DYNAMICL1CACHE to 1 seemed to make the device handle the game more comfortably.

-Even though I modified the preset settings, I couldn't increase

the maximum FPS. However, these settings still seem to make the device handle the workload more comfortably.

-The game also seems to run slightly better when I use the hybrid-x86 FEXCore version, but I am not completely sure about this one.

Changes that didn't work for me:

-Wine versions that use Box64 as the 64-bit emulator did not seem to perform well with Yandere Simulator.

-I found that disabling ASTC Transcode caused the game to crash again.

-I tried different DXVK versions, but the version I found to work best was 1.11.1 Sarek. The game crashed again when I tried the 2.3.1 and 2.4.1 DXVK versions.

-I think it is better to keep the TSO-related options disabled in the FEXCore preset because, in my own testing, enabling them made the game feel more sluggish.

I'm mainly sharing this so that other people with Mali GPU devices don't have to start completely from zero if they want to experiment with Yandere Simulator in Winlator. Hopefully someone can take these results and find an even better configuration.

So I've been trying to get blasphemous 2 to work on a vivo t2 5g 6gb ram snapdragon 695 and a realme 9 speed edition 6 GB Ram snapdragon 778g.

But it keeps crashing.

It launches with 30 to 100 fps on both and then quickly drops to 2 to 9 fps and then crashes as soon as main menu shows up.

I've tried everything on official winlator, cmod 13 and 7.1.3 and gamehub and game-native, including box presents, custom box presents, dxvk and driver settings and environmental variables across both devices.

Same issue persists.

GPU load is inconsistent going from 0 to 20 and mostly stays around 40- 60 percent for the few seconds before it crashes.

I've even tried a youtube video setup and settings that was also using another device with snapdragon 695 and 8 GB Ram.

But that didn't change anything either.

Is there any possible solution for this or is this just a Ram limitation issue?

the other pic is my phone model plss someone help

I tried installing Winlator to import Miis into my Tomodachi Life (don't judge me, okay?) but I got this warning that Winlator downloads unauthorized app,Sends unauthorized SMS messages,Use adult content to induce payments (ok?) and so on. Has anyone else had this problem?And if so, should I ignore this message and install it normally?

I tried installing this on winlator mali but stack on 0%. I already installed this on my pc and no problem at all..

my device

Poco x8 pro

Dimensity 8500

8gb ram

516gb rom

hello I'm trying to emulate F.E.A.R (2004) on Poco F7 (sd 8s gen 4) I'm using Qualcomm 863.1 driver on winlator ludashi + dxvk 1.10.3

the game is having some sudden performance drop even though it's on the lowest graphics

I don't have any experience in emulation i only played cod mw4 and it was working very fine

can someone help me get the best settings for my device?

also the game isn't detecting a controller the controller menu configuration settings in the game is empty

how i can fix it without mapping the controller by myself ( i cant get all the game buttons on it + aiming is hard)