Hi. I just noticed this thread in the wake of the fact that we are hitting what appears to be the same failure after recently updating to 5.3. Although we still have one working branch of our project still on 5.1, updating to 5.3+ is ultimately necessary for another plugin dependency to work properly. The exact callstack looks a little different, but a lot of that has to do with our custom startup procedure and how we initialize nDisplay. Either way, the same Vulkan errors regarding incomplete descriptor state for a UNIFORM_TEXEL_BUFFER and a STORAGE_TEXEL_BUFFER are there, and it ultimately traces to the same Niagara init process, so I’m inclined to believe that it’s the same bug.
Just wanted to know if there was any update on the bug report. We don’t have any really involved use of Niagara just yet (it’s not a pressing concern at the moment), but we very well could in the near future, so disabling it isn’t really the best option. The last hotfix release seems to predate this thread, so I don’t expect it to have anything related. Do you have a link to the report?