Can you provide an apitrace?
The game seems to require geometry shader instancing, which is not implemented yet. Shouldn't be too hard to do, but I'd like to have a test case.
Here is the apitrace:
https://drive.google.com/file/d/123krX7j2IIbkvOqXXsIwobSsRY2DmuwR/view?usp=sharing
Hopefully I made it properly. It's a shame that the game developers are not going to release this game to Linux, considered all their other games have been.
Thanks.
fb11acbc9139ea2567a4b60ff1ea5ff9330c9e8c implements geometry shader instancing. Please let me know if that fixes the crash.
Looking at the trace file, the game may also require DXGI 1.2, which DXVK doesn't support at all yet. This would be the next thing to tackle in order to get it to work, although that's going to be a farily large task.
The errors about the geometry shader instancing are gone, but the game still crashes with "Not Responding"
Here is the wine output:
Frostpunk_wine.log
Here's an initial implementation of the required DXGI 1.2 stuff (in a separate branch for now): https://github.com/doitsujin/dxvk/tree/dxgi1_2
Please test if the game works with that branch. Replaying your trace file does work with those patches.
Progress! I am able to successfully start the game, however the screen is all black and the cursor. I am able to move the cursor and click on menu options, and I can hear menu changing - I just can't see it.
Is it still black if you replay your own trace file with d3dretrace.exe? Because that works for me, although I'm not sure if it's rendering correctly.
Using d3dretrace.exe does appear to work and render correctly.
On 22 May 2018 at 20:39, Philip Rebohle [email protected] wrote:
Is it black if you replay your own trace file with d3dretrace.exe?
Because that works for me, although I'm not sure if it's rendering
correctly.—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/doitsujin/dxvk/issues/385#issuecomment-391174620, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AlrSEyCUCA8sOtYJdO_EpAsZxVOCcw0pks5t1KGsgaJpZM4UH13j
.
To give you an update, the issue is that the game uses D3D9 to render a single frame shortly after starting the game, which implicitly creates an OpenGL context. This prevents the Vulkan swap chain from getting through.
Here's a very dirty workaround for the issue:
dxvk-frostpunk.patch.txt
Not sure if this can be fixed in a proper way.
I came up with a better workaround which is already in the master branch: https://github.com/doitsujin/dxvk/commit/38c5e570257e8cd9dcb78ab227baa2a2c877bd0f
Please let me know if that makes the game work for you.
That workaround works. The graphics appear to render correctly and are
nice and fluid. The only catch now is that ~10-20 seconds after loading a
game my system hard-locks and I have to shutdown by the power button. I
have a feeling that freeze isn't related, but I'll investigate some more
this evening.
On 23 May 2018 at 08:08, Philip Rebohle [email protected] wrote:
I came up with a better workaround, which I pushed to the dxgi1_2 branch:
38c5e57
https://github.com/doitsujin/dxvk/commit/38c5e570257e8cd9dcb78ab227baa2a2c877bd0fPlease let me know if that makes the game work for you.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/doitsujin/dxvk/issues/385#issuecomment-391308819, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AlrSE-OOreKjl5BLM70FkYYRH9h3UUM4ks5t1UNDgaJpZM4UH13j
.
I'm aware of the freeze, it's unrelated. It's likely a driver issue, I'm looking into it.
@rogowskys Using DXVK 0.53, latest mesa-git and llvm-svn, the game runs fine now on my RX 480, no more GPU hangs.
When attempting to start Frostpunk through Steam(which runs ok), the game attempts to start and then crashes immediately.
Software information
Frostpunk V1.0.1 using Steam
System information
Log files
Frostpunk_d3d11.log
Frostpunk_dxgi.log