mirror of
https://github.com/mumble-voip/mumble.git
synced 2026-03-03 00:46:56 -05:00
Overlay doesn't working with FOnline (OpenGL) under linux #19
Labels
No labels
GlobalShortcuts
Hacktoberfest
accessibility
acl
asio
audio
bonjour
bsd
bug
build
certificate
ci
client
code
documentation
external-bug
feature-request
gRPC
github
good first issue
help wanted
help-needed
ice
installer
linux
macOS
needs-ckeck-with-latest-version
needs-more-input
overlay
positional audio
priority/P0 - Blocker
priority/P1 - Critical
priority/P2 - Important
priority/P3 - Somewhat important
priority/P4 - Low
public-server-registration
qt
recording
release-management
server
stale-no-response
stale-support
support
task
test
theme
translation
triage
ui
windows
wontfix
x64
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/mumble-mumble-voip#19
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mumble-voip on GitHub (Apr 14, 2013).
Hello guys, I've tried to use mumble-overlay in game called FOnline and it seems, that it doesn't working.
Under windows both FOnline.exe (ogl) and FOnlineD3D.exe (dx) are working with overlay, under Linux (Debian Wheezy) native FOnline, FOnline.exe with wine doesn't display overlay and FOnlineD3D.exe shows it.
If it helps, here's sdk repository for that game (giving link to sdk, because it's faster to download than downloading any game made with it)
https://xp-dev.com/svn/fonline_sdk/
This ticket has been migrated from sourceforge. It is thus missing some details like original creator etc.
The original is at https://sourceforge.net/p/mumble/bugs/979/ .
@Krzmbrzl commented on GitHub (Jan 15, 2020):
Does this issue persist in v1.3?
@no-response[bot] commented on GitHub (Feb 15, 2020):
This issue has been automatically closed because there has been no response to our request for more information.
With only the information that is currently in the issue, we don't have enough information to take action.
Please reach out if you have or find the answers we need so that we can investigate further (or if you feel like this issue shouldn't be closed for another reason).