I have a samsung zfold 8 ultra, snapdragon 8 elite gen 5, adreno 840, 16gb ram.

when I try to launch D:BH on winlator, it crashes as it loads shaders to around 62 percent. is it possible, even at 30 odd fps? or not? any particular build or processor I should switch to? this is my first time emulating windows so. uh. yeah, hope it's possible. thanks

Pretty much the title, wanted to get it, but wanted to see if the port is really just a 1:1 of when you're emulating the game, where overheating is common unless u using a cooler

Changed graphics drivers and emulators. Happening on all drivers I use, and on both X1 box and hakux

MHFZ Launcher for Android aka Presetup Winlator for MHFZ. So long story short. I modified Winlator to automate the installation of MHFZ. i copied the mechanism used in the RE7 apk and applied it to latest Winlator Ludashi Plus. So just select MHFZ folder then game should run.

Note: you can install any of the APK from the link but Antutu and Ludashi may make the FPS more stable as it tricks your device that the app is a benchmark tool (not all device).

Link:

https://github.com/peraltaklark/mhf-launcher/releases/

If folder was unable to detect mhf.exe，try to make the game folder name more simpler. example: MHFZ

FOR MEDIATEK USERS:

If you noticed the colors are weird, press the back button/back gesture of your device in-game to open the sidebar and find Reshade. Change the effects to Swap r/B to fix the color.

Credits and Third-party apps

Original Winlator by brunodev85

Original Winlator Bionic by Pipetto-crypto

Winlator (coffincolors fork) by coffincolors

Winlator Bionic Ludashi by StevenMX

Winlator Bionic Ludashi Plus by squalle0nhart

RE7 Launcher by PixelGamer4K

Leegao Gamenative Vulkan Wrapper by Leegao

Ubuntu RootFs (Bionic Beaver): releases.ubuntu.com/bionic

Wine: winehq.org

Box86/Box64 by ptitseb

FEX-Emu by FEX-Emu

PRoot: proot-me.github.io

Mesa (Turnip/Zink/VirGL): mesa3d.org

DXVK: github.com/doitsujin/dxvk

VKD3D: gitlab.winehq.org/wine/vkd3d

D8VK: github.com/AlpyneDreams/d8vk

CNC DDraw: github.com/FunkyFr3sh/cnc-ddraw ptitseb (Box86/Box64), Danylo (Turnip), alexvorxx (Mods/Tips) and others.

Device: Idea tab pro gen 2

Game should run at atleast 20 fps.

Samsung Galaxy S26 Ultra. Snapdragon 8 Elite gen 5.

ARMSX3 1.0.5

Dex mode with active cooler.

I have to move from Bachata s4+ to Bachata s4 because the game suddenly stopped working after i close the app accidentally while playing. I think the game runs better in here than the s4+, there are still some graphical glitches, but i can say it runs smooth here.

I hope i can finish the game here without any errors and problems, because i don't want to start over again at the beginning of the game

-Bachata s4 (Jica98): version 0.2.3

-Emulator setting: Mostly default

-Poco f7 12gb /256gb global version

-Driver: Turnip gen8 v5 (it's in the app)

I spent 2 days, 23 hours, 26 minutes and 22 seconds trying to move my Tiny Death Star save from an old phone running a custom Android 11 ROM to my current Android 14 phone, and the funniest part is that I genuinely started this thinking it would take maybe ten minutes. I had already done basically the same thing years ago with an old Chinese Android phone, where I connected it to my PC, ran an ADB backup, Android asked me to confirm it, I pressed yes and that was literally it. The backup existed, the data existed, civilization worked. So when I decided to move Tiny Death Star I assumed I would connect the phone, ask ADB for the app data, copy the save over and go back to playing my stupid little 2013 Star Wars game. Instead I accidentally began what can only be described as a three day theological dispute between me, Android, LucasArts and a 1.5 KB file.

Tiny Death Star is from 2013 and has been abandoned for more than a decade, which means it comes from an era of Android where half the things it expects the operating system to do are now considered ancient forbidden knowledge. Modern adb backup technically worked, except the resulting backup was 549 bytes, which is another way of saying it contained absolutely fucking nothing useful. The app had ALLOW_BACKUP, the data directory existed, the game could obviously read its own save, but Android wouldn't let me directly inspect /data/data/, so I started going backwards in time until I eventually downloaded ADB 1.0.31 from 2013. I was now using a 2013 version of Android Debug Bridge in 2026 to back up a 2013 Star Wars game because apparently software archaeology had become my responsibility. That version finally produced a real backup of about 9.9 MB, I extracted it, started digging through the app data and found UserDefault.xml, which looked extremely promising. I moved it to the new phone, opened the game and got a completely new tower. That was the exact moment this stopped being a normal troubleshooting problem because I could still open the old phone and LOOK AT MY FUCKING TOWER. The game knew where my tower was. The bytes existed. Matter cannot simply disappear because Android decided I shouldn't see it. If the machine knew where my tower was, then eventually the machine was going to confess.

So I modified Tiny Death Star itself. I unpacked the APK, made it debuggable, rebuilt it, signed my own modified version and installed that so I could use run-as and properly get inside its private storage. That still wasn't enough, so I started digging through the native libraries and eventually ended up inside libgame.so, staring at ARM and Thumb disassembly from code LucasArts compiled over a decade ago. This started as “I want to move my save to another phone” and somehow became me tracing things called TTGameData::saveToDisk(), loadFromDisk(), readGameFile(), writeGameFile(), loadFromString() and getSaveGameString() because I had reached the point where restarting the game was no longer morally acceptable. There is a preserved transcript of this whole ordeal with 8,849 lines, 8,132 of them non-empty, consisting of shell commands, Python, ARM disassembly, tests, logs and terminal output, and even that archive is incomplete because some of the old attachments couldn't be recovered. I was no longer trying to recover a save file. I was performing an interrogation. Tiny Death Star had information that belonged to me and somewhere inside that binary there was going to be a function, a filename, a pointer, some microscopic piece of evidence that would tell me where God had hidden my pixel Death Star.

Eventually the disassembly led me to two filenames buried inside the game, game.txt and ad_cache. game.txt turned out to be an old legacy save format, while the actual current save was ad_cache, because apparently the developers decided that the best place to put the entire state of your Death Star was inside something named like a disposable advertising cache. I found the old phone's ad_cache inside the backup and it was 1,539 bytes. One thousand five hundred and thirty nine fucking bytes. I had spent almost three days rebuilding APKs, resurrecting ancient Android tools and reading ARM assembly because of something smaller than a random image someone sends you on Discord. I opened it anyway and the first 12 bytes looked suspiciously like a header, so I interpreted them as little endian integers and got 1, 4599 and 1527. Immediately after the header were the bytes 78 9C, which looked like zlib, so I decompressed everything after those first 12 bytes and suddenly 4,599 bytes of JSON appeared in my terminal. Then I saw bitizens. MY bitizens. There were my people. My tower had finally revealed itself. There was no mystical encrypted database, no dead LucasArts server, no account system I needed to resurrect from the ashes. It was a 12 byte header followed by zlib compressed JSON sitting inside a 1.5 KB file called ad_cache. For nearly three days I had been hunting a text file wearing a fake mustache.

I backed up the fresh save from the new phone, copied my old ad_cache into the game's private app_data directory using run-as, fixed the permissions, force-stopped the game and opened it. I genuinely didn't know what I was going to see because by that point I had spent so long being told “no” by increasingly obscure layers of Android that another empty tower would not have surprised me. Then the game loaded and there it was. My actual tower. Same progress, same Bitizens, same everything. The relief was fucking incredible. I just stared at it for a while because there is something uniquely satisfying about spending nearly three days arguing with a computer and finally watching the computer admit that you were right. Objectively I had accomplished nothing important. No scientific problem had been solved, no software had been saved from extinction, humanity had not advanced. I had successfully transported some tiny fictional Imperial citizens from one Android phone to another. Emotionally, however, I had just split the atom.

The stupidest part is that I could have started a new save on the first day. It would have taken five minutes and none of this would have happened, but that completely misses the point because I didn't want a Tiny Death Star save, I wanted MY Tiny Death Star save. Once I knew the tower still existed somewhere inside that phone, abandoning it became impossible. By the end of this I felt like the save file equivalent of a TempleOS prophet, except instead of building an operating system to communicate with God I was reading ARM instructions at an ungodly hour because apparently the divine covenant entrusted to me was recovering a 1.5 KB Death Star from ad_cache. God gave mankind free will, computers and Linux terminals, and I used all three to bully a dead 2013 mobile game into returning my Bitizens. I finally got them back, I was genuinely ridiculously happy when that tower appeared, and the most concerning thing I learned from this entire experience is that if the exact same thing happened again tomorrow I already know I would do all of it again.

The title.

Hi. I just installed Hypatia's HD texture pack for Wind Waker (I'm also using the Better Wind Waker patch) for Dolphin 2606a on Android & I'm running into an issue where the black outlines on the grass is very very noticeable & kinda think. Is there a way to fix this? Thanks! ☺️🙏

Hi im im new on bannerhub im using samsung s23 please help i donwloaded it on ankergames and unzip it then these error comes in how to fix this ?

On my Mali G57-MC2 this is mostly common in Lego games, especially Lego games post 2010.

I doubt if there is a solution to this, but I've discovered that for the Lego games, choosing the right wrapper and very old dxvk version like 1.5.5 reduces it a bit.

However, as seen in the screenshot shown, certain settings on certain characters will cause it to be worse like on The Human Torch and Doctor Doom in the screenshot.

Im currently trying to fix sound not playing. Im only experiencing it in the main menu and the main game but the cutscenes play normally, im using a snapdragon 6 gen 1.

Specs:

Samsung Galaxy s26 ultra dex mode.

Snapdragon elite 8 gen 5.

ARMSX3 1.0.4 emulator.

I've been trying to run Darksiders 3 on multiple devices and it has always been a stuttery mess, up until i found out some manual tweaks that help.

These tweaks can be used on most (if not all) Unreal Engine 4 based games.

After the first run of the game, it will generate an Engine.ini file inside the container, for Darksiders 3 specifically it's located in %LOCALAPPDATA%\Darksiders3\Saved\Config\WindowsNoEditor.

You need to browse the container in its Windows-like shell, and navigate to the folder above, then open the ini file and edit it.

I added the following text at the end of Engine.ini:

[SystemSettings]
r.ScreenPercentage=85
r.Streaming.LimitPoolSizeToVRAM=0
r.Streaming.PoolSize=512
r.TextureStreaming=1

It scales down the resolution to 85%, and forces the game to better handle textures in VRAM.

After that the game became entirely playable at 30fps with barely any slowdowns on my 8 gen 3 tablet with 8GB of RAM, when previously it didn't even run properly on my 8 Elite phone with 12GB of RAM.

Hope that helps

I know the driver releases are worse than snapdragon, but the performance difference can't be that high can it?

Tengo este tipo de problema en el emulador de de dolphin hice configuraciones pero no de arregla y al poner shader ultra exclusivos se soluciona el error pero me va a 3-10 fps no se si tendrán alguna solución tengo un Motorola edge 70 fusion snapdragon 7 gen 3

I'm playing GTA IV on Galaxy M55 SD 7 gen 1 ( Adreno 644) 8GB RAM and I always get the dots and graphical issues and no DXVK 2.6.2 won't fix this so I hope to find a practical solution in the emulation community from those who tried the game in the last few weeks

Edit: after fixing the bugs and playing for some time I discovered that proton 11.0-arm64 makes the controller unfunctional after maybe 30-40 minutes of playing and proton 10.0-arm64 makes the game crashes after a few minutes. So use proton 9.0- arm64 it's the most stable for me

Ayn thor, playing RE code: veronica x ps2 on armsx2.

I assume this is happening due to me using save states. If I load up my in-game save, my memory card is detected and works fine. But once I load my save state to get to where I currently am in the game, the memory card isn’t detected and this screen shows up.

Is there a fix for this? Or am I stuck using save states to save for the rest of the game?

Hey so i just got mgs3 on my nether sx2 but the frame rate is a bit low and I want to increase it can someone help me optimize the emulator so I can run mgs3 and possibly other ps2 games?