search

HansKristian-Work / vkd3d-proton

Fork of VKD3D. Development branches for Proton's Direct3D 12 implementation.
GNU Lesser General Public License v2.1
1.86k stars 194 forks source link

Spider-Man Remastered ray-tracing artifacts. #1895

Open robotman40 opened 7 months ago

robotman40 commented 7 months ago

The game has ray-tracing artifacts that appear on the edges of buildings with ray-tracing enabled. This does not occur when ray tracing is off. The artifacts can be described as being black sharp artifacts and such.

Also, I can confirm it is not a hardware issue since ray-tracing works fine in other games like Forza Horizon 5 with nearly the same performance as Windows.

Software information

Spider-Man Remastered on Steam

System information

Blisto91 commented 7 months ago

Hi there.

Can you provide screenshots so we know what to look for? Also a proton log

robotman40 commented 7 months ago

Hit there.

Can you provide screenshots so we know what to look for? Also a proton log

I will try to get a screenshot later, but it's most noticeable if you go to the tallest building on the south side of the map that is completely glass and run up it vertically.

sonic2kk commented 1 month ago

I believe I am encountering the same bug. I realise this issue report is very old, and my hardware and drivers are different (although I am also using an AMD GPU). Let me know if I should open a separate issue. I have not played this game so I don't know too much context about specific levels or settings.

System Specifications:

Arch Linux does not have Mesa 24.2 available yet, but I will also re-test when this version is available.

I was able to confirm that the problem is specific to enabling raytracing. Disabling raytracing fixes the issue, so it is easy to workaround.

I don't believe this effect to be specific to GPU load, as it can appear when GPU load is at approximately 40% usage on the Main Menu, approximately 70% usage in vents, and approximately 80-90% usage in the first level open tower area.

The effect is mostly present when there are objects with transparency in a scene, such as glass. However this then bleeds over onto the Spider-Man model as well. Strangely, as far as I can tell, most objects are not affected, just objects with transparency and then Spider-Man.

The problem increases and decreases in severity, mostly when panning the camera.

However this effect is not visible all of the time. On the Main Menu it is not visible, but once you enter the game it is visible (at least at the beginning, where my screenshots are from). However once leaving the game and going back to the Main Menu, the bug is present.

As well as this, in certain areas, the problem is either significantly reduced or not present at all. To my eyes it does not look present but I could be wrong. If exiting in an area where the problem is not present, then the problem will not carry over onto the Main Menu. However if exiting in an area where the problem is present, then it will carry over.

Below are some screenshots of the problem at different stages. I tried to capture various levels of intensity, although as the effect does not look as intense in the screenshots.

All screenshots were captured with the game running at close to maximum settings with no upscaling, and no HDR as I do not have a HDR display. While the screenshots were captured at 3840x2160@60Hz, I also tested 1920x1080@60Hz and 1920x1080@165Hz, and they all produced the artifacting. The common denominator appears to be ray tracing.

Screenshots were taken with Steam's screenshot feature using the "Uncompressed" option except where noted otherwise.

Main Menu - No Artifacting

1817070_20240823155152_1

1817070_20240823155156_1

1817070_20240823155207_1

Level Example - Artifacting Present

This is the area in the beginning of the game where the problem is most prevalent. Many apologies but I had to compress these screenshots as they were slightly too large to upload uncompressed.

1817070_20240823153538_1

1817070_20240823153544_1

Main Menu After Experiencing Problem - Artifacting Carried Over

1817070_20240823154514_1

Enclosed Area - Issue Not Present

If exiting from this area, the artifacting above is not present on the Main Menu.

1817070_20240823154314_1

Less Enclosed Area - Artifacting Present But Not Captured

The issue also occurs in the area shown in this screenshot, but I could not capture it. The issue is much more reduced than the main screenshot. I was unable to get this to appear on a screenshot, and I could not return to this area for an additional screenshot. However I am attaching anyway in case the effects present in this area give hints as to the cause of the artifacting.

1817070_20240823153612_1

@robotman40 please let me know if these match the artifacts you are describing. If they are not, many apologies and I can open a separate issue.

sonic2kk commented 1 month ago

I discovered that this appears to be similar to #1191.

Blisto91 commented 1 month ago

I've never been able to reproduce either issue after a lot of trying. But will give it a shot again later.

sonic2kk commented 1 month ago

If there is any further information I can provide, any kind of GPU rendering information, let me know and I can try to provide it. I don't really know anything about how rendering works but if there's a log file I can generate I would be happy to provide such a thing (I realise screenshots and trying to describe where and how a problem occurs in a game can only get you so far, so any concrete technical information I can provide, just let me know :-))

One thing I realised I did not include in my post is that I am using KDE Plasma Wayland 6.1.4, so the game is running via XWayland. Apologies for this omission as this could be significant.

mbriar commented 1 month ago

@sonic2kk are you sure you're not using amdvlk, post vulkaninfo | grep driver. Sorry, but on arch linux i always feel like asking.

sonic2kk commented 1 month ago

Thanks for asking, but I am sure. I don't have amdvlk as far as I'm aware. (EDIT: This sounds rude, apologies, I meant this as a good callout which is why I said thanks, it is a piece of information I didn't think to explicitly call out)

        VK_LUNARG_direct_driver_loading        : extension revision 1
        driverVersion     = 24.1.6 (100667398)
        driverID        = DRIVER_ID_MESA_RADV
        driverName      = radv
        driverInfo      = Mesa 24.1.6-arch1.1
        driverUUID      = 414d442d-4d45-5341-2d44-525600000000
        driverUUID                        = 414d442d-4d45-5341-2d44-525600000000
        driverID                                             = DRIVER_ID_MESA_RADV
        driverName                                           = radv
        driverInfo                                           = Mesa 24.1.6-arch1.1
        VK_KHR_driver_properties                      : extension revision 1

To my understanding the relevant Vulkan packages for amdvlk on Arch are extra/amdvlk and multilib/lib32-amdvlk (for 32bit), and neither of those packages are installed.

sonic2kk commented 1 month ago

I updated to Mesa 24.2.1 today and wanted to update that this issue is still present. If it is a Mesa issue I can report it upstream.

K0bin commented 1 month ago

I discovered that this appears to be similar to https://github.com/HansKristian-Work/vkd3d-proton/issues/1191.

That happens without ray tracing though.

sonic2kk commented 1 month ago

Yes, I was just noting that the effect looks similar. The problem in this issue, at least in the way I am experiencing it (and the way I understand OP to be experiencing it), only happens with raytracing, or at the very least I have been unable to reproduce it in any other way.