Faster Load?

Oh and also, it reloads the last used texture on load it seems, why not make some cache (i think thats what they are called) type thing so if the texture was loaded in the last session its not re-done untill a new image has been set or another filter selected, only for the main load though.

The main reason of Filter Forge high loading times is almost surely the large amount of filters in your library. We had the same issue like a year ago (only a lot worse, imagine that it was around ... 8-10 times slower), and did a lot of improvements to the process (filter metadata is cached in one separate file, so we don't need to skimp over several thousands files, thumbnails are loaded on-demand and such), but as it seems there is still room for improvement. I will take a peek at this when time permits and _maybe_ will have something for you in one of the future versions.

I checked the related code today, was able to squeeze out around 15% more performance with a quick fix, but otherwise it looks completely solid and I afraid we won't be able to make it any faster unless we change the storage format. There are other options like the suggested "loading" screen (relatively easy to implement, not sure if Vlad would like it though), along with background filter loading (complex stuff, I'm sure we won't work on it even for the 2.0 version), so I doubt there will be significant speed increases in near future. Still, the amount of filters in the library grows, and we might be forced to invent something new for library filters storage, though, which will be a lot faster, but will prevent fiddling with the library filter files by hand (well something should be traded for speed).