UT99VulkanDrv icon indicating copy to clipboard operation
UT99VulkanDrv copied to clipboard

f5d6b8a Crashes on start with UT 436

Open RGD2 opened this issue 3 years ago • 1 comments
trafficstars

Just pulled down f5d6b8a to have a look.

Built in VS 2019 - with Release configuration, no errors. Copied in VulkanDrv.dll and VulkanDrv.int as directed, set up UnrealTournament.ini also:

On start up there's about one note of music before it crashes with a GPF. History: UVulkanRenderDevice::Unlock <- UViewport::Unlock <- UWindowsViewport::Unlock <- UGameEngine:Draw <- UWindowsViewport::Repaint <- UWindowsClient::Tick <- ClientTick <- UGameEngine::Tick <- UpdateWorld <- MainLoop

Set VkDebug=True and ran again for the log:

UnrealTournament.log

I am running AMD Adrenaline version 22.3.2

Are there any special requirements or missing steps from the README instructions?

I note in the code there seems to be a VulkanDrv.VulkanClient - I tried putting that in for ViewPortManager, but I get the same crash. Only other thing unusal perhaps is that I've got the D3D11 render device also: But when selected, it works.

RGD2 avatar Mar 27 '22 10:03 RGD2

Just gave it a spin in 436 myself and it works here. That's on a Nvidia RTX 3080 card though - I've never actually tested this driver on AMD.

I'm not sure if it helps, but now I've updated the GLSL compiler and the vulkan support libraries to a much newer version. Please note that if you do testing with VkDebug set to true you now need the latest Vulkan SDK (or one within a year) installed or it will not generate any error messages from the validation layer.

About VulkanDrv.VulkanClient that should not be enabled as I never finished it. It was intended to fix some issues with the viewport manager (slow alt-tab, raw mouse input, mouse cursor appearing on alt-tab, etc.) that already got fixed in 469.

In general I really recommend using 469 instead of 436 as it solves more problems than it introduces in my opinion. The HRTFAudio driver in this project also assumes 469 as they made some breaking changes that makes it difficult to support both at the same time.

If you are looking for an alternative to the D3D10/D3D11 drivers, which for me created rather nasty stuttering (the reason I did my own driver in the first place), there's also the OpenGL drivers in 469 that may interest you. :)

dpjudas avatar Mar 27 '22 12:03 dpjudas