u/mr_worm__z9z

I know I can buy a replacement, but I want to get rid of the drifting problem permanently.

The game concept is great. I hope the developers will create servers for this game because it won't work without them. I wished I could play it when I was little, but I couldn't because I couldn't afford a PS Vita back then.

Without Modders the Vita would be very bitter

​

Gamehub (formerly Gamefusion Emulador, by GameSir/NXTeam Studios, also Eggns)

has a long, documented history of taking open-source code, rebranding it, and taking the credit/selling it, without attribution,with active denial when confronted. This is not a one-time mistake

Case 1: My Vulkan Renderer (StevenMX) + Xlorie ( stole from Termux X11)

I am the developer of Winlator Bionic Ludashi,with have my vulkan renderer backend

Gamehub combined, my Vulkan renderer with the JNI/compositor architecture from Termux-X11 (Lorie) two separate open-source projects, inside their closed source product

Running strings on libxserver.so from the Gamehub APK reveals 4 registered renderer backends:

winemu-xserver / winemu-flip / winemu-vk / lorie-vk

lorie-vk is the Frankstein

The binary also leaks hardcoded build paths from the developer's on a Mac Device:

/Users/me/Documents/WinEmuKernel/lib/src/main/cpp/x11/xserver/dix/events.c

The real internal project is called WinEmuKernel, never disclosed publicly.

the GitHub repo https://github.com/gamesir123/xserver-gf they shared as "proof of independence" did not generate the APK It is a decoy.

The Vulkan strings embedded in their binary match my exact internal abstractions: per-window descriptor sets (e->ds), VkSamplerYcbcrConversion for AHardwareBuffer (e->ycbcr), dedicated cursor descriptor set (g.cursor.ds), and a per-window texture pool with .img / .view / .ds None of this is in their public repo. All of it is in my VulkanRendererContext

Their JNI layer is also a direct copy of Termux-X11's Lorie architecture with renamed functions: rendererSetWindow → updateSurface, lorieActivityConnected → onFirstWindowOpened, and Lorie's single sendMouseEvent(x, y, button, down, relative) broken into three separate functions (mouseMoveBy, mouseMoveTo, mouseClick). Standard X servers don't use shared memory paths (shmPath) this design is specific to Lorie architecture.

Their Community Manager Kael stated publicly: "We have a completely independent X11 renderer… our devs didn't even know anything about Winlator. The binary says otherwise.

Case 2: leegao's BCn compute shaders

Developer leegao (bionic-vulkan-wrapper)

https://github.com/leegao/bionic-vulkan-wrapper

analyzed libGameScopeVK.so from the Gamehub APK and opened

https://github.com/leegao/bionic-vulkan-wrapper/issues/77

concluding he is 95.7% certain Gamehub forked his code:

they also stole some of BrunoSX Vortek (From Winlator official) Work, even before bruno having opened the code

These are not coincidences. You don't accidentally copy someone's debug artifacts.

that's how they got BCn implementation for Non-Adreno Devices

Case 3: The DXMT "DirectX 12" work is AI-generated slop

https://www.reddit.com/r/macgaming/s/1VYncoYmzm

Recently, Gamehub announced their own emulador for Mac, with a DXMT fork with DirectX 12 support, with a contributor named yuemingruoan committing code at

https://github.com/gamesir-labs/dxmt

This was celebrated in communities as a major achievement.

A developer named 3Shain, who works at CodeWeavers on DXMT, reviewed the code and concluded it is AI-generated slopware that will never be accepted upstream. Their analysis:

"Gamehub team shows no understanding of the D3D12 binding and synchronization model. Instead of implementing DX12 natively, they emulate low-level D3D12 features on top of a high-level abstraction designed for D3D11. This wastes large amounts of CPU cycles on every draw call (scanning the rootsig/descriptor heap per drawcall makes no architectural sense), and hits hard dead ends like unbounded descriptors that are simply unimplementable with this approach. In their words: "a real experienced engineer will not even try to implement the thing like that."

This is consistent with everything else: the pattern is not just taking other people's code, it is also shipping AI-generated work as original engineering, while marketing it to users who have no way to tell the difference.

Given all of this, I will give you two alternatives.

1. Give proper credit to the developers whose work you have been using.

2. Make your emulator open source, publish all of Gamehub code and its components on GitHub,with date and commit history preserved, ensure it is compilable.

If this is ignored, that's fine. But know that I will continue working to help this community, and the accusations, not just mine, will not stop. You care about your reputation now. Act like it. we will post more proof if you guys keep denying it and we will make sure this news reaches the China Community