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

Ratchet & Clank: Rift Apart - some textures aren't streamed in high resolution #1936

Closed aufkrawall closed 4 months ago

aufkrawall commented 6 months ago

What looks to be like decals may appear quite blurry, e.g. before the rift to pub/arena in the "Zurkies" level.

Linux VKD3D-Proton + RADV: 1895880_20240310175159_1

Windows D3D12: RiftApart_2024_01_19_17_41_25_268

Software information

Ratchet & Clank: Rift Apart, latest Steam version, 1440p TAA max. settings (RT off).

System information

Log files

Is spammed with stuff like

7395.685:0124:0128:warn:vkd3d-proton:vkd3d_get_image_allocation_info: Padding allocation requirements. Requested alignment 65536 < 262144 (dim 3, 512 x 512 x 1, 7 levels, 1 samples, fmt #62, flags #0).

steam-1895880.log

Blisto91 commented 6 months ago

Sorry yeah I did see your previous message and noted it but haven't gotten to give it a proper deep look yet besides taking a quick peek at the same rubble ingame back then without immediately seeing anything.

doitsujin commented 6 months ago

Probably an issue with VRAM budget reporting as usual, unfortunately we don't really have source access to any of these resource streaming systems to figure out why they are all going horribly wrong. Assuming you're using the same settings on both, there's no reason why texture resolution would be low.

The message spam is benign.

RiantAnda commented 6 months ago

@aufkrawall May be complete nonsense, but did you also check Windows+vkd3d-proton and with/without direct storage on Windows?

aufkrawall commented 6 months ago

When you delete the DS DLLs, it doesn't stream textures in highest resolution on either platform. I haven't checked if they then look exactly the same on Windows D3D12 vs. VKD3D-Proton RADV, but I think it wouldn't be that interesting when the goal is to get the proper resolution on VKD3D with DS.

aufkrawall commented 4 months ago

There apparently was some change in VKD3D-Proton that has fixed it, as the issue is gone with recent build shipped by Proton Experimental or when using vkd3d-proton git-master (With 2.12 DLLs, the issue is still there.): 1895880_20240605195509_1