Refer to the following clip for the symptoms(disregard the trailing noise frames), the defects are usually seen around the protagonist's character sprite, and will be clearly visible in some certain background/scenes:
Are you able to provide a save game for a section that shows the issue
@Blisto91
Are you able to provide a save game for a section that shows the issue
This save file can provide access to reproduce this issue, refer Solution 3: Apply the Save Files We Provide | Save File Restore · 九日 支援 / Nine Sols Support for the instructions.
Reproduce instruction:
I've filed a report to Mesa as well: [[RADV] - Nine Sols(1809540) - Flickering random black rectangle graphic defects appear around protagonist's sprite on AMD graphics systems. (#11404) · Issues · Mesa / mesa · GitLab](https://gitlab.freedesktop.org/mesa/mesa/-/issues/11404#description)
I have not been able to reproduce it on my rdna2 iGPU (or Nvidia RTX 4080) even when using the same mesa and dxvk version. Have this only been observed on rdna3 GPUs?
If this reproduces on Windows even without dxvk then i would say it is a likely game bug
@Blisto91
Have this only been observed on rdna3 GPUs?
As far as I can tell, yes.
If this reproduces on Windows even without dxvk then i would say it is a likely game bug
This issue isn't reproducible on NVIDIA and other graphic hardware, though. I'd rather suspect that it is a bug in the graphics driver/shader compiler etc. I've already filed the issue to the game developers before the release of the game.
Thanks for the info, feel free to close this issue if you believe this is out of scope.
I will take another look when i switch back to my 7900 xtx
This bug is still reproducible in the current build of the game(b7ca1880).
Does RADV_DEBUG=nodcc help (on linux)?
@mbriar
Does
RADV_DEBUG=nodcchelp (on linux)?
Yes! The problem is no longer reproduced after specifying that environment variable in the Steam launch options.
@ewfwefewfw
@brlin-tw Could you share the save file again? This save file seems expired.
The developers seemed to have replaced the save file, please use this one instead:
https://drive.google.com/file/d/1CO_7yxEvQGd4OkYHaJ6V6bZe6Mft2mVu/view?usp=drive_link
It is the After Factory Boss Fight save file in the Save File Restore · 九日 支援 / Nine Sols Support support page.
The game devs have debugged the issue and made the following discoveries:
I've tested the parameters one by one and found that the defect only appears when we set the Unity lightmask rendertexture (format) to a single R channel to reduce memory usage. When I set it back to the default value the defect no longer appears.
When the (render texture) format is set to channel R and (the texture) is thrown into postprocessing the problem resurfaces.
Select the following format will trigger the issue:
R8_UNORM
When I select the
R8G8B8A8_UNORMbelow it the problem is no longer reproduced.
(It seems that I have accidentally reposted this reply, apologies.)
It is known that the Unity SystemInfo.SupportsRenderTextureFormat method call returns true for the R8_UNORM render texture format on RDNA3 systems(e.g. ROG Alloy), so it's not that the graphical driver doesn't support such format.
Closing here since there's a corresponding Mesa issue already and everything is strongly pointing towards a hardware/driver quirk.
proton experimentalx1 2024-06RADV_DEBUG=nodcc`x2 2024-07DXVK_HUDx1 2024-06
Software information
Game: Nine Sols v202406261615.64af447d.0-steam-app-packing/win-production
Graphic settings: Reproduced on 720p, 1080p, and others, with all the combinations of graphic details settings.
System: Framework Laptop 13(AMD 7040 series)@Linux
System information
Apitrace file(s)
https://drive.google.com/file/d/1W7krl7B_QVsnhYDxhbFDODi6B4rj8ZiO/view?usp=sharing
Log files
steam-1809540.log.gz
Additional info
Corresponding Mesa issue: [[RADV] - Nine Sols(1809540) - Flickering random black rectangle graphic defects appear around the protagonist's sprite on AMD graphics systems. (#11404) · Issues · Mesa / mesa · GitLab](https://gitlab.freedesktop.org/mesa/mesa/-/issues/11404)
Some people reproduced this issue without using DXVK on:
So it's probably an even low-level problem.