Probably referring to what I was talking about. 
Yes I knew about toggling "Load Custom Textures" to test old vs new on the fly. The side effect from prefetching, and what I was talking about on the Xenoblade thread, is that you can't test new texture changes on the fly with it enabled using the method of:
- Have load custom textures enabled
- Save a state
- Overwrite an already loaded texture
- Load state and the new texture is loaded
It only works if the custom texture you are replacing is already loaded and prefetching is disabled, and it's only useful when updating or making changes to a texture. To load new textures on the fly you have to toggle the load custom textures option, the save state trick is just much quicker for testing small changes.
Yes I knew about toggling "Load Custom Textures" to test old vs new on the fly. The side effect from prefetching, and what I was talking about on the Xenoblade thread, is that you can't test new texture changes on the fly with it enabled using the method of:- Have load custom textures enabled
- Save a state
- Overwrite an already loaded texture
- Load state and the new texture is loaded
It only works if the custom texture you are replacing is already loaded and prefetching is disabled, and it's only useful when updating or making changes to a texture. To load new textures on the fly you have to toggle the load custom textures option, the save state trick is just much quicker for testing small changes.