[1.5.2] Too many visual effects causing crashes/lag spikes

[MilesTiden]

I recently started a Sawbutcher on Insane in 1.5.2. It had been going very well up until Vor Pride, where I picked up the t5 Steamsaw Artifact Dethzaw. What this does, is it attacks everything around you when you crit, which, considering I have a 100% crit chance, is happening pretty much constantly. It also causes a visual effect to happen, similar to that of Windblade. However, due to my setup, this causes far, far too many visual effects to play whenever I use Rush or Rocket Dash on something. The Rush animation, the Tempest of Metal animation, the Saw Wheels deactivation animation, and god knows how many instances of Dethzaw's animation. This means that every time I Rush, it massively slows my game down. I couldn't get a screenshot because of how my game is set up, but whenever I do it, the entire line from where I Rush to is basically just a blob of animations. Now, I could deal with this, but twice in a row now I have Rushed something, and it crashed my game. My computer is usually able to handle ToME pretty well, but I guess this is just too much for it?

While I'm not entirely sure this is the right place for it, but I figure that triggering the animation multiple times is problematic enough to be labeled a bug. In general, I feel like large, 'on-hit' animations could definitely cause these sorts of problems, though I don't have any other drastic examples like this one, at least since the memory leak problems have passed. Is it possible to get some sort of way to disable on-hit animations through the options, as they aren't affected by any of the video options one would normally use to reduce lag, like particle effects and shaders?

Thank you, and if there's a better place to put this please let me know. I would rather not have to heavily nerf my character because of this.

EDIT: Okay, turns out turning off the basic OpenGL Shader option was enough to solve the problem, it just didn't save/implement my settings right when I was trying that. Problem solved, I guess.