search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
23.86k stars 1.04k forks source link

Pioneers of Pagonia (2155180) #7339

Open Somamint opened 8 months ago

Somamint commented 8 months ago

Compatibility Report

System Information

Operating System Version: "Pop.OS" (64 bit) GPU: NVIDIA Corporation NVIDIA GeForce RTX 2060
Video driver version: 4.6.0 NVIDIA 545.29.06 Proton version: 8.0-4

I confirm:

Symptoms

The game starts like normal. But once you wanna build something, the game crashes.

Reproduction

  1. Start Pioneers of Pagonia
  2. Start a new map.
  3. Try to build something
  4. Game will crash

--> steam-2155180.log System Information.txt

CubieMedia commented 8 months ago

Same Problem here, also tried with Proton-Experimental.

zocker-160 commented 8 months ago

I am pretty sure this is still the same issue as I have reported some time ago for the demo: https://github.com/HansKristian-Work/vkd3d-proton/issues/1719

It seems that nothing has changed on the game side since then.

monarc99 commented 8 months ago

It works on my Nvidia 1060, but crashes on e.g. Nvidia 2060 and 3060.

Somamint commented 8 months ago

steam-2155180.log new log

racsnet commented 8 months ago

looked a litle closer. (PROTON_LOG=1 VK_INSTANCE_LAYERS=VK_LAYER_KHRONOS_validation VKD3D_CONFIG=vk_debug %command%)

Seems like on crash it throws the following (last line repeats endless)

19274.146:0140:019c:trace:seh:RtlRestoreContext returning to 000000017000F1EA stack 000000002563E3A0
19274.146:0140:019c:err:seh:KiUserCallbackDispatcher ignoring exception
19274.146:0140:019c:err:vkd3d-proton:vkd3d_debug_messenger_callback: Validation Error: [ VUID-VkRenderingInfo-pDepthAttachment-06088 ] Object 0: handle = 0x7fa1500f6990, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0x584a50000002448, type = VK_OBJECT_TYPE_IMAGE_VIEW; Object 2: handle = 0x4f75530000000238, name = Committed Texture (zeroed) (cookie 184), type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0x1a3ac387 | vkCmdBeginRendering(): pRenderingInfo->pDepthAttachment->imageView internal image must have been created with VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BIT. The Vulkan spec states: If pDepthAttachment is not NULL and pDepthAttachment->imageView is not VK_NULL_HANDLE, pDepthAttachment->imageView must have been created with VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BIT (https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/vkspec.html#VUID-VkRenderingInfo-pDepthAttachment-06088)
19274.146:0140:019c:err:vkd3d-proton:vkd3d_debug_messenger_callback: Validation Error: [ VUID-VkImageMemoryBarrier2-oldLayout-01659 ] Object 0: handle = 0x4f75530000000238, name = Committed Texture (zeroed) (cookie 184), type = VK_OBJECT_TYPE_IMAGE; | MessageID = 0x920e207e | vkCmdPipelineBarrier2(): pDependencyInfo->pImageMemoryBarriers[0].oldLayout (VK_IMAGE_LAYOUT_DEPTH_ATTACHMENT_STENCIL_READ_ONLY_OPTIMAL) is not compatible with VkImage 0x4f75530000000238[Committed Texture (zeroed) (cookie 184)] usage flags 0x7. The Vulkan spec states: If srcQueueFamilyIndex and dstQueueFamilyIndex define a queue family ownership transfer or oldLayout and newLayout define an image layout transition, and oldLayout or newLayout is VK_IMAGE_LAYOUT_DEPTH_ATTACHMENT_STENCIL_READ_ONLY_OPTIMAL then image must have been created with VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BIT (https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/vkspec.html#VUID-VkImageMemoryBarrier2-oldLayout-01659)
19274.163:0140:0144:warn:vkd3d-proton:d3d12_fence_set_native_sync_handle_on_completion_explicit: Event completion for native sync handle is already in the list.

and a dmesg shows: NVRM: Xid (PCI:0000:2d:00): 109, pid=437650, name=Pioneers of Pag, Ch 00000076, errorString CTX SWITCH TIMEOUT, Info 0x3c046

maybe related to https://forums.developer.nvidia.com/t/multiple-cuda-rtx-vulkan-application-crashing-with-xid-13-109-errors/235459/221 ?

CubieMedia commented 8 months ago

So it looks like @zocker-160 posted it at the correct address?

Somamint commented 8 months ago

So it looks like @zocker-160 posted it at the correct address?

yes but it got not fixed for everybody.

zocker-160 commented 8 months ago

If I understood this issue correctly, there are actually two separate problems at play here.

One was caused by vkd3d which got fixed (see the linked issue) and the other one reported here is - according to the vkd3d devs - caused by an app bug.

I also have to add, that on devices which don't crash, the performance when placing buildings tanks heavily (from over 60fps to 22fps on the Steam Deck for example), so there is something weird going on.

On other AMD based devices (Vega GPU) the game causes my entire system to hang up.

Somamint commented 8 months ago

If I understood this issue correctly, there are actually two separate problems at play here.

One was caused by vkd3d which got fixed (see the linked issue) and the other one reported here is - according to the vkd3d devs - caused by an app bug.

I also have to add, that on devices which don't crash, the performance when placing buildings tanks heavily (from over 60fps to 22fps on the Steam Deck for example), so there is something weird going on.

On other AMD based devices (Vega GPU) the game causes my entire system to hang up.

so you mean, we can not fix it. The dev need to fix it?

zocker-160 commented 8 months ago

I am just quoting the devs of vkd3d saying that, which to me sounds like they are probably not willing to implement some kind of hack / workaround to make it run.

This however does not mean that no solution exists outside of the game fixing it (which probably won't happen anytime soon given that it is early access).

My hope is that some wine ace like GloriousEggroll might be able to find a fix for this.

Somamint commented 8 months ago

Its just so strange. That you can play on older GPUS so there must be a way to get it work.

u42671 commented 7 months ago

Today's Manjaro updates fixed the crashes/freezes which I experienced before, when building something! I suspect the fix came with the update of Mesa from 23.1 to 23.3.3-1. Maybe also the kernel update from 6.6 to 6.7 is involved.

The game is now running without issues for me with good performance on high graphic settings. I still need Proton Experimental (Some DirectX12 error message when running with Proton 8), but no special commandline settings are required.

Though I'm using a Radeon RX 5700. Any feedback from owners of Nvidia cards, whether Mesa 23.3.3-1 / Kernel 6.7 also fixes this issue for Nvidia?

lindesbs commented 7 months ago

No. Manjaro with actual Mesa 23.3.3.1 and nvidia-545.29.06 (RTX 2070) still hangs

Somamint commented 5 months ago

So any news about this problem, when the game hangs, when you try to build something?

RobertZenz commented 5 months ago

It's still there with Pioneers of Pagonia 0.4.1 (nVidia RTX 3060, 545.29.06), if that is of any help.

Root-Core commented 5 months ago

This still is a problem with Nvidia driver 550.67-6 on Manjaro. PoP Version 0.4.3 / 0.5.0 Beta. The proton log doesn't really help. The only thing that looks strange:

18902.293:0110:0530:warn:vkd3d-proton:d3d12_resource_QueryInterface: {6b3b2502-6e51-45b3-90ee-9884265e8df3} not implemented, returning E_NOINTERFACE.
18902.293:0110:0554:warn:vkd3d-proton:d3d12_resource_QueryInterface: {6b3b2502-6e51-45b3-90ee-9884265e8df3} not implemented, returning E_NOINTERFACE.
18902.293:0110:0558:warn:vkd3d-proton:d3d12_resource_QueryInterface: {6b3b2502-6e51-45b3-90ee-9884265e8df3} not implemented, returning E_NOINTERFACE.
18941.424:0110:0558:warn:vkd3d-proton:d3d12_resource_QueryInterface: {6b3b2502-6e51-45b3-90ee-9884265e8df3} not implemented, returning E_NOINTERFACE.
18941.424:0110:0558:warn:vkd3d-proton:d3d12_resource_QueryInterface: {6b3b2502-6e51-45b3-90ee-9884265e8df3} not implemented, returning E_NOINTERFACE.

It is also present if you launch the app, before you even load a game. So I think it is unrelated.

Matthias-C commented 4 months ago

It's still there with Pioneers of Pagonia 0.5.0-3718+148081 (nVidia RTX 4080, 550.67), if that is of any help.

megian commented 4 months ago

https://github.com/HansKristian-Work/vkd3d-proton/issues/1725#issuecomment-2058452620

RobertZenz commented 4 months ago

A fix for the crashes on NVIDIA GPUs seems to be underway and is currently included in the Vulkan developer beta driver branch, and it will land in the next release according to @esullivan-nvidia:

The issue with Pioneers of Pagonia freezing on NVIDIA GPUs is currently fixed in the Vulkan developer beta driver branch. It will also be fixed in the upcoming release branch drivers, but the developer beta is the the only public release that has the fix for now.

depate commented 2 months ago

Hello!

~I am still experiencing this game crash on AMD based graphics.~

~What is your opinion on the implications on Mesa and AMD Vulkan drivers with respect to the Nvidia fix?~

~Do we have to make mesa or AMD OpenGPU developers aware?~

The issue resolved on my AMD based system using the latest upstream mesa. For more info see this comment.

RobertZenz commented 1 month ago

The crashes with NVIDIA are resolved with the 555 driver (555.42+), for those curios. 555.58 is the latest release of that series as of right now.

torgeros commented 1 month ago

Independently, I was able to run PoP with the latest experimental proton and the 550 driver, even though it used to crash before. I do not know what was updated in the mean time, but my nvidia driver is at 550.

zocker-160 commented 1 month ago

Can confirm, Nvidia 550.90.07 + Proton Experimental works for me on Ubuntu 22.04.