Texture Array vs Texture2D Array

Hi!

I have a lots of textures(40 packs by about 40 items), and Atlas isn’t a solution, so i found two pipeline
selecting group ot textures, create Texture Array, pass it to shader and blueprint

or create array of textures directly inside blueprint, by drag’n’droping a bunch of textures

What approach would be better in terms of performance?
And more important - which one i can automate by Python (built in eu4) scripts!?

Since this is a lot of work, and taking into account iterative nature of workflow - manual approach simply not acceptable.

2 Likes

Creating dynamic instance on tick does not look too healthy, allocating and creating is processes that take longer.

1 Like

thank you for the opinion