Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trying to build MangoHud for Winlator Glibc. Help needed #1507

Open
coffincolors opened this issue Dec 15, 2024 · 1 comment
Open

Trying to build MangoHud for Winlator Glibc. Help needed #1507

coffincolors opened this issue Dec 15, 2024 · 1 comment

Comments

@coffincolors
Copy link

Describe the bug
When I launch applications that use OpenGL or Vulkan, such as 3D tests like TestD3D.exe, or SphereMap.exe, the resulting window is black and unresponsive.

List relevant hardware/software information

  • Linux Distribution - Cross compiled on Ubuntu Focal Fossa, running on Winlator Cmod with Native Glibc
  • MangoHud version - Modified latest commit with one patch located here: termux/termux-packages@29f15ee
  • GPU - Adreno 750? It's a Galaxy S24 Ultra

To Reproduce
Steps to reproduce the behavior:

  1. Enable MangoHud = 1 in Winlator
  2. Launch any GL application, window is black and frozen

Expected behavior
It runs at all.

Additional context
I've modified cpu.cpp, overlay.cpp, and battery.cpp, and other classes to not use the standard paths for hardware monitor, to bypass any issues related to that. i've also changed the path for sh, to /data/data/com.winlator/files/imagefs/usr/bin/dash due to issues with selinux context on Winlator. I generated a machine-id with uuidgen and placed it in the correct location- i've also implemented missing opcodes in Winlators custom x11 server, 36 and 37 (grab client i think). I compiled vulkaninfo and apitrace for Winlator, but it hasn't proven very useful thus far. Any guidance or any direction to the build that is used in termux would be very helpful. If i can replicate that code and make slight adjustments for winlator that would be ideal. I can provide more notes and steps taken so far. Any insight is genuinely appreciated. The logs themselves are not super helpful after bypassing the file path errors related to power_supply and others like hwmon, proc, sys. I see that text is being rendered supposedly based on the logs, i at least get that far. But otherwise the applications launched with mangohud enabled are black and cannot be clicked.

I guess really, where is the source code for MangoHud used in things like Mobox and DarkOS? Or at least the diff patches that make those function at all.

@coffincolors
Copy link
Author

coffincolors commented Dec 17, 2024

Nevermind I figured it out! check_keybinds was failing in the Winlator environment. I'll need to debug that further but bypassing this allows mangohud to work in Winlator Glibc! Not closing this in case anyone has any interest and suggestions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant