Sorry to say this is a duplicate of issue #13973.

@JimScript OK. I didn't see that older post from June 2023. Strangely, the problem exists only when the player can drive the jetski. I looked if the problem is present in Chapter 3 and 13 too but it isn't even there is a lot of water in the levels. I don't know if this extra information would help to solve the issue. I look if the problem also exists when the player drive the jetski in Chapter 12 to Chapter 13. I didn't considered this in my playthrough.

Edit: No. The graphical glitch disappears when the player comes to the starting area of Chapter 13 even when the player drive the jetski from Chapter 12 to Chapter 13. The glitch is gone too when Chapter 13 is selected in the main menu.

So this issue doesn't appear if you "jump" to the target level but it is there when coming in from a different one. This points to a cache corruption/aliasing problem. I'll circle back to this.

So this issue doesn't appear if you "jump" to the target level but it is there when coming in from a different one. This points to a cache corruption/aliasing problem. I'll circle back to this.

I don't have the water issue on Chapter 13 when I select the Chapter directly in the main menu as well as I drive with jetski from Chapter 12 to the area of Chpater 13. For the record, the transition from Chpater 12 to 13 is flurent and there aren't any cutscenes between them.

Here is a video (it was too big to upload this directly):
BCES00065_recording_2024_04_10_22_34_39.zip

By the way, this case can be closed because it's a duplicate.

Sorry to say this is a duplicate of issue #13973.

The original report seems to have vanished, so I'm reopening this

I'm so glad to Duckhost for saving this screenshot (it was from the original report)
This is the build which breaks the water in Uncharted #13901

I confirm the issue on #13901 (build 0.0.27-15047) and it is present only with Vulkan renderer.
It is properly working in OpenGL.

If I disable the custom border color commenting out the line 35 in vkutils/sampler.cpp:

//if (!g_render_device->get_custom_border_color_support())                    // <-- line 35
{
	value = get_closest_border_color_enum(color_value);
	return;
}

the issue is no more present.

I also verified that the broken water effect in Killzone 3 reported in ##15949 is also fixed by the above change in the code.
Below some screenshots of the issue and the temporary fix.

OpenGL - working:

Vulkan - broken - custom border color enabled since #13901:

Vulkan - working - custom border color disabled by temporary fix:

This is a known issue, I honestly just forgot about it.

This is a known issue, I honestly just forgot about it.

For that reason I provided an update (obviously not my intention to bore anyone) reporting a sort of history (for what I see and understand) of the issues and if there could be some relationships with the new/changed features you are periodically implementing/improving that hopefully could help the developers to discover and fix the issues more easily.
I see you have tons of bugs in the list to investigate, so the minimum effort from our (users) side is just to try to help.

If there should be no relationship (interference) between custom border color and SNORM/GAMMA/BX2/UNSIGNED_REMAP (you clarified to me in #15949) hopefully my report above could help.
With current RPCS3 (updated just today), if a disable the custom border color also the issue in Killzone 3 is not present.

No problem, tickets get forgotten about all the time due to the overwhelming number.

With current RPCS3 (updated just today), if a disable the custom border color also the issue in Killzone 3 is not present.

Does killzone 3 also work correctly with OpenGL by default?
Also if possible can you capture a RSX capure of the scene? It would be a great help. The attached trace here is old and also incorrect format.

PS. In this case I mean a capture of uncharted, not killzone.

No problem, tickets get forgotten about all the time due to the overwhelming number.

With current RPCS3 (updated just today), if a disable the custom border color also the issue in Killzone 3 is not present.

Does killzone 3 also work correctly with OpenGL by default? Also if possible can you capture a RSX capure of the scene? It would be a great help. The attached trace here is old and also incorrect format.

PS. In this case I mean a capture of uncharted, not killzone.

I tried also Killzone 3 in OpenGL and there were more issues in general than with Vulkan. I mean the issue on the water was present but there are also other glitches (the water had also a white bloom). I will provide screenshots and RSX captures (possibly in the related bug report #15949 just to avoid confusion with this bug report).

Yes, I got an RSX capture for UC1 yesterday (about 75MB). I will provide the download link here this night (I'm currently at work)

The reason UC1 is failing with border color may be different. In this case it's just because vulkan has some stricter requirements on how border colors must be used that we ignored. That will be fixed soon, but if KZ3 is broken in OpenGL then it could be a different matter altogether. The fact that border color affects it though tells me the remapper pipeline needs to be expanded a little bit, but I need to do the hardware tests to decide the correct texel path which needs time.

Yes, I had also the feeling that the issue in KZ3 still present in OpenGL could (unfortunately) be a different story. Performance in OpenGL for KZ3 are really bad, I mean ultra low performance (just few fps) and I also thought that the issues were due to that, so I didn't consider the result solid enough to be reported. If possible I will also get a recording of that.

@kd-11 attached the RSX capture and a recording for UC1 on Vulkan

Attachments on Vulkan:

RSX capture: https://mega.nz/file/arQSkADQ#OdLx_Qf0QZMvnYV-M1DraC21ThZx9W-hEkdtCxyPnWA

Recording; https://mega.nz/file/G2wmFYDC#2iShGlFGviDNkINWs8RvMH7I1Sne3OCsTGRAaxqZ3_U

#16169 fixes this issue. No idea if it does anything for KZ3 though.

thanks. I will check also in KZ3!

#16169 fixes this issue. No idea if it does anything for KZ3 though.

bug on UC1 fixed. As you already suspected, the issue on KZ3 is a different story and unfortunately it was not fixed by your PR