MIME-Version: 1.0
References: <c07e2e51-5a3f-e0aa-818b-45a8dcf62a90@lywenn.eu.org>
In-Reply-To: <c07e2e51-5a3f-e0aa-818b-45a8dcf62a90@lywenn.eu.org>
From: Leonard Ritter <leonard.ritter@duangle.com>
Date: Mon, 15 Jun 2020 12:44:42 +0200
Message-ID: <CAEjO-TtOoWYY=0T_3DJ60xvAp2O8OyF+TjcmerDWRzbrR7RHKA@mail.gmail.com>
Subject: Re: nvidia optimus support in scopes
To: Daniel Borges <dborges@lywenn.eu.org>
Cc: ~duangle/scopes@lists.sr.ht
Content-Type: text/plain; charset="UTF-8"

Sounds like a good workaround.

Would there anything speak against always linking this symbol into the
executable?

Leonard

On Mon, Jun 15, 2020 at 11:44 AM Daniel Borges <dborges@lywenn.eu.org> wrote:
>
> Hello,
>
> I finally found out why Tukan wasn't running on my laptop. Tukan needs
> OpenGL 4.5 and my laptop's intel GPU only supports up to 4.2.
> Fortunately, my laptop also has an nVidia GPU that supports 4.5. There
> are several ways of making programs use it:
> http://developer.download.nvidia.com/devzone/devcenter/gamegraphics/files/OptimusRenderingPolicies.pdf
>
> I ended up adding the following line to scopes' main.cpp.
>
> extern "C" _declspec(dllexport) DWORD NvOptimusEnablement = 0x00000001;
>
> That probably isn't the best solution though but considering the dynamic
> nature of scopes, I don't really know how to handle this.
>
> One thing I noticed though is that, contrary to what states the above
> link, the value of NvOptimusEnablement doesn't matter. Even if it's
> zero, the GPU will be used. So it's value can't be used to
> enable/disable the feature...
>
> Regards,
>
> --
> Daniel Borges
> Game Developer
> +33 6 11 92 32 84
> http://pawarumi.com