[PATCH 2/2] wined3d: Allow setting the renderer using the WINE_D3D_RENDERER environment variable.

[Zebediah Figura]

On 3/7/22 05:06, Henri Verbeet wrote:
> On Sat, 5 Mar 2022 at 00:39, Zebediah Figura <zfigura at codeweavers.com> wrote:
>> This is significantly more convenient, and scriptable, than modifying the
>> registry.
>>
> I don't mind this, although I think in recent history we've preferred
> to stick with the registry for Wine configuration. It does raise the
> question what's special about the "renderer" setting compared to some
> of the other configuration options we have, other than that it happens
> to affect something currently under active development. Something
> analogous to vkd3d's VKD3D_CONFIG may be nicer in that regard.
> (Although VKD3D_CONFIG exists for very different reasons.)

Nothing's particularly special about the "renderer" setting, except 
perhaps that it's more common to modify nowadays (and less of a 
"workaround" setting than others). But in any case adding a generic 
configuration variable seems reasonable to me as well.

> In terms of scripting though, I've been using "wine reg add ..." and
> "wine reg delete ..." for this as well as other configuration like
> "csmt", "shader_backend" and "MaxVersionGL", and I can't say I've had
> issue with that.

"wine reg add" is scriptable enough, sure; I shouldn't have mentioned 
that. It's still a lot less convenient, though (e.g. harder to remember 
and type, slower due to Wine process overhead...)

For what it's worth, this is a request that came up when some other 
people were testing the Vulkan backend.