In 1.5.1, I had around 5-10 FPS. The MagicLauncher stuff I've used before and it doesn't seem to load the shaderpacks. I aahave yet to try to move optifine up. Do you know if Intel i5, 4GB RAM, and Intel HD 4000 512mb will run good?
In 1.5.1, I had around 5-10 FPS. The MagicLauncher stuff I've used before and it doesn't seem to load the shaderpacks. I aahave yet to try to move optifine up. Do you know if Intel i5, 4GB RAM, and Intel HD 4000 512mb will run good?
If You set render distance on tiny and use the lowest shader packs (like KryPPoX or Chocapic13), You'll get about 30-45. I know because I'm using almost same specifications computer like Yours (Intel i5, 8 GB RAM, Intel HD 3000 512 mb).
I keep getting lag. Can someone help me lower it or remove it? Everything work completely fine, but I need the lag removed. I keep ending up breaking two more blocks with my awesome pickaxe. I have low FPS (7-12 fps)
I keep getting lag. Can someone help me lower it or remove it? Everything work completely fine, but I need the lag removed. I keep ending up breaking two more blocks with my awesome pickaxe. I have low FPS (7-12 fps)
Please read all replies I'm repeating:
Always make sure you have the latest drivers (314.22 for Nvidia or for AMD it's 13.4)
There's a few things you can do to speed things up, lowering draw distance and resolution are the two big ones.
The quickest boost to your framerate are draw distance and resolution. Put the game in a window and shrink it until you get the frame rate you want, if the window gets too small, drop the draw distance and then try again.
After that you'll have to start losing the pretties.
You could turn off waving grass, wheat and trees by going into gbuffers_terrain.vsh and putting // in front of #define WAVING_GRASS #define WAVING_WHEAT #define WAVING_LEAVES #define WAVING_FIRE
You can disable POM (parallax occlusion mapping) by putting // in front of #define POM in gbuffers_entities.fsh gbuffers_hand.fsh and gbuffers_terrain.fsh (not really relevant if you're on 1.5.x as there's no normal mapping anyway)
You could lower the shadow render distance in composite.fsh by changing the values of SHADOWDISTANCE and SHADOWHPL (make sure they have the same value)
While you're in composite.fsh you can reduce the shadow resolution by lowering the value of SHADOW_RES
Some people have said that disabling SSAO in composite.fsh helped them a lot, although I only got a couple of extra frames out of it. (you have to comment out // every line with #define SSAO in it)
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Here it is.
If You set render distance on tiny and use the lowest shader packs (like KryPPoX or Chocapic13), You'll get about 30-45. I know because I'm using almost same specifications computer like Yours (Intel i5, 8 GB RAM, Intel HD 3000 512 mb).
Don't know. Maybe first install Optifine, then Shaders mod
It automatically asks me if I wanna close it because there was an error.
I waited 20 minutes for it to load but nothing happened.
What error? What the error says?
Thanks.
This file not. This link is for shaders mod 1.5.1: http://goo.gl/4YkdE
If link doesnt work - reply.
Me too...
Please read all replies
Always make sure you have the latest drivers (314.22 for Nvidia or for AMD it's 13.4)
There's a few things you can do to speed things up, lowering draw distance and resolution are the two big ones.
The quickest boost to your framerate are draw distance and resolution. Put the game in a window and shrink it until you get the frame rate you want, if the window gets too small, drop the draw distance and then try again.
After that you'll have to start losing the pretties.
You could turn off waving grass, wheat and trees by going into gbuffers_terrain.vsh and putting // in front of #define WAVING_GRASS #define WAVING_WHEAT #define WAVING_LEAVES #define WAVING_FIRE
You can disable POM (parallax occlusion mapping) by putting // in front of #define POM in gbuffers_entities.fsh gbuffers_hand.fsh and gbuffers_terrain.fsh (not really relevant if you're on 1.5.x as there's no normal mapping anyway)
You could lower the shadow render distance in composite.fsh by changing the values of SHADOWDISTANCE and SHADOWHPL (make sure they have the same value)
While you're in composite.fsh you can reduce the shadow resolution by lowering the value of SHADOW_RES
Some people have said that disabling SSAO in composite.fsh helped them a lot, although I only got a couple of extra frames out of it. (you have to comment out // every line with #define SSAO in it)