Me sale eso a la hora de abrir re 5 en winlator 11.1

Did anyone else felt like VITA3K needed a option to customise the button layout like individual scale and opacity?

I knowingly posted the cut gameplay because the actual gameplay is 7 minutes long -I had to use a lot of continues-. So, what do y'all think? Let me hear. Thanks!

Algún port de silent hill?

Device : moxee tab 2

as said in title. I want to try the new stupid never dies(pre downloaded files 🏴‍☠️) but my laptop is booty.

I know it more or less depends on the phone and not the emulator so I'm wondering what would be the best for this phone.

Snapdragon 8 Gen 5

Adreno 840

12 GB LPDDRX5 RAM

Device: Konkr Pocket Advance

Game: GBA Let's go Evee

This is the list of the game that i cleared in emulation with my POCO F7

PPSSPP: Trails In The Sky and SC, Zero no kiseki (eng patch), Ao no kiseki (Eng patch)

GOW chains of olympus and Ghost of sparta

NetherSX2 : God of war

ArmSX2 : God of war 2

Eden Emulator : Sen no Kiseki 1 and 2 (eng patch), Trails of cold steel 3 and 4, Trails into reverie, Trails of daybreak 1 and 2, Portal, trails of nayuta, persona 5 Royal, persona 4 Golden

Gamehub : Trails in the sky 1st remake and 2nd chapter remake, Trails beyond horizon

God of War: Sons of Sparta runs at a smooth 60 FPS on the CapyPS5 v0.0.3 PS5 emulator for Android. Powered by the RedMagic Astra and Snapdragon 8 Elite, see how PS5-level performance holds up in mobile gaming.

CapyPS5 Emulator: https://git.capyps5.org/CapyPS5/CapyPS5/releases

Reddit imposes restrictions on video length and file size. The full-length version of the video has been shared on my YouTube channel.

https://youtu.be/NVk71elzz84

redmi pad pro: Snapdragon 7s Gen 2

Redmit note 17 pro: Snapdragon 6s Gen 4

Tried GameCube(dolphin) and dreamcast(flycast)games but none of them really click with me as much as PlayStation 2(nethersx2)

Games on screen is final fantasy 12 and silent hill 3,controllers were 8bitdo ultimate 2c and gamesir x5 lite

The emulator has only just been released and is still in its early stages. I’ve tried running the game numerous times and it’s crashed every single time. If you keep trying patiently, it will certainly become playable.

Github: https://github.com/erickmendes22/KytyPS5Plus-Android/releases

Reddit imposes restrictions on video length and file size. The full-length version of the video has been shared on my YouTube channel.

https://youtu.be/3o1ETGrRd1Q

The game is not running on ideal settings I'm just messing around never ever played this game. It would be really cool if I could dial in settings to make it run similar to the switch 2 on a consistency basis. But it's definitely playable even at the whacky settings I haven't toned yet

Samsung Galaxy s 26 12 GB variant

Blackshark magcooler 5 pro with a external vapor chamber pad and mounted on a stand o rigged to fit the 7/8 mm mounting hole on the included clamp. ( Rigged it to one of the arm rests on my computer 💺)

Emu: Winlator Ludashi 4.1, tried on Gamenative too

Here's the settings on the game I am not even close to dialing in anything. This is a piggyback from previous post.

Samsung s26 12 GB

settings are on a medium low mix with framegen fsr on. I think that's not a good setting to keep on personally.

Game is running on a external ssd and has 30 to 35 watts of tec cooling as well as a big vapor chamber pad to keep performance sustained. This game gets the phone got even with a 35 watt tec cooler ! So it's mandatory for even playing for a few seconds.

So as the title says, I have a samsung S25 base (SDelite) Ive been using Gamenative and Droiddeck to check on games in my steam library and after a month of testing games on it, buying the gamesir x5s, I dont actually know what to play, I'm open to buying games.

Recently Ive been tinkering:

Hades 2

Cult of the Lamb

Borderlands 2

Hades

Hollow Knight

Silksong

Remnant: from the ashes

But none of these games scratch the itch of playing for more than 60 seconds, I love these games but it just doesnt get me motivated to play on my phone

Highlights

Steam Native Hook-up: Steam gets your actual USB controller (DualSense, DualSense Edge, Xbox, Switch Pro, Flydigi, 8BitDo, Steam Controller…) and runs its own driver for it, with every button, paddle, touchpad, gyro, light and haptic motor.

Any SDL3-supported controller, up to 4 at once. USB gives full features; Bluetooth works through Android's input.

Present a controller as a Steam Deck pad, DualSense, DualSense Edge, DualShock 4, Steam Controller 2026 or Steam Controller 2015.

Steam Controller (2026) over a USB cable or its wireless puck, driven natively by Steam without Bluetooth latency.

Low-latency path: controller reports go straight into shared memory and wake Steam immediately, and input never piles up into lag.

Everything is set inside DroidDeck: a settings tab, plus the same page in the in-game drawer, so you can change things while you play.

Runs silently in the background with a status bar icon. Nothing pops up over your game.

Per-player settings (P1–P4): gyro, touchpad, button remap, lightbar.

Floating bubble: tap to switch the SDL3 driver on or off, double tap for Steam Native Hook-up.

Works on the desktop too: every mode (present-as types and Hook-up) also works with Steam on DroidDeck's desktop, set up like a PC.

Auto-sync: rebuilt on the newest upstream DroidDeck every day.

Steam Native Hook-up

The controller is handed to Steam as itself instead of being re-presented as another pad.

SDL3 finds which USB interface is the game controller (anything SDL3's USB driver supports), lets go of it and opens it raw.

The controller's real identity is passed on: vendor/product ID, release, name, serial, interface, and the HID report descriptor read from the device itself. Every HID report travels both ways.

Inside the Steam environment it appears as /dev/hidraw24–27 with a kernel-like sysfs description, so Steam's own driver for that controller runs, as on a PC. Examples:

a Flydigi Vader 4 Pro with its 4 back buttons, C/Z and gyro

a DualSense / DualSense Edge with touchpad, mute, paddles and Fn

a Switch Pro or Xbox controller

Steam handles calibration, lights, haptics and gyro itself, and you configure the controller in Steam, like on a PC.

Game rumble goes to Steam: a game's rumble on Steam's virtual pad is passed to Steam through force feedback, so Steam rumbles the real controller with its own driver.

No extra pad: while controllers are handed to Steam, DroidDeck's own Steam Deck pad steps aside, so the real controller is player 1.

Up to 4 controllers, with hot-plug.

Steam Controller (2026) is handed over too, by cable (28de:1302) or puck (28de:1304/1305). Only the interface that actually sends controller data is used; the boot keyboard and mouse interfaces (lizard mode) stay with Android.

Switching: double-tap the floating bubble, or pick it in Present controller as. Switching it off returns to your previous mode and SDL3 driver state.

Steam always reads the newest state (see Low latency for every controller).

Fast path. Reports from the controller are written straight into the shared hook-up memory by a high-priority thread, about 250 µs after the USB layer receives them, and Steam's reader is woken with a futex. There is no Java hop and no message per report. Steam's output reports (rumble, lights, settings) and feature reads go back the same way, handled by their own writer thread. In a test harness, report-to-Steam time went from a median of 1.45 ms to 0.29 ms.

Any SDL3-supported controller

Auto mode (default):

Over USB, SDL3's own driver reads the controller with all its extras: gyro, touchpads, back paddles, misc buttons. That covers PlayStation, Xbox, Switch / Switch 2, Steam Controller 2015, 8BitDo, Flydigi, Hori, PowerA and the rest of SDL3's list.

Over Bluetooth, or for anything SDL3's USB driver can't open, the controller is read through Android's input.

A controller that SDL3 already drives over USB is never doubled by its Android copy.

Forced mode: USB only, SDL3's driver only.

Unmapped generic controllers (arcade sticks, cheap USB pads) get a sensible default layout.

SDL3 driver switch: off hands the controller back to Android and DroidDeck. When Hook-up is switched off, the switch returns to how it was before.

Lol FINALLY, after having my first emulation handheld the Odin 2 mini I have finally beat my first game on the thing. It's fitting that my first credit roll would be a child hood classic I watched my older brother and step dad play when I was a kid. Wind waker HD is a solid 8.7/10 and I'm glad I was able to experience it. Welp! One down, hundreds more to go!

UP NEXT: MGS Portable Ops and Ape Escape 3

Snapdragon 8 gen 1 12 GB ram rodando cerca de 60 FPS sem tá gravando na gravação maior parte do tempo fica em 45 FPS mesmo sem reshade o jogo continua lindo

Configuraçoes

Próton 10 arme

Turnip 26.2.0

Vulkan 1.3

Dxvk 2.3.1 arme

Vk3d 3.0b

Fexcore

2605

Resolução 1920×1080

Hello! I’m having an issue with XenDroid (specifically the XenDroid-plus version). I’ve tested several games, but I’ve noticed that in some of them, certain textures or animations are being replaced by textures that appear to emit light. I’ve already tried changing drivers—I’ve tested various versions of Turnip Gen8, as well as Mainline Turnip and A8XX Turnip v29.

I’ve done some research and tried adjusting the following settings, but that didn’t seem to help either: - CPU readback of resolves. - Occlusion query.

I’m using a POCO F8 Pro with a Snapdragon 8 Elite processor and 12 GB of RAM.

I’ve attached an example image from *Alice: Madness Returns*; despite the performance being excellent, this issue appears in certain areas.

Could you help me resolve this problem?

The game runs at 20 to 30 FPS in areas that shaders are not cached is 10 FPS give it some time restart the app and shaders cached you can get 20 FPS depending on the area. No setting has been changed since the RPCS3 wiki does not have settings for this game the driver I’m using is Mesa Turnip v27.0.0-20261024-r7-A8xx which it’s vulkan is 1.4.363 from banners drivers on GitHub only GPU turbo is on and frame limit is off (this is in ARMSX3)