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

Wrong GPU selected after osu!lazer update #10550

Closed
ghost opened this issue Oct 17, 2020 · 10 comments · Fixed by #28743
Closed

Wrong GPU selected after osu!lazer update #10550

ghost opened this issue Oct 17, 2020 · 10 comments · Fixed by #28743

Comments

@ghost
Copy link

ghost commented Oct 17, 2020

Describe the bug:
I need to manually add osu to the list of programs nvidia will detect in order to run osu on my dedicated gpu (I'm using an old laptop from around 2009).
After updating osu the folder where osu is located has changed because it has the version numbers in it.
Not that it's a big issue but now I have to add the new version to nvidia's list after every update 😄

Screenshots or videos showing encountered issue:
image

osu!lazer version:
2020.1017.0

@bdach
Copy link
Collaborator

bdach commented Oct 17, 2020

I'm half inclined to say this shouldn't be our problem. Unless we change our deployment/update method to not use separate executables for each version I don't know what we could possibly do to convince the vendor software to use the actual graphics card instead of the integrated one.

@ghost

This comment has been minimized.

@bdach
Copy link
Collaborator

bdach commented Oct 18, 2020

As far as I can tell optimus should be forcing high performance if some static libraries are linked, but I don't think we do any static linking. There does seem to possibly be another way but (a) it only works for some driver versions (Release 302 and above) and (b) it's absolutely hideous (source):

extern "C" {
     _declspec(dllexport) DWORD NvOptimusEnablement = 0x00000001;
}

I'm not sure how to even embed that in a .NET Core executable.

The %LocalAppData%/osulazer/osu!.exe path should be a reliable workaround, so I think we should go with that as the official way to make optimus switch to the higher-perf card and not add any ugly workarounds.

@ghost
Copy link
Author

ghost commented Oct 18, 2020

Sorry about that, adding just that path did not work after all.

@Game4all
Copy link
Contributor

This overlaps with / is a dupe of #5582.

@bdach bdach closed this as completed Oct 18, 2020
@smoogipoo
Copy link
Contributor

I wouldn't say this is a dupe really. Also the linked issue needs discussion anyway - I'm not convinced we should be using the dGPU by default anyway - it can, depending on the system and optimisation of the game, actually result in lower frametime/higher latency (see: osu!stable).

I'll keep this open to track the issue of driver configs not persisting across updates, as this is definitely something we'll want to fix regardless.

Maybe something to consider at the point of moving away from Squirrel (if ever).

@smoogipoo smoogipoo reopened this Oct 19, 2020
@KarstenPH

This comment has been minimized.

@smoogipoo
Copy link
Contributor

That is the intended way to use Windows. There's even a GPU setting somewhere in the system settings these days made for this purpose and intended to replace the NVIDIA control panel setting.

@caesay
Copy link

caesay commented Apr 25, 2022

This will be fixed by clowd/Clowd.Squirrel#24

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

Successfully merging a pull request may close this issue.

7 participants
@peppy @caesay @smoogipoo @Game4all @bdach @KarstenPH and others