This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Vulkan errors report
#14
On my GeForce linear tiling prevents texture from using several mipmap level which break almost all 3d games. For some reasons it looks like not all GeForce are affected.
In addition the current implementation always use host visible memory to store data. On Radeon this is fine since device memory is host accessible however on GeForce it's not which means all rendering operation happen in main memory instead of device memory which is bad for performance.

I guess these limitations lead to the upload/default/read back design decision of dx12 ; I'm currently implementing a similar way of doing for Vulkan. While it will add an extra copy operation for Radeon user the texture cache will limit the amount of such copy. On the other hand usage of optimal tiling will increase bandwidth usage for sampling and rendering operation so the benefit are likely to outweighs the drawback performance wise.
If necessary an heuristic could detect which textures are modified per frame and use linear tiling for such texture on Radeon but that's a more long-term idea.
Reply


Messages In This Thread
Vulkan errors report - by Ekaseo - 03-11-2016, 10:34 AM
RE: Vulkan errors report - by tambre - 03-11-2016, 12:28 PM
RE: Vulkan errors report - by Annie - 03-11-2016, 02:11 PM
RE: Vulkan errors report - by Ekaseo - 03-11-2016, 03:17 PM
RE: Vulkan errors report - by tambre - 03-11-2016, 03:24 PM
RE: Vulkan errors report - by Ekaseo - 03-11-2016, 03:37 PM
RE: Vulkan errors report - by tambre - 03-11-2016, 04:08 PM
RE: Vulkan errors report - by Ekaseo - 03-11-2016, 06:30 PM
RE: Vulkan errors report - by cuzudo - 03-11-2016, 08:20 PM
RE: Vulkan errors report - by Yagami Light9 - 03-11-2016, 09:46 PM
RE: Vulkan errors report - by Yagami Light9 - 03-12-2016, 11:25 PM
RE: Vulkan errors report - by Ekaseo - 03-12-2016, 11:42 PM
RE: Vulkan errors report - by cuzudo - 03-13-2016, 12:05 AM
RE: Vulkan errors report - by vlj - 03-16-2016, 01:35 AM
RE: Vulkan errors report - by kd-11 - 03-16-2016, 09:18 AM
RE: Vulkan errors report - by vlj - 03-16-2016, 04:46 PM
RE: Vulkan errors report - by kd-11 - 03-17-2016, 04:18 PM
RE: Vulkan errors report - by AlexVS - 03-16-2016, 06:33 PM
RE: Vulkan errors report - by Annie - 03-16-2016, 07:44 PM
RE: Vulkan errors report - by AlexVS - 03-16-2016, 10:27 PM
RE: Vulkan errors report - by vlj - 03-17-2016, 06:11 PM
RE: Vulkan errors report - by kd-11 - 03-17-2016, 08:46 PM
RE: Vulkan errors report - by AlexVS - 03-24-2016, 12:32 PM
RE: Vulkan errors report - by tambre - 03-24-2016, 01:08 PM
RE: Vulkan errors report - by AlexVS - 03-24-2016, 01:30 PM
RE: Vulkan errors report - by AlexVS - 03-25-2016, 04:18 PM
RE: Vulkan errors report - by vlj - 03-31-2016, 07:30 PM

Forum Jump:


Users browsing this thread: 7 Guest(s)