@tonfilm Thanks for the input!
I think its loading already compressed, so yes, same issue.
The cache is this DB file mentioned here i guess?
Is it save to delete during runtime? I might try and report, but it seems that this is unrelated to RAM, no?
I tried TextureReader non async in async region and it also introduced a lag somehow.. I asume that receiving those textures async is not possible without a lag.. But just a guess. I havent looked in how to asign it to another thread, is this easy to do?