also get signs to wave like leaves, no matter what shaders i use
Hmm, that is indeed strange.
This can happen with the 'Jelly Shaders' from Sildur or Beed28, but not typically (well, ok, almost never -- I haven't seen it or really heard about it happening to others and I've been around here for a while) with SEUS or Chocapic or Sildur's Vibrant/Basic.
What video card are you running in your system? Also, do you happen to know which driver version you are running?
The Meaning of Life, the Universe, and Everything.
Location:
Sector ZZ9 Plural Z Alpha
Join Date:
12/3/2009
Posts:
76
Minecraft:
PhaserRave
Member Details
Items held in my hand seem to be translucent when not using a shader (but with this mod installed), and when using a shader, it's both translucent and glowing. I tried systematically removing my mods to find the root of the problem, but I can't pin it down. Has this happened to anyone else?
Edit: It only happened in a single save, too. None of my others. Additionally, when I tried removing this mod, the problem was solved.
This can happen with the 'Jelly Shaders' from Sildur or Beed28, but not typically (well, ok, almost never -- I haven't seen it or really heard about it happening to others and I've been around here for a while) with SEUS or Chocapic or Sildur's Vibrant/Basic.
It's worth noting that signs and chests in my Jelly World shader "bumped" up and down with the players and mobs when they weren't supposed to when the shader was loaded in certain versions of the shaders mod itself, but it's fixed in the latest version.
Hoping I can get some help on optimizing my setup here. I'm using the Direwolf20 FTB pack. When running the game using my 64 x 64 resource pack, I get an average of 120 fps. When using the vanilla textures, it's closer to 180 fps. When running the shaders mod and using NO shaderpacks, my fps plummets with the 64 x 64 Resource Pack. I'm using Minecraft version 1.6.4. FTB uses Forge, and I'm using the correct version of the Shaders Mod afaik. Any suggestions would be amazing. Optifine is a no go, as it doesn't play so well with Forge anymore.
System:
Windows 7 64 bit
12 Gb of Ram
Intel i7 950
Nvidia GeForce GTX 760 4Gb Video Ram (using recommended driver from OP)
Is it possible to install this using MultiMC? I have tried but I am unable to get this working so either I have done something wrong or it's not working
Create an instance, then install the latest/recommended version of Forge (Whatever suits you.) Then add the Shaders core under Loader mods. Add your shaderpack under /instances/[instancename]/minecraft/shaderpacks/
ﯼᵵᴀᵶᵶᴬﯼ'ﺤ SuperShaders V3 full release is now up for download!!!!!!
* All features from ALPHA & BETA ( If you have been following )
* Many versions to choose from inc. Low, Standard and Ultra with MotionBlur & DOF versions
Hoping I can get some help on optimizing my setup here. I'm using the Direwolf20 FTB pack. When running the game using my 64 x 64 resource pack, I get an average of 120 fps. When using the vanilla textures, it's closer to 180 fps. When running the shaders mod and using NO shaderpacks, my fps plummets with the 64 x 64 Resource Pack. I'm using Minecraft version 1.6.4. FTB uses Forge, and I'm using the correct version of the Shaders Mod afaik. Any suggestions would be amazing. Optifine is a no go, as it doesn't play so well with Forge anymore.
System:
Windows 7 64 bit
12 Gb of Ram
Intel i7 950
Nvidia GeForce GTX 760 4Gb Video Ram (using recommended driver from OP)
As a general rule of thumb, running the ShadersMod with no shaderpacks selected causes some pretty strange bugs to occur.
You may not be able to run SEUS v10.1 High/Ultra on that card, but you won't have any problems with Standard or Sildur/Chocapic/MrMeep or the others.
It is very typical to drop FPS from 100-200 to 20 with Shaders because of the way that they run. The shaders are all rendered in real-time, not after the frame is completed, or added as an 'after-effect' like most video games today.
On my 780ti I drop from 200+FPS at 1920x1080 to ~30-40 in SEUS v10.1 Ultra at Far view distance.
So.... Theres a problem with my JVM Arguments. I don't know how to find them to make it help but whenever I load MC the Arguments are AUTO SET to this, even after I delete my entire MC folder. I was using 1.7.2 then when I try to play a different version and try to change the arguments: -Xmx1G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M
So.... Theres a problem with my JVM Arguments. I don't know how to find them to make it help but whenever I load MC the Arguments are AUTO SET to this, even after I delete my entire MC folder. I was using 1.7.2 then when I try to play a different version and try to change the arguments: -Xmx1G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M
I'm Using MultiMC, and my arguments are different, but those seems wayyyy wrong.
So.... Theres a problem with my JVM Arguments. I don't know how to find them to make it help but whenever I load MC the Arguments are AUTO SET to this, even after I delete my entire MC folder. I was using 1.7.2 then when I try to play a different version and try to change the arguments: -Xmx1G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M
Those are the default arguments now with the latest launcher (it changed from just the -xmx1g argument somewhere over the last couple of months).
If you delete the MC Folder, or the launcher XML file, it will re-create the launcher XML file and re-do those exact arguments again.
If you are changing the arguments, saving, exiting, and when you go back in they are back to defaults -- something else is wrong. Perhaps you are running a non-admin account (standard user) and don't have write access to the %appdata%\.minecraft folder.
I have access, It worked before but after I ran the 1.7.2 Shaders It started doing that CONSTANTLY, unchangeable for even launching 1.6.4, I don't understand. I can open Appdata, Thats how I force installed the mod. Any ideas?
First, install forge.
- Use Minecraft Launcher. Make sure you have run Minecraft 1.7.10 at least once before installing Forge.
- Close Minecraft Launcher.
- Use Forge installer to install Forge.
- Open Minecraft Launcher and select Forge Profile (or new/edit profile and select a forge version).
- Click Play. Forge should create mods folder in game directory.
Next, install ShadersMod in mods fodler.
- Copy ShadersMod jar file to mods folder in game directory, so it will be loaded by Forge next time.
- If you want to install this together with OptiFine, also copy Optifine jar file to mods folder.
Test.
- Open Minecraft Launcher. Select Forge profile and click Play.
- Open Option screen. There should be Shaders button. Click it to open Shaders screen.
How to install (Non-Forge Edition)
Before running this installer:
- Use minecraft Launcher. Run Minecraft 1.7.10 at least once and close it.
- Also close Minecraft Launcher before you run this installer.
- If you want to install this together with OptiFine, run OptiFine installer before ShadersMod installer.
- This installer can detect installed OptiFine_1.7.10_HD_U_A4. It will add a separated profile for OptiFine+ShadersMod.
The installer is executable jar file. Double-click it to run.
- If your computer doesn't associate .jar file properly, you may have to run java from command line or batch file.
-- This is the command to use "java -jar ShadersMod-v2.3.21mc1.7.10-installer.jar"
-- You may have to use full path to java.exe if it is not in your PATH environment.
After you run installer successfully:
- Open Minecraft Launcher. Select Profile 1.7.10-ShadersMod or 1.7.10-OptiFine-ShadersMod and click Play.
- Open Option screen. There should be Shaders button. Click it to open Shaders screen.
You also need shaderpack for use with this mod.
- Download and copy shaderpack zip file to shaderpacks folder in minecraft folder.
- You can select shaderpack in Shaders screen.
bump-shadow-waving v0.9.9 (2014-09-06) Download page
Change
- Fix POM glitch on some blocks (eg. Redstone wire).
- Demonstrate how to use the new at_tangent attribute.
- Require ShadersMod v2.3.20+.
The Meaning of Life, the Universe, and Everything.
Location:
Toronto
Join Date:
12/12/2013
Posts:
54
Member Details
Hey Karyonix, I just tried 2.3.20 & 2.3.21 with Optifine instead of the 2.3.18 & 2.3.19. The OpenGL Error Code 9 crashes I use to have when the Shaders Mod and Optifine were combined are no longer occurring and the game runs without any issues at all as of this moment. A HUGE thanks to you Karyonix, you have made my experience with the Shaders a whole lot more enjoyable.
As my way of thanking you for fixing this issue, I have decided to share an In-Progress screenshot of my SEUS-Native Resource Pack that I am currently developing called Faithful Ultra, a high-resolution pack with Shaders-Native capabilities (Bump, Specular, POM, etc.) while trying to maintain the original Minecraft appearance despite all the massive graphical improvements. I have decided to sync the timeline of this resource packs A5 release to the 1.8 Shaders Mod release due to the fact I am upgrading some POM to Models. Thank you so much for fixing those crashes.
Hmm, that is indeed strange.
This can happen with the 'Jelly Shaders' from Sildur or Beed28, but not typically (well, ok, almost never -- I haven't seen it or really heard about it happening to others and I've been around here for a while) with SEUS or Chocapic or Sildur's Vibrant/Basic.
What video card are you running in your system? Also, do you happen to know which driver version you are running?
my card is gtx 470 with 340.52 drivers
Hmm, I haven't upgraded past 335 on my 780ti or 650ti machines.
What other mods do you have installed? Are you using Optifine as well?
Is it possible that its just the card coz it seems to suffer a lot
Edit: It only happened in a single save, too. None of my others. Additionally, when I tried removing this mod, the problem was solved.
It's worth noting that signs and chests in my Jelly World shader "bumped" up and down with the players and mobs when they weren't supposed to when the shader was loaded in certain versions of the shaders mod itself, but it's fixed in the latest version.
Jelly World (Ver. 5.1) - Bendy Ground (Ver. 1.1) - The Wave (Ver. 1.0)
System:
Windows 7 64 bit
12 Gb of Ram
Intel i7 950
Nvidia GeForce GTX 760 4Gb Video Ram (using recommended driver from OP)
Uh, hi
Create an instance, then install the latest/recommended version of Forge (Whatever suits you.) Then add the Shaders core under Loader mods. Add your shaderpack under /instances/[instancename]/minecraft/shaderpacks/
One week for MCP, then however long for the mod developer. Estimated 1.5-2 weeks minimum.
--My PC --SEUS 10.1 Fixes --SEUS Water Fix --SEUS 10.2 Preview --MultiMC 1.8 Shaders Fix (Not needed if using Forge)
* All features from ALPHA & BETA ( If you have been following
* Many versions to choose from inc. Low, Standard and Ultra with MotionBlur & DOF versions
Come and check them out!!!
As a general rule of thumb, running the ShadersMod with no shaderpacks selected causes some pretty strange bugs to occur.
You may not be able to run SEUS v10.1 High/Ultra on that card, but you won't have any problems with Standard or Sildur/Chocapic/MrMeep or the others.
It is very typical to drop FPS from 100-200 to 20 with Shaders because of the way that they run. The shaders are all rendered in real-time, not after the frame is completed, or added as an 'after-effect' like most video games today.
On my 780ti I drop from 200+FPS at 1920x1080 to ~30-40 in SEUS v10.1 Ultra at Far view distance.
Forge edition? I feel this is a trick question...
--My PC --SEUS 10.1 Fixes --SEUS Water Fix --SEUS 10.2 Preview --MultiMC 1.8 Shaders Fix (Not needed if using Forge)
I'm Using MultiMC, and my arguments are different, but those seems wayyyy wrong.
[-XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump, -Xms4096m, -Xmx4096m, -XX:PermSize=128m, -Duser.language=en, -jar, d:/Users/Joshua/Google Drive/MultiMC/jars/NewLaunch.jar]
--My PC --SEUS 10.1 Fixes --SEUS Water Fix --SEUS 10.2 Preview --MultiMC 1.8 Shaders Fix (Not needed if using Forge)
Those are the default arguments now with the latest launcher (it changed from just the -xmx1g argument somewhere over the last couple of months).
If you delete the MC Folder, or the launcher XML file, it will re-create the launcher XML file and re-do those exact arguments again.
If you are changing the arguments, saving, exiting, and when you go back in they are back to defaults -- something else is wrong. Perhaps you are running a non-admin account (standard user) and don't have write access to the %appdata%\.minecraft folder.
ShadersMod v2.3.20 Forge Edition for Minecraft 1.7.10
Download link1 or link2
ShadersMod v2.3.21 Non-Forge Edition Installer for Minecraft 1.7.10
Download link1 or link2
Recent Change
- Added vertex attribute vec4 at_tangent. (at_tangent.xyz = tangent vector, at_tangent.w = handedness)
- Fixed compatibility with ProjectRed-Lighting-1.7.10-4.4.8.47
How to install (Forge Edition)
First, install forge.- Use Minecraft Launcher. Make sure you have run Minecraft 1.7.10 at least once before installing Forge.
- Close Minecraft Launcher.
- Use Forge installer to install Forge.
- Open Minecraft Launcher and select Forge Profile (or new/edit profile and select a forge version).
- Click Play. Forge should create mods folder in game directory.
Next, install ShadersMod in mods fodler.
- Copy ShadersMod jar file to mods folder in game directory, so it will be loaded by Forge next time.
- If you want to install this together with OptiFine, also copy Optifine jar file to mods folder.
Test.
- Open Minecraft Launcher. Select Forge profile and click Play.
- Open Option screen. There should be Shaders button. Click it to open Shaders screen.
How to install (Non-Forge Edition)
Before running this installer:- Use minecraft Launcher. Run Minecraft 1.7.10 at least once and close it.
- Also close Minecraft Launcher before you run this installer.
- If you want to install this together with OptiFine, run OptiFine installer before ShadersMod installer.
- This installer can detect installed OptiFine_1.7.10_HD_U_A4. It will add a separated profile for OptiFine+ShadersMod.
The installer is executable jar file. Double-click it to run.
- If your computer doesn't associate .jar file properly, you may have to run java from command line or batch file.
-- This is the command to use "java -jar ShadersMod-v2.3.21mc1.7.10-installer.jar"
-- You may have to use full path to java.exe if it is not in your PATH environment.
After you run installer successfully:
- Open Minecraft Launcher. Select Profile 1.7.10-ShadersMod or 1.7.10-OptiFine-ShadersMod and click Play.
- Open Option screen. There should be Shaders button. Click it to open Shaders screen.
You also need shaderpack for use with this mod.
- Download and copy shaderpack zip file to shaderpacks folder in minecraft folder.
- You can select shaderpack in Shaders screen.
bump-shadow-waving v0.9.9 (2014-09-06)
Download page
Change
- Fix POM glitch on some blocks (eg. Redstone wire).
- Demonstrate how to use the new at_tangent attribute.
- Require ShadersMod v2.3.20+.
As my way of thanking you for fixing this issue, I have decided to share an In-Progress screenshot of my SEUS-Native Resource Pack that I am currently developing called Faithful Ultra, a high-resolution pack with Shaders-Native capabilities (Bump, Specular, POM, etc.) while trying to maintain the original Minecraft appearance despite all the massive graphical improvements. I have decided to sync the timeline of this resource packs A5 release to the 1.8 Shaders Mod release due to the fact I am upgrading some POM to Models. Thank you so much for fixing those crashes.
Sincerely,
-Mephisto43