Preparatory Steps
Preliminary steps before configuring Winlator to fix emulator lag
Okay, in these steps, we’re going to create shortcuts for our games to apply individual configurations for each one, rather than a general setup. This is because each game works differently and may require specific settings that others don’t. Keep in mind, this is only necessary for certain tips; others won’t need it.
Once you’ve created your container and opened it, locate your game, press on it, and then touch the screen with two fingers. Select “Create Shortcut.” Close the app, reopen it, and go to the “Shortcut” section. You’ll see your game listed there, and if you tap the three dots next to it, you’ll be able to configure it individually.
Improve loading time in Winlator
This first tip is aimed at improving load times in games. What do we mean by this? Well, starting from Android 9, the operating system introduced a change that reduced the read time for files stored in the memory, specifically in the root folder and its subfolders. As a result, when you open a game and try to load a map or a mission, it might take longer and could even cause a drop in FPS.
How do we fix this? Simply move your games to a folder that doesn’t have this issue. In this case, the folder is located at: `android/data/com.winlator`. You should copy your installed games there.
However, starting from Android 11 and onward, the android/data folders have been restricted. Therefore, we recommend following this tutorial that will teach you how to access them:
Access android/dataWe open Winlator, go to the container, and navigate to drives. Then, we add a new drive and select the Android folder, and click accept. In my case, the path will be as follows, but it may differ for you: /storage/emulated/0/android
Press it to edit, and add /data/com.winlator to the path. It should look something like this:
/storage/emulated/0/android/data/com.winlatorNow, when we open Winlator, we access the new drive with our games inside. Check out the following video to see the results and comparisons.
Improve performance 32-bit games in Winlator
This method really only works for 32-bit PC games or programs, but how do you know which games are 32-bit? The easiest way to tell is if the game is old—typically from 2009 or earlier—or by doing a quick Google search to find out what bit system the game runs on.
Another way to check is if you have Windows 10 or later on a personal PC or laptop. Open the Task Manager, go to the “Details” tab, and you’ll see the programs that are currently running. Start your game and check if it indicates whether it’s 32-bit or 64-bit.
Speeding up these games is straightforward. When setting up your container in Winlator, it’s important not to select all the available cores. Why is this? It’s because these programs typically use only 2 to 4 cores and perhaps 2 threads from the processor. To put it simply, enabling all the cores can actually decrease the game’s FPS. This issue doesn’t occur with 64-bit games, so you should configure it accordingly for those.
Note: There are some games that, even if they are old and 32-bit, make use of all the cores on your phone. You should test them to see which ones are those.
Open Winlator, go to the container settings, then navigate to Advanced and scroll down to Processor Affinity (32-bit apps). Select only the last 3 or 4 CPU cores.
But why shouldn’t we select the first 3 cores? The reason is simple: they are less powerful, and you might notice a drop in FPS. However, by choosing the last 4 cores, you’ll see a significant improvement.
Performance Configuration in Winlator with DXVK
This is more of a recommendation than a simple tip or trick for speeding up the emulator. What you should do is test each DXVK version with your game to determine which one delivers better FPS and fewer graphical glitches or crashes.
For example, in the game Warcraft 3, using DXVK 1.10.3 or 2.3.1 typically yields around 100 FPS. However, with version 2.4, the FPS drops to a stable 50 to 60. Each version of DXVK comes with its own set of advantages and disadvantages, such as unexpected game crashes or, conversely, a smooth experience allowing you to complete the game without issues.
This is something you’ll need to approach through trial and error to find out which version works best for your game.
Remember the previous step. Go to the shortcut of your game, then Settings → DX Wrapper, and choose the DXVK version you want to test.
Using Box64 Preset in Winlator
This can really speed up games, especially older ones, but it’s not the case for all games. Some games created with Unity might require a different configuration in the Box64 Preset.
Remember the previous step. We recommend going to the shortcut of your game, then Settings → Advanced, and setting Box64 Preset to Performance. Launch your game, and if you notice an FPS improvement with no issues and the game runs smoothly, then you can use it. However, if your game doesn’t launch when set to Performance, it’s better to leave it on Intermediate or Compatibility.
Improve stability in games in Winlator
To wrap things up, I’ll share one last tip—not to boost performance, but to make your game more stable during play. Imagine your game is fluctuating between 23 to 29 FPS, but it’s not consistent. In this case, you could limit the game to 20 FPS. However, this is a matter of personal preference. Some people might find it unbearable to play at such a low frame rate, while others might get used to it within the same day. It all depends on what feels right to you.
Take the PSP handheld console as an example—many of its high-quality games ran at 20 FPS, but your eyes would adjust, allowing you to complete the game without any issues.
Similarly, if your game runs between 33 to 45 FPS, it’s better to limit it to 30 FPS. Never limit it to 40, 43, or 50 FPS, as those numbers won’t sync well with your phone’s screen refresh rate, which is typically 60Hz or 120Hz, etc.
Remember the previous step. Go to the shortcut of your game, then Settings → Environment Variables, and set:
dxvk_frame_rate 30
Remember to set the FPS to the desired value for better stability.
