Quack,
I just packaged DXVK 2.0 which brings lots of improvements.
It is the first time since I took over that the requirements were bumped
and the bar is high: Wine 7.1 and Mesa3d 22.0 (minimum version, not
recommended):
https://github.com/doitsujin/dxvk/wiki/Driver-support
With the
Quack,
On 2022-03-11 21:52, Adrian Bunk wrote:
dxvk should have an RC bug documenting why it is not in testing,
and this bug in dxvkshould be fixed by using the non-development
version of wine.
I agree documenting is nice but this is not my decision. It is unlikely
that wine maintainers
On Wed, Mar 09, 2022 at 12:56:39PM +0900, Marc Dequènes (duck) wrote:
> Quack,
>
> Btw, Adrian could you clarify with you bumped the severity?
> wine-development was already blocked from entering Bullseye and that blocked
> dxvk as well, so no need to add a RC bug just for that.
dxvk should have
Quack,
Btw, Adrian could you clarify with you bumped the severity?
wine-development was already blocked from entering Bullseye and that
blocked dxvk as well, so no need to add a RC bug just for that.
Regards.
\_o<
--
Marc Dequènes
Quack,
Could you please test the changes in branch 'br982159' on Salsa and tell
me if it works for you?
Regards.
\_o<
--
Marc Dequènes
Quack,
Sorry for the late reply.
You're right DXVK can now handle wine-stable version (5.0.3). I have not
tested it but upstream claims 3.10 as the minimum version needed.
That still won't let this package into testing though as it is built
against libwine-development-dev that will never
6 matches
Mail list logo
