I added the corrected comment about Vega to the freeze bugs.

So it's the Nvidia's fault here and no workarounds ?

I suppose part of the problem is in Nvidia blob, but they aren't likely to care about it. But you are free to file the bug to them of course. Unlike Mesa bugs, this process is not public, so you'll never know what they are doing about it, until they'll decide to answer to you if ever.

See here: https://devtalk.nvidia.com/default/topic/522835/linux/if-you-have-a-problem-please-read-this-first/

I suppose part of the problem is in Nvidia blob, but they aren't likely to care about it.

A bit of a curious conclusion seeing that a piece of experimental code is literally the only thing that has problems.

A bit of a curious conclusion seeing that a piece of experimental code is literally the only thing that has problems.

I wouldn't call Wine experimental code. But normally Nvidia care about some big native titles, not about Wine gaming.

If i recall correctly this happens when you copy the 32bit ddls to the x64 bin directory. Make sure you copy the 64-bit dlls ("file xinput1_3.dll" should tell if its the right one.

Not sure if needed here but did you try to copy and override the other xinput dlls as well?

Yes I have the 64-bit dlls (xinput1_3.dll and xinput9_1_0_dll). This used to work with lutris but not if I launch the game from commandline. Actually xinput9_1_0.dll is not needed and doesn't make a difference. And the same xinput1_3.dll works fine with fallout 4.

got some issue here patching wine. I'm almost sure it's an easy fix but lack the time and concentration right now to pin it down.

sh ~/wine-dirs/wine-staging/patches/patchinstall.sh DESTDIR=~/wine-dirs/wine-source/ wined3d-buffer_create
WARNING: Skipping generation of patchlist because 'Staging' patchset is disabled.
Applying /home/thomas/wine-dirs/wine-staging/patches/wined3d-buffer_create/0001-wined3d-Do-not-pin-large-buffers.patch
error: Anwendung des Patches fehlgeschlagen: dlls/wined3d/buffer.c:1455
error: dlls/wined3d/buffer.c: Patch konnte nicht angewendet werden
ERROR: Failed to apply patch, aborting!

got some issue here patching wine. I'm almost sure it's an easy fix but lack the time and concentration right now to pin it down.

Applies fine for me. Make sure your wine source isn't mangled in any way before applying the patch.

Assuming, you used git clone to get the Wine source, go to the source directory, and do this:

git reset --hard HEAD
git clean -df
git checkout master
git pull

Then try applying the patch again. I also recommend running the script from the staging patches directory. May be running it from elsewhere causes a problem.

Thanks that did the trick. Even when i can't tell what was the culprit here.

All i did was cloning the sources and then applying the patches (also tried running from patches directory)



Only wined3d-buffer_create or are there any other important patches at the moment?

Only wined3d-buffer_create or are there any other important patches at the moment?

The other patch you can test is one that fixes distorted monsters, but it's not yet fully correct (causes freezes for Mesa).

See https://bugs.winehq.org/show_bug.cgi?id=43872#c18

Nothing else is needed as far as I know.

Yes I have the 64-bit dlls (xinput1_3.dll and xinput9_1_0_dll). This used to work with lutris but not if I launch the game from commandline. Actually xinput9_1_0.dll is not needed and doesn't make a difference. And the same xinput1_3.dll works fine with fallout 4.

you are right, xinput9_1_0.dll should not be needed.
just tried it with vanilla-wine 2.21, wine-staging-2.21 and my custom build 3.0-rc3 with wined3d-buffer_create patchset applied.

only with wine-staging I was able to start the game with overwritten dll

Yes I have the 64-bit dlls (xinput1_3.dll and xinput9_1_0_dll). This used to work with lutris but not if I launch the game from commandline. Actually xinput9_1_0.dll is not needed and doesn't make a difference. And the same xinput1_3.dll works fine with fallout 4.

if you're patching wine by yourself, you may want give https://github.com/Tetralet/wine-xinput a try. works pretty good for me.

Working like a charm. Thanks ;-)

Does anyone know how to reset an AMD GPU through a kernel variable? I want to test if that can unfreeze the system if TW3 freezes it.

'rmmod' and 'modprobe' should do just that.

I've no idea whether you can force this though while it is in use by X.

The whole point is to be able to do it without losing DE session.

I was experimenting with Ryzen CPU governors to see how it affects TW3 in Wine. Looks like performance one improves it a bit, but not much:

On demand:


Performance:


The change could be just an error margin of changing the camera view slightly, so it's not very conclusive.

That 15% could be because of camera view between two tests. I tried positioning them close, but they could still be a bit different. But I do expect performance governor to improve it somewhat, since the game is CPU bound.

I was experimenting with Ryzen CPU governors to see how it affects TW3 in Wine. Looks like performance one improves it a bit, but not much...

I saw a similar effect here - it does improve performance a bit (~5fps).

Those of you on > 4 core systems try locking W3 down to 4 CPU's e.g.:
taskset -c 0-3 <wine cmd>

That gave me a marked increase in performance (~10fps)!

Those of you on > 4 core systems try locking W3 down to 4 CPU's e.g.:
taskset -c 0-3 <wine cmd>

That gave me a marked increase in performance (~10fps)!

This is less of an issue if you have fast RAM.

This is less of an issue if you have fast RAM.

Well I'm running DDR4-3600...