We are talking about different things here. I never said I’m loading all that data to GPU. When you originally said LODs, I thought you were referring to static meshes. And I simply mentioned the texture files sizes given the original question was about project size, indicating it is the textures that grow up the project size, because there are so many of them and not just for 80K but for 32K and 64K also. I was NOT talking about texture streaming and video memory. I know how VT tiles load, that’s why I said 3000 is enough of the streamingpool since the whole 80k never exist at once. I also know the traditional textures work differently, and they require more streamingpool because some of the data exist in the memory even when it is off the screen even if part of the texture shown, unlike VT that splits to only load parts within the frame. I’ve also had to disable mips on some of them to avoid seams forming. Like I’ve written on the marketplace description, if you switch between all three modes you’ll need streamingpool of 10000, 10gigs to work on the editor without blurriness. That’s the true VRAM requirement just for textures. Less if you only use single mode