@mikan wrote:
When I try to make texture effects an action, it pops it, but then it will freeze when it tries to process the image.
I also have had problems with it where it says it runs out of memory and crashes, which is odd since I have a gtx480 with 1.5gigs and also a gtx460 with 768mb although it might not be able to use my second graphics card.
Anyway, it seems to be a persistant issue on more than just one of my machines, it happens on my system with gtx750ti's too, so there definitely seems to be some sort of bug when its called by actions.
neither of these problems happen when I just call the program normally, it works flawlessly normally.
The way it acts when it's called is strange too, I don't see why it should need to pop the program, just run the filter without popping the interface like every other filter you have does?
Posts: 2
Participants: 2
