-
-
Notifications
You must be signed in to change notification settings - Fork 102
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
CrossOver does not show above games in fullscreen mode #1
Comments
This is indeed a big issue for some apps... Give this a look https://github.com/hiitiger/gelectron |
gelectron looks very cool and very similar to what I'm designing, although I'm attempting to make the 'injection' invisible on load and keep this app cross-platform |
|
This may actually be near-impossible for Electron apps without some sort of injection method, and then may be detected by anti-cheat systems. Unless someone wants to investigate using native modules to handle this, it will be a Related: #26 |
Hi! |
This is fixed in the latest version 🙂 |
I am currently using the 1.0.3 and it's not working with the fullscreen of the game Rust :( |
@benjaminaudet What OS? |
Windows 10 |
Yep, unfortunately this is a limitation of Electron, GPU-accelerated programs (especially Vulkan), and probably anti-cheat systems. It sucks but until someone can offer me a valid cross-platform method of getting above fullscreen windows, I don't plan to ever support it (because I am not going to write and support a native extension myself) |
There can't be valid cross-platform method because of specifics of the problem. It's better to start supporting it for one platform with "not implemented" fallback for other platforms. |
Fortnite has updated the way they display as well and is no longer showing in windowed-fullscreen mode either :/ |
I tried to use it for Halo Masterchief collection, but is not working when playing at Fullscreen |
Windows attempts to hide overlays on fullscreen mode, requiring windowed fullscreen to work with CrossOver.
The text was updated successfully, but these errors were encountered: