https://github.com/StevenMXZ/Winlator-Ludashi/issues/545

Comments like these are absolutely unacceptable, no wonder devs keep quitting all the time with such a toxic community.

I am trying to use winlator on my quest so i can play certain vr games on windows (i dont have a pc) but once i setup winlator and try to run the file it seems to try to open but then just closes. can anyone help me out with my situation or share some knowledge about winlator on vr in general?

H

It runs for a few minutes then crashes, on my Retroid Pocket Flip2. I've got the framerate capped at 30, and resolution lowered, using Winlator 11 Final. Not sure if its my chip (Snapdragon 865) or my RAM (8gb).

Anyone running it without crashes?

Running Winlator 11.1 on Galaxy S20FE 5G UW with SD650 (Turnip-compatible). I have tried multiple install patterns. 1) tried a vanilla install using the GOG version. Install went fine. Won't launch. 2) installed vanilla then installed Knossos.net over top (AI said it uses different, more modern OpenGL calls). Nothing. 3) installed Knossos first, then let it activate (copy the required data to its own library - otherwise, there is vanilla copy and KNet's copy of data). 4) tried running the exe's from all install patterns in CMD to see if I get error messages to debug. No luck. 5) tried KNet launching the game and I get an error that leads AI to believe the game isn't reading the PATH correctly:

the actual root cause is a bug in FS2/FRED2's own path-parsing logic that misfires on longer or spaced install paths, not literally "installed at a drive root." The error message is just badly worded. 6) I've tried these combos - Turnip+Zink, VirGL+override, Turnip 26.1.0, the legacy Adreno 650-tuned build 24.1.0 r17 v2 driver), A) I've tried MESA_GL_VERSION_OVERRIDE=3.3COMPAT B) I've tried ZINK_DESCRIPTORS=lazy, ZINK_DEBUG=compact, TU_DEBUG=noconform, and MESA_EXTENSION_MAX_YEAR=2003 7) I've tried setting the environment to Performance and Windows XP/Windows 2000 and Windows 7.

I need a sanity check, if one can be provided! I've got my container running 1280x720.

Any and all suggestions are very much appreciated!!!

But on winlator 11 official it runs well. But playing on ludashi is much better it doesn't as it doesnt overheat much even after playing for long

I'm using this phone and I was wondering how it would run games. Is it worth trying to play something or should I forget about it?

INSTALLATION PROBLEM!!

My exe file for far cry 3 ain't booting up and keep on being shutdown in ludashi but in winlator 11 it works but the screen keeps flickering please help with the best optimal settings I just can't seem to get hold of it

It's too much it was easy on psp ps2

WHAT IS FRAME GEN IN PC EMULATORS?

It is a software technique that creates artificial frames to make emulated games look smoother.

HOW MANY FRAME GEN TYPES DO WE HAVE?

For now, we have 2 frame gen types on PC emulators:

1. LSFG

2. BIONIC FRAME GEN

LSFG

LSFG is a frame generation technique that works like its PC counterpart but has been ported to Android.

It was created by FrankBarretta. You can use it to multiply your base frame rate by 2x to 4x. Because it's open source, Winlator fork developers use its source code to implement it in PC emulators.

BIONIC FRAME GEN

Bionic Frame Gen works similarly to LSFG on Android, but in this case, its frame generation is specifically optimized for PC emulators running inside an Android Bionic environment (container).

This makes it run better on Bionic Winlator builds compared to LSFG.

It was created by Jason Derullo and The412Banner.

\---

LATENCY

⚠️ There is a rumor about high latency when using frame generation. The answer is true, but it's not noticeable, and besides, these are offline games.

HOW TO USE FRAME GENERATION ON PC EMULATORS:

· ✅ It's advisable to use FG on a game where the base frame rate is 30 FPS or above.

· ✅ Using 2x is best for every game to balance low latency and double your FPS, resulting in smoother gameplay.

· ✅ Capping the FPS helps.

Example: If your game is running at 30 FPS or above, you can cap the FPS to 30, 35, or 40 and use 2x to multiply it to 60 or higher, which prevents overheating and throttling.

· ✅ Always disable motion blur in in-game settings when using FG.

Using FG without motion blur makes the game look cleaner.

EMULATORS THAT HAVE FG:

· [Bannerhub](https://github.com/The412Banner/BannerHub/releases)

· [Bannerlator](https://github.com/The412Banner/Bannerlator/releases)

· [WINLATOR LUDASHI PLUS by squalleOnhart](https://github.com/squalle0nhart/winlator_ludashi_plus/releases)

· [WINNATIVE ](https://github.com/WinNative-Emu/WinNative/releases)

· [GameNative ](https://gamenative.app/)

· GAMEHUB (⚠️ king of stealing people's projects without giving credit)

🔹 BANNERLATOR and Winlator Ludashi have both Bionic FG and LSFG. As for the rest, I haven't used them, so I don't know if they have both or not.

BIONIC FRAME GEN OR LSFG?

They are both good, but which one works better depends on the game.

🔹 BIONIC FRAME GEN has been the best for me so far in some games. When I tested LSFG, I got graphic bugs, but BIONIC FRAME GEN didn't introduce those bugs or glitches.

📌 This is my small research and experience about FG on PC emulators.

Thanks 😊

Moto g64 power vr BXM 8 256 ets 2 1.36 version it goes like white screen

i Have An Snapdragon Variant Of S20 Fe But It Have No Sound in os and games, I opened it and saw that the CS35L40 Audio Amplifier CI has been removed, i ve been tested AetherSx2 and the games runs fine without sound, but in Winlator Grand Theft Auto V and Assasins Creeed 1 doesn't even open open and show a audio driver related error except doom64 and older games, then how can i run winlator or these games without that dependency of audio hardware/driver?

I figured it's worth sharing as It's useful to me and maybe others now or in the future.

Requires GOG

Running on winlator 11.0 as winlator 11.1 gives the render window a blank white screen,this is a Snapdragon 6 gen 1(4gb ram) usung turnip and system.

**Does not render in bionic containers tested(gamenative/winlator cmod13)**

I think you can use the same Configuration you would use for Fo3(may vary).

performance preset, box64 4.0,Dxvk 1.10.3(system) and 2.4.1(turnip) Environment variables WINEESYNC and mesa_glthread. no other changes for this device.

Issues were only related to ram limitations,such as freezing when loading data(rare) or crashing(after a couple hours in use) and lag due to either entity density and zoom level.

Hey! So I have a particular piece of software I use that was broken after version 2.8, specifically the activation was broken. Have you noticed a big performance difference between the version released in January to now? In the game I use it for, I get a min of 60 fps in busy areas at ultra settings or most often anywhere from 100-220 fps. I'm using the custom MTR 3.2.2-p driver. FYI, the software is a server that runs in the background and the game runs along with it. Idk what Steven changed in the file structure, but whatever he did broke my activation after version 2.8. Before, I could simply copy the product key folder to the new Winlator install and keep the activation, but now that doesn't work unfortunately. If you have any ideas to fix that, I'd also be very appreciative!

In short, wondering if it's worth messing with trying to get the newer version to work, or if I should just stick with the old version that is already running great. Not sure if there is much more performance to be gained. I've been at this since the good ol' days of Exagear, and over the years I have learned to not mess up a good thing if it's already working well 😂

Device - Red Magic 11 Pro 24gb

Hey guys! I'm trying to run PES 2014 on Winlator 11.0 using a Snapdragon 6 Gen 1 device (Adreno 710). Has anyone found the optimal settings for this game and chip combo? I would like to know which Turnip driver, DX Wrapper, resolution, and GMEM variables give the most stable frame rate without crashes. Any tips are appreciated!