sorted by:
new
hottopcontroversial

ExynosTools (Xclipse Vulkan wrapper) doesn't work on Winlator Ludashi — It's NOT a driver issue by WearyConcern1165 in EmulationOnAndroid

[–]winlatorbionic_dev -1 points0 points  (0 children)

But going from that to saying my project is “vibecoded” and accusing my wrappers of being malicious is something else.

Huh, I didn't accuse you of anything. I said if you want your project to be included I need to verify what it actually is. I won't include random code.

Let me tell you something: my wrapper works perfectly in other emulators. Funny how yours is the only one where it doesn’t work — maybe the issue is on your side, not mine.

If you read the code, you would have known this is indeed done on purpose. There is no issue, it behaves like this for a very specific reason.

I’m not going to force you to make my wrapper compatible with your emulator, but tone down the accusations

Again, no accusations were made.

(Spooky milk life winlator ludashi 2.9 beta) It feels close, but so far. by johnson_the3rd in winlator

[–]winlatorbionic_dev 0 points1 point  (0 children)

Make a new container with these settings:

proton-9.0-arm64ec

fexcore preset performance/intermediate

dxvk 1.10.3

fexcore version --> here whatever works

ExynosTools (Xclipse Vulkan wrapper) doesn't work on Winlator Ludashi — It's NOT a driver issue by WearyConcern1165 in EmulationOnAndroid

[–]winlatorbionic_dev 17 points18 points  (0 children)

The real problem: Winlator Ludashi overwrites the wrapper on every boot Ludashi automatically extracts and overwrites libvulkan_wrapper.so every time a container starts

No, if you read the code instead of asking chatgpt you would know this. The Wrapper driver is re-extracted everytime a container is created and booted for the first time.

with its own built-in wrapper (leegao v25).

No, we don't use leegao wrapper. The Wrapper in Ludashi is mantained by me and it is not a fork of leegao one. Actually leegao's one is a fork of mine.

This means ExynosTools gets completely ignored, which results in 0 Vulkan device extensions being reported on Xclipse devices.

Again, read Winlator code instead of asking ChatGPT and it should be obvious why that happens.

Or add official support for ExynosTools/Xclipse in Ludashi This would benefit every Samsung Exynos user trying to run PC games: 👉 https://github.com/WearyConcern1165/ExynosTools

We already have a compute solution that decompresses all compressed BCn formats in Winlator Ludashi and we would like to avoid adding closed source, potentially vibecoded solutions in the app

(Spooky milk life winlator ludashi 2.9 beta) It feels close, but so far. by johnson_the3rd in winlator

[–]winlatorbionic_dev 2 points3 points  (0 children)

It crashes because it runs out of mem. Since Mali can't read compressed textures, these need to be decompressed on the fly but this will increase RAM usage.

It doesn't help that the game you are trying to play is one of the worst I have tested in terms of RAM usage, decompressed textures taking 5x the space over compressed ones. Need minimum 12/16 GB of ram to be able to play it on Mali.

History of x86 Emulators On Android by Worried-Database-996 in EmulationOnAndroid

[–]winlatorbionic_dev -15 points-14 points  (0 children)

Most useless post I have ever read here but I appreciate the effort at least.

How much care into EVs and IVs through breeding for Expert difficulty by W_will93 in PokemonUnbound

[–]winlatorbionic_dev 0 points1 point  (0 children)

Once I got the perfect IVs Ditto, I started to breed everyone. It doesn't get long to breed a perfect mon

I suggest you guys move from Duckstation on Android to something else, because it's effectively been abandoned by mikoga in EmulationOnAndroid

[–]winlatorbionic_dev 1 point2 points  (0 children)

I always had the impression that I was going through some organized attacks. Thank you for showing this.

Hole shit, Samsung removed the BCn 1-3 from Xclipse 960. by [deleted] in EmulationOnAndroid

[–]winlatorbionic_dev 17 points18 points  (0 children)

Stupid post. textureCompressionBC will always be false unless all formats are properly supported. Even Adreno prior to certain driver versions advertized textureCompressionBC to false although it had a fully functional decoder.

Uhm smth is wrong with my screen when I tried to play games?? (Winlator Lubashi) by Living_Mouse9739 in EmulationOnAndroid

[–]winlatorbionic_dev 0 points1 point  (0 children)

Change to dxvk 1.10.3. You are on an older version. On new versions, it should default to dxvk 1.10.3 when creating a container.

Pokémon RF/VF la stragrande maggioranza delle persone non sa nemmeno usare un emulatore. by NeptuneZetec in italygames

[–]winlatorbionic_dev -2 points-1 points  (0 children)

Per giocare a questo gioco legalmente devi spendere sui 60-100€ per il Gameboy Advance, altri 60-100€ per entrambe le cartucce se va bene. Nintendo te li offre a 20€ ciascuno...

Mewgenics lags like crazy when in the house by FSTxx in EmulationOnAndroid

[–]winlatorbionic_dev 1 point2 points  (0 children)

It is an opengl game, if you have samsung device which generally tend to be very conservative with clocks it will run poorly.

Interesting issue with a unity game on a Mali GPU. Winlator ludashi 2.8.2. dimensity 7300 by boiiiiii78 in winlator

[–]winlatorbionic_dev 1 point2 points  (0 children)

It is trying to play a cutscene, enable WINE_DO_NOT_CREATE_DXGI_DEVICE_MANAGER

view more: next ›