Originally Posted by semlar
The beta client doesn't seem to be using the existing copy of the texture that's been loaded into memory and is creating a new copy of it every time the texture is set.
I'm not sure if it can't tell that the textures are the same because of what they did to texture paths, but I don't think this is intentional because loading new textures is extremely slow compared to reusing the copy in memory.
|
Did a test on this and yeah, it's reading the texture from the hard drive each time SetTexture() is called.
I don't believe this will be up for the release.
Hey @MunkDev, thank you for the tips.