Change log
2.0.1 beta14
Fixed buffer overflow in ShadersTex.
2.0.1 beta13
Does not require Forge but requires FML.
Compatible with Optifine.
Fixed crash when used with TConstruct.
Bug: ShadersTex does not allocate buffer properly.
Here are my problems:
All the skins get replaced by black and white skins and the items in my hand dont even show up (They are invisible) here is a photo:
<snip>
EDIT:All lighting sources look like this: (Note: They look like this when I drop them too , but in my toolbar they seem normal)
<snip>
And they only light one block.
Hmm, what video card & driver are you running (with nVidia, make sure you aren't running Beta releases)?
Also, forge/glsl/of versions too plz.
Any Dev versions of SEUS being used here, or all SEUS v10.0?
BTW, i've tried DenPipes-1.6.2-2.1.11 with the last forge (871). Only valve pipe is there, the others dont load. Like i said, take your time
I've got 2 pipes, the valve pipe and auto wooden pipe (confirmed in the denpipes.ini). There are a bunch of others showing at the bottom of Buildcraft after the cover panels, but honestly, I don't remember if they were there before denPipes or not..
The wiki is a bit outdated, so, I'm also not sure if I am supposed to see more --- or not. First time using denPipes as well ;)!
We need to know some of your specs, what video card are you trying to run this on? And what OS (Win7, Win8, MAC)?
We are looking at one of 3 scenarios:
1) You have an intel integrated video adapter, in which case, Sildur's shaders would be your only option
2) You are running a MAC (non-intel), in which case, there is no resolution -- speculation says the next MACOS will support OpenGL 4 -- which will get you running again
3) You have a supported video card on Win7/Win8, run the latest WHQL drivers, and you need to edit the composite file for a small patch (below)
Change line 47 in composite.vsh from 'float timePow = 2.0f;' to 'float timePow = 3.0f; Changing it will get rid of the Invalid Program Composite error.
hi, i think this has been previously mentioned but i havent found any answers, ive got a strange huge shadow sphere around me, its size varies depending on how heavily shadowed the shaders are.
if extra info might help i have a radeon 7950 and a i5 3570k
I also run this using a minecraft.jar with forge and the shaders put in magic launcher.
ive also noticed dthat my game crashes when trying to use a non-shadow shader.
You need to edit the composite.fsh using Wordpad or Notepad++ and change the line (#28 in SEUS v10.0):
const float shadowDistance = 80.0f;
to:
const float shadowDistance = 120.0f;
You can go higher than 120.0f, say 160.0f or 200.0f, but this will render much more shadows that you can't see -- and will slow down your game quite a bit.
If you are using a dev build, make sure you read lines 3&4, because there are 2 variables you need to edit so they match.
Hey, I've already done this, this computer was built so no cheap paste and all vents / fans are cleaned regularly, I can't stand dust/fluff :~P
Like I said, CPU temps are high, I cannot reproduce the problem so easily without playing with shaders for an extended period of time but I don't really need to, it's an issue my side, I already know the issue and the only fix really is upgrade / build from scratch which is what I'll be doing shortly
New specs
i5 3570k overclocked
Nvidia GTX 770
16GB RAM
plus of course, all the other parts but in terms of performance those 3 are very different and I expect to not run into the problems I am running into now
Hmm, just sounds strange, funny errors and problems like this bug me to no end . Your specs aren't terribly bad, not great, but not bad. They're a generation behind, on the lower end of the scale, but still would make a good amount of ppl happy.
If you want to upgrade, or use it as an excuse to upgrade (hee hee ), to each their own -- have at it!
If you want to get the old one running and sell it to recoup some of the cost, I'd say swap out RAM (maybe), reinstall Windows & drivers -- probably fix your issue. I know I'd be doing that. Actually, I'd probably get it running, and give it away to someone -- but sounds like you're going to be spending close to a grand after taxes, yeeeeesh !
Ah friend got the same thing, I suggest to stay with beta 9 as it was the best one so far.
You mean GLSL Shaders Beta 9?
Yeah, anything after 9 had the shadow bug as well.. I tweaked most of the shaders I use to get rid of that circle and put the shadows back in ..
I'm trying to keep OF compatibility, mind you, it doesn't really appear to offer the huge performance increases as everyone had hoped -- does it? Especially considering I was using the FPS Plus mod that you were recommending before your thread was wiped :/.
Hey just wanted to Tell you That you cannot Have Mods with this Mod it is a One Mod Thing so Create a New .minecraft Like me, i have a WorldEdit and Optifine .minecraft a Optifine Minecraft a Pixelmon .minecraft a Regular .minecraft just make a .minecraft Backup folder like me then Make Folders in it make a GLSL Shaders .minecraft
Umm, no that is completely incorrect.
There are a small handful of mods that are incompatible. Anything based on modloader (of course -- because FML is supposed to be modloader compatible, but it doesn't appear any 1.6.2 modloader stuff works in Forge). A lot of the video render modifying mods don't, because they interfere with how Optifine / GLSL render the screen.
I've got 54 mods running, just fine... I've got a list around here somewhere...
The user with the error report has problems with BuildCraft & IC2, and I am using both of them .. no problem.
I had problems with PortalGun, and had to remove it.
I've cleaned the system, both inside and out, it's AMD 13.8 driver BETA
Depending on the shaderpack I do get the black scree - GPU stopped responding and recovered, java SE binary stopped etc etc
But this was with a shaderpack I know works fine and I've had hours of gameplay fine with it
What happened was, black screen, "Recommended resolution: 1920x1080" which flickers then any sounds freeze up sounding like some bad dubstep, then BSOD / restart, I've run memory tests and all is good, cpu temp is up
I don't mind, I will continue to use the shaders once I build my new computer, new specs are better and will handle it better and has a cooling system for the cpu, also changing from AMD to Nvidia (build within the next week/fortnight)
edit: sorry i didn't see you latter comment, It was a swift blue screen, I didn't get a chance to read it but assumed it was a mem problem but all is good there, I'm going to put it down to the cpu for now and live without shaders for a week or two
Yeah, still up in the air...
Haven't heard of any problems with 13.8 (or 13.10 beta now?).. Actually, ppl are recommending it over 13.4.
So, it locks up, your monitor loses video signal and goes to sleep, and the classic audio loop. I don't mind dubstep, but definitely not when I'm trying to do something else ;)!
I'm going to say it's either RAM or heat. Maybe the CPU or video card is overheating.
It's crazy simple to pop off the CPU heatsink, clean it up, and re-thermal paste it (if you have the materials -- haha ). Pretty simple with the video card, except instead of some form of quick connect, it's usually 4 screws.
Usually, once pasted, you won't run into problems. Some prebuilts are cheap on the paste, or they use a pad (pads are OK for RAM, but nothing else)... Plus you'd have problems elsewhere.
I'd vote for RAM, or small chance a driver still.
Reboot your machine, hit F8 (you want to be hitting it after the BIOS screen, and before the Windows loading screen). Pick 'disable automatic reboot on system failure'. Then reproduce the error.
This way the blue screen will stay, you can get the error, memory locations (only the first one after STOP is important), and a driver/file that caused it. Then, just reset your PC normally to get it back up and running.
Sadly I can't use these anymore due to a crash the other day which shut the entire computer off with a blue screen, it's a shame because I had no problems at all running it, 50 - 100 FPS on default settings depending on the pack, 35 fps on ultra packs such as SEUS, maybe more if I dropped down to normal render.
I can only presume it's my CPU but there are no noticeable performance dips in game, I was using a medium pack at the time and my FPS was around 80, no lag spikes, just a screen black out then system crash, not sure what I expect as a reply but just putting this out there in case it's not my side
That is sad.
I would try limit frame rate to lower value and use lower resolution to reduce GPU workload.
If you just update your graphics driver, take this into consideration. NVIDIA driver 320.xx crash very often on my PC and 326.xx beta crash less often. I can only use up to 314.22.
Sounds like it could be drivers, as Karyonix mentioned, but usually you get the 'video display driver stopped working and recovered' message.
I would suggest cleaning fans/heatsinks/filters. It sounds like either heat, or power if you get random lockups/crashes/reboots with no BSOD or errors.
Err, you said bluescreen, what error does it say? Basically, it could still be: heat, power, drivers, but could also be RAM.
I would try removing mods, one of them must be causing the issue.
When you say it goes small to the lower-left, you mean the brown minecraft-bg is over the whole screen, but the play area is only 1/4 of the screen? What happens if you minimize/maximize the screen again?
Sounds like it could be damage indicators, NEI's item name overlay causes problems with shaders (makes the screen flash and flicker).
So I have come across an issue. I have everything installed and Minecraft runs properly except when I turn on any of the shaders my screen minimalises to the bottom left corner and has other images of it in the corner as well. When I turn the shaders off though it all goes back to normal.
Which versions are you using (MC, Forge, GLSL, Optifine)?
I... Got the mod working, but now it leaves me even more confused... Whenever I switch shaders in a world my player model gets all sorts of messed up. The torso becomes a leg, the head becomes an arm, the legs just kinda.. Float in place perpendicular to where the torso should be, my arms replaced my torso... ._.
Yeah, Karyonix is aware, Sildur pointed it out about 5 minutes after him posting the new release :P.
Karyonix had to re-write how the body is rendered (or is re-writing?) due to a glitch in Beta 9/11.
I believe it was resolved in Beta 12, but when you change shaders this happens.
Just choose the shaderpack you want to use, exit MC, and go back in. The glitch should be fixed.
I just now got this, installed without any problems.. But even without any shaders, when I attempt to load a world, the screen continuously flashes between a dirt background and the main menu while the world continues to play in the background. I know it's actually loaded because all of the sounds are playing, I can hear my footsteps as I walk, zombies in a nearby cave, etcetera... But all I see is the flashing main menu. What could be causing this?
-Edit-
My Optifine and Forge versions are outdated it seems, installing the updated versions now.
-Edit-
Updating Forge proves to completely break my game for some reason. The crash report has something to do with worldgen, the heck?
You should be running Forge 859 with the latest GLSL Shaders Beta 12 (that is what Karyonix tested it on and recommends). Optifine 1.6.2 Ultra C4 needs anything over Forge 845.
When you are downloading GLSL, make sure you grab the Optifine edition ;)!
As for installing, both OF and GLSL go into the mods folder, nothing going into the Forge JAR (.minecraft\versions\Forge##\Forge##.jar) anymore. If you are using MagicLauncher, both mods go in the bottom, nothing goes in the top.
I keep getting this error that says "invalid program composite" when i try to use SEUS, but all other shaders i use work fine. Yes, I did install it correctly.
Specs:
8 gigs ram
1tb hdd
GTX 760
AMD Phenom II X4 965
600 w PSU
I'm guessing you have a white screen as well? Try redownloading. If you altered the composite .fsh or .vsh, and what you enetered doesn't work, you will get that error as well, so try rollback to when it was working, or redownload and replace the file.
Well, first off, if you are running the Beta nVidia drivers -- roll back to 320.49 (Sonic Ether recommends 306.XX).
Otherwise, it's likely that he/she will need to edit the composite.vsh and change a value (happens intermittently on some video cards - Windows):
Change line 47 in composite.vsh from 'float timePow = 2.0f;' to 'float timePow = 3.0f; Changing it will get rid of the Invalid Program Composite error.
0
Affirmative, this is a known issue in V12.
It is resolved in V14.
0
Hmm, what video card & driver are you running (with nVidia, make sure you aren't running Beta releases)?
Also, forge/glsl/of versions too plz.
Any Dev versions of SEUS being used here, or all SEUS v10.0?
0
I've got 2 pipes, the valve pipe and auto wooden pipe (confirmed in the denpipes.ini). There are a bunch of others showing at the bottom of Buildcraft after the cover panels, but honestly, I don't remember if they were there before denPipes or not..
The wiki is a bit outdated, so, I'm also not sure if I am supposed to see more --- or not. First time using denPipes as well ;)!
Forge 859 here.
0
We need to know some of your specs, what video card are you trying to run this on? And what OS (Win7, Win8, MAC)?
We are looking at one of 3 scenarios:
1) You have an intel integrated video adapter, in which case, Sildur's shaders would be your only option
2) You are running a MAC (non-intel), in which case, there is no resolution -- speculation says the next MACOS will support OpenGL 4 -- which will get you running again
3) You have a supported video card on Win7/Win8, run the latest WHQL drivers, and you need to edit the composite file for a small patch (below)
*******************
You need to edit the composite.fsh using Wordpad or Notepad++ and change the line (#28 in SEUS v10.0):
to:
You can go higher than 120.0f, say 160.0f or 200.0f, but this will render much more shadows that you can't see -- and will slow down your game quite a bit.
If you are using a dev build, make sure you read lines 3&4, because there are 2 variables you need to edit so they match.
0
Hmm, just sounds strange, funny errors and problems like this bug me to no end . Your specs aren't terribly bad, not great, but not bad. They're a generation behind, on the lower end of the scale, but still would make a good amount of ppl happy.
If you want to upgrade, or use it as an excuse to upgrade (hee hee ), to each their own -- have at it!
If you want to get the old one running and sell it to recoup some of the cost, I'd say swap out RAM (maybe), reinstall Windows & drivers -- probably fix your issue. I know I'd be doing that. Actually, I'd probably get it running, and give it away to someone -- but sounds like you're going to be spending close to a grand after taxes, yeeeeesh !
Good luck!
0
You mean GLSL Shaders Beta 9?
Yeah, anything after 9 had the shadow bug as well.. I tweaked most of the shaders I use to get rid of that circle and put the shadows back in ..
I'm trying to keep OF compatibility, mind you, it doesn't really appear to offer the huge performance increases as everyone had hoped -- does it? Especially considering I was using the FPS Plus mod that you were recommending before your thread was wiped :/.
0
Forge 859, Optifine 1.6.2. Ultra C4, GLSL Shaders Beta 14.
nVidia Quadro FX880m w/ 320.18 drivers
Basic Shaders 8:
Vibrant Standard:
Vibrant w/ CEL:
0
Umm, no that is completely incorrect.
There are a small handful of mods that are incompatible. Anything based on modloader (of course -- because FML is supposed to be modloader compatible, but it doesn't appear any 1.6.2 modloader stuff works in Forge). A lot of the video render modifying mods don't, because they interfere with how Optifine / GLSL render the screen.
I've got 54 mods running, just fine... I've got a list around here somewhere...
The user with the error report has problems with BuildCraft & IC2, and I am using both of them .. no problem.
I had problems with PortalGun, and had to remove it.
0
Yeah, still up in the air...
Haven't heard of any problems with 13.8 (or 13.10 beta now?).. Actually, ppl are recommending it over 13.4.
So, it locks up, your monitor loses video signal and goes to sleep, and the classic audio loop. I don't mind dubstep, but definitely not when I'm trying to do something else ;)!
I'm going to say it's either RAM or heat. Maybe the CPU or video card is overheating.
It's crazy simple to pop off the CPU heatsink, clean it up, and re-thermal paste it (if you have the materials -- haha ). Pretty simple with the video card, except instead of some form of quick connect, it's usually 4 screws.
Usually, once pasted, you won't run into problems. Some prebuilts are cheap on the paste, or they use a pad (pads are OK for RAM, but nothing else)... Plus you'd have problems elsewhere.
I'd vote for RAM, or small chance a driver still.
Reboot your machine, hit F8 (you want to be hitting it after the BIOS screen, and before the Windows loading screen). Pick 'disable automatic reboot on system failure'. Then reproduce the error.
This way the blue screen will stay, you can get the error, memory locations (only the first one after STOP is important), and a driver/file that caused it. Then, just reset your PC normally to get it back up and running.
0
Don't mind if I dooooooooooo :D!
Sounds like it could be drivers, as Karyonix mentioned, but usually you get the 'video display driver stopped working and recovered' message.
I would suggest cleaning fans/heatsinks/filters. It sounds like either heat, or power if you get random lockups/crashes/reboots with no BSOD or errors.
Err, you said bluescreen, what error does it say? Basically, it could still be: heat, power, drivers, but could also be RAM.
0
I am running the same versions, along with all of your mods except:
I would try removing mods, one of them must be causing the issue.
When you say it goes small to the lower-left, you mean the brown minecraft-bg is over the whole screen, but the play area is only 1/4 of the screen? What happens if you minimize/maximize the screen again?
Sounds like it could be damage indicators, NEI's item name overlay causes problems with shaders (makes the screen flash and flicker).
0
Which versions are you using (MC, Forge, GLSL, Optifine)?
0
Yeah, Karyonix is aware, Sildur pointed it out about 5 minutes after him posting the new release :P.
Karyonix had to re-write how the body is rendered (or is re-writing?) due to a glitch in Beta 9/11.
I believe it was resolved in Beta 12, but when you change shaders this happens.
Just choose the shaderpack you want to use, exit MC, and go back in. The glitch should be fixed.
0
You should be running Forge 859 with the latest GLSL Shaders Beta 12 (that is what Karyonix tested it on and recommends). Optifine 1.6.2 Ultra C4 needs anything over Forge 845.
When you are downloading GLSL, make sure you grab the Optifine edition ;)!
As for installing, both OF and GLSL go into the mods folder, nothing going into the Forge JAR (.minecraft\versions\Forge##\Forge##.jar) anymore. If you are using MagicLauncher, both mods go in the bottom, nothing goes in the top.
0
Well, first off, if you are running the Beta nVidia drivers -- roll back to 320.49 (Sonic Ether recommends 306.XX).
Otherwise, it's likely that he/she will need to edit the composite.vsh and change a value (happens intermittently on some video cards - Windows):
Well, we need some more specs from you:
CPU
RAM
Video Card
Also, how much memory is allocated to Minecraft?
Which mods are in use?
Might help if you posted your Forge Log too (copy/paste into a pastebin and linky here).