-
-
Notifications
You must be signed in to change notification settings - Fork 461
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
[Fix] Some things missed in the EOS Overlay PR #1563
Conversation
…ents relating to first-time overlay install
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
src/screens/Settings/components/AdvancedSettings/index.tsx
still invokes the isEosOverlayEnabled
IPC call with one empty string (only on Windows, so it doesn't cause any issues, but it's still a little misleading IMO)
Wait a minute. I didn't know that is also in advancded settings? Can we only put it in one of the section for now? |
The advanced settings is where the main "control panel" is, where you can check for overlay updates, install/uninstall the overlay, and (on Windows) enable/disable it globally. You can only en-/disable it globally on Windows, so having a game-specific setting/button doesn't make sense. That's why it's there on Windows, and in the Tools page on Linux |
Ok make sense. From my side this whole thing needs more time and clean up. Better frontend handling (component). dxvk and vdk3d are for example downloaded on startup in the background if i'm correct. why not downloading eos_overlay on startup and add a checkbox to settings for eos like dxvk? |
One simple issue: DXVK and VKD3D are 8 and 2 MB in size respectively. The overlay is ~330MB. We don't just want to reserve 1/3rd of a GB of Hard Drive space for a feature the user might never use/want |
As for
Yes, definitely. I just wanted an initial implementation that's usable, so I don't have to run users through the song-and-dance of running Legendary manually (and don't even get me started on Flatpak permission issues) |
Also true. Still i think as ariel pointed out, we can bundle all the frontend stuff into one component. Maybe in another PR? So would say this is then a good usable starting point and we can final test/review it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this stable enough now. Frontend can be imrpoved in another PR.
TEsting here and it has a bug with the SEttings.
Change to: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good besides the bug I found.
This isn't such a simple fix. The whole "General" settings are not loaded when switching from Game Settings -> General Settings. |
wdym by not loaded? for me they are showing fine. |
It still breaks on specific tabs, but this happens in beta aswell. |
8b97883
to
11c2e1c
Compare
Can you check if it still happens on this PR? |
overlay_version.json
isn't present (Legendary only createsoverlay_version.json
if the overlay is installed)Enable
button will now correctly showDisable
(as the overlay is automatically enabled on Windows)Use the following Checklist if you have changed something on the Backend or Frontend: