From: Henri Verbeet Subject: Re: [PATCH 5/5] winevulkan: Add executable name Quirk regkey handling Message-Id: Date: Tue, 15 Sep 2020 17:03:09 +0430 In-Reply-To: <83cab73b-1b69-92af-2ff1-a8ca3c9878f0@nvidia.com> References: <20200914123146.12912-1-lmiddlebrook@nvidia.com> <20200914123146.12912-5-lmiddlebrook@nvidia.com> <87bli7iiiq.fsf@wine> <83cab73b-1b69-92af-2ff1-a8ca3c9878f0@nvidia.com> On Tue, 15 Sep 2020 at 16:13, Liam Middlebrook wrote: > Additionally, this information is already being used within WineVulkan > to match the idTech engine [2]. There are also a few different Vulkan > driver implementations [3], [4], [5], which use this for enabling > per-application/per-engine settings. > Incidentally, I absolutely *hate* drivers that do this kind of thing, particularly the overly broad variants like the "vkd3d" example in [4] above, or the simply *broken* variants like [6]/[7] where the default configuration is broken to work around an application bug in a non-default configuration. Back on-topic though—and I think what Alexandre was referring to—do we really think there's a case in practice for users to apply quirks based on e.g. the internal engine name, instead of simply the executable name? [6] https://bugs.winehq.org/show_bug.cgi?id=48818 [7] https://bugs.freedesktop.org/show_bug.cgi?id=110462