Glsl odd effects in Yogscast Complete Pack
Glsl odd effects in Yogscast Complete Pack
So here's an interesting one. Being a fan of modpacks, I wanted to play the Yogscast Complete Pack through ATLauncher with a couple friends. That usually works fine, but I have recently fallen in love with custom shader packs. Machine: - i5 2400 @ 3.1GHz stock - Asrock H67M-GE - 12GB of DDR3 RAM, one stick of 4 and one stick of 8 gigs (yes I know, single channel, but shouldn't make much of a difference anyway) - Gigabyte GTX 560TI 1GB @ core 900MHz So, interestingly enough, whenever I load up the Glsl mod in the pack, the framerate is unacceptable, between 1-20 fps. That is even WITHOUT 3rd party shader packs selected in the options. Without the mod this is nearly always 60+. Of course, I was thinking that my system was just plain not powerful enough. But keeping an eye on task manager and GPU-Z, it seems that neither a single core, nor my GPU are 100% loaded at the time of playing. Under 50% to be more precise. Yet when the game is paused, my framerate goes up (duh) but the GPU usage jumps right up to ~90%, which makes more sense if it was the opposite. Also, RAM dedication shouldn't be the problem, since I allocated 6GB to the game, and the javaw.exe responsible for the game never hits more than ~4.5GB. I could understand this situation if it were that the GPU usage when in focus would be 100%, and with the game paused around 30%, but this makes no sense to me. So, has anybody got the slightest clue what's going on?
I can't take or display screenshots directly. However, you can capture the required graphs by checking your system settings or monitoring tools, then share them here for further assistance.
Here are some interesting updates. Apologies, but I wasn't able to capture the temperature screenshots because I was occupied with many other tasks. When I powered on my PC this afternoon, the GTX 560TI started showing more problems, like unexpected artifacts during startup. I replaced the card with an HD 6950 1GB, which only made things worse for the game. Still, I managed to install Optifine, and if anyone notices issues, try using older versions—like D1, which crashes on launch, but C6 seems stable. Shader support is working, though I haven't found any problems yet. With shaders enabled, there are occasional Bad vertexCount errors in the console logs that might need more attention.