Umm, can someone help me? Everything looks okay but when i used sildur's shaders or MrMeep's Shader pack, it looked ok for 5 seconds but then my Minecraft Crashed. And when i use the other Shaders, i my character is pitch black and some other players are untextured. And i cant see any kind of mobs what hit me or what i am killing and i cant see anything what is is on my hand.
Help, Please?
You're using 1.6.4?
Are you using Optifine as well?
If you are ... did you apply Karyonix FML Loading patch?
Well, Im using 1.6.2, and using Optifine HD U C4, (yes they are for 1.6.2) But i don't seem to see the KaryOnix FML Shader Patch, nor i haven't downloaded it yet... i've searched for it but nothing is found?
The Karyonix FML Patch is on the 1st post of this thread, but it is only needed in 1.6.4.
What kind of video card is in your computer (Intel, AMD, nVidia)? Also, what driver is installed for it (320.49, 331.XX //\\ 13.9, 13.11), and what OS (Windows, Mac)?
Do you use any other resource packs on your machine? If you did, did you increase your Java memory in the Minecraft Launcher at all?
Might help if you posted a ForgeModLoader-Client-0.log or Crash Dump when it crashes, please use spoiler tags, or post it to pastebin.com and link it here.
It could be talking about VideoRAM (if he has Intel Integrated video, or a 256/512MB video card)..
As for RAM, I would recommend Xmx350M (the default), and Xms####M as 1/2 of your physical ram (the number that start -> rt-click computer -> properties says under system).
If your computer has 4GB of RAM, use Xms2048M. If it is 8GB of RAM, you can use Xms4096M. Don't use any more than that, even if your computer has the RAM, it's useless.
To be honest, anything over 2048MB is useless. Minecraft allocates 1024 (1GB) by default now.
Yeah I see what you mean, only reason I use the parameters is because when you reach a certain number of mods minecraft crashes.
Only issue I'm having now atm is with the shaders mod here. when I have it installed I get that flickering screen when the world tries to load up and of course the lines I posted on the previous page of this thread. Don't know why it's doing it, before I didn't have an issue and now it just does it.
Yeah I see what you mean, only reason I use the parameters is because when you reach a certain number of mods minecraft crashes.
Only issue I'm having now atm is with the shaders mod here. when I have it installed I get that flickering screen when the world tries to load up and of course the lines I posted on the previous page of this thread. Don't know why it's doing it, before I didn't have an issue and now it just does it.
I use Xms350M and Xmx4096M myself, because all of my machines have either 8GB or 16GB of RAM, and I use a x32 texturepack with Bump Mapping (and Mod Support). I have 60 mods in my list.
Works pretty flawlessly, and I'm quite happy with it!
Enough bragging, mind you, lol..
I can agree that more mods, and more textures will cause MC to crash if it isn't allocated enough ram. If it's allocated too much, Windows will crash :P. The other concern is that the shaders run in a memory allocation outside of MC & WINDOWS, so, it needs its own RAM as well.
What video card is in your system, and what OS?
I'm going to guess Windows, and nVidia.
If it's Mac, you're going to be out of luck. You'll have to use Sildur's Shaders, or Chocapic's WIP.
If it's Windows, roll back your display drivers to 320.49 or earlier. Sonic Ether recommends 306.XX and Karyonix recommends 314.XX. I use 320.49 myself on all of my computers. The latest 331 works, but you have to edit composite.vsh and change line 47 'float timepow = 2.0f;' to 'float timepow = 3.0f;'.
If it's Windows and you have an AMD, strange, it's slower but normally flawless. Upgrade your drivers to the latest 13.11 BETA drivers. They work great, and give more OpenGL support ;).
I use Xms350M and Xmx4096M myself, because all of my machines have either 8GB or 16GB of RAM, and I use a x32 texturepack with Bump Mapping (and Mod Support). I have 60 mods in my list.
Works pretty flawlessly, and I'm quite happy with it!
Enough bragging, mind you, lol..
I can agree that more mods, and more textures will cause MC to crash if it isn't allocated enough ram. If it's allocated too much, Windows will crash . The other concern is that the shaders run in a memory allocation outside of MC & WINDOWS, so, it needs its own RAM as well.
What video card is in your system, and what OS?
I'm going to guess Windows, and nVidia.
If it's Mac, you're going to be out of luck. You'll have to use Sildur's Shaders, or Chocapic's WIP.
If it's Windows, roll back your display drivers to 320.49 or earlier. Sonic Ether recommends 306.XX and Karyonix recommends 314.XX. I use 320.49 myself on all of my computers. The latest 331 works, but you have to edit composite.vsh and change line 47 'float timepow = 2.0f;' to 'float timepow = 3.0f;'.
If it's Windows and you have an AMD, strange, it's slower but normally flawless. Upgrade your drivers to the latest 13.11 BETA drivers. They work great, and give more OpenGL support .
Yeah I have an AMD card, used to use Nvidia but I switched over, the AMD card I use right now has lasted much longer compared to the Nvidia cards I've had, 3 so far and all them have died on me and they weren't even overclocked! I'll try applying the beta drivers and see what happens.
Yeah I have an AMD card, used to use Nvidia but I switched over, the AMD card I use right now has lasted much longer compared to the Nvidia cards I've had, 3 so far and all them have died on me and they weren't even overclocked! I'll try applying the beta drivers and see what happens.
You won't have any luck. The folks in this thread think that everything works hunky-dory on AMD cards, when the truth is that it does not.
Yeah I have an AMD card, used to use Nvidia but I switched over, the AMD card I use right now has lasted much longer compared to the Nvidia cards I've had, 3 so far and all them have died on me and they weren't even overclocked! I'll try applying the beta drivers and see what happens.
You won't have any luck. The folks in this thread think that everything works hunky-dory on AMD cards, when the truth is that it does not.
I have to say this is completely inaccurate. There are far more nVidia problems on here (driver related) than AMD problems.
The only AMD problem is that it is 50% slower than the comparable nVidia counterpart. Once in a blue moon you will get a shaderpack that won't load pieces, which is a shaderpack issue -- the only ones I've seen do this are SEUS L1-2-3 and M1.
Good luck from me and all the people above me! (:P)
I honestly wish for you to take your time, since I wouldn't like people to report the same bugs over and over again.
Really? AWESOME!!! And can someone help me with the missing arms, legs, body parts, etc. bug?
You're using 1.6.4?
Are you using Optifine as well?
If you are ... did you apply Karyonix FML Loading patch?
Do you use Optifine? is so the missing body parts on Steve and mobs is from a bug in Optifine.
Yup. I know that. I just want to know if anyone has a fix for it.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium2013-11-27 08:15:13 [INFO] [STDERR] GL error 0x0506: Invalid framebuffer operation (Fb status 0x8CD6) at pre endHand
2013-11-27 08:15:13 [INFO] [STDERR] FramebufferStatus 0x8CD6 at pre endHand
2013-11-27 08:15:13 [INFO] [STDERR] GL error 0x0505: Out of memory at pre-useProgram
2013-11-27 08:15:13 [INFO] [STDERR] GL error 0x0506: Invalid framebuffer operation (Fb status 0x8CD5) at pre-final
2013-11-27 08:15:13 [INFO] [STDERR] GL error 0x0506: Invalid framebuffer operation (Fb status 0x8CD6) at shadow clear pre
2013-11-27 08:15:13 [INFO] [STDERR] FramebufferStatus 0x8CD6 at shadow clear
2013-11-27 08:15:13 [INFO] [STDERR] GL error 0x0506: Invalid framebuffer operation (Fb status 0x8CD6) at shadow clear
2013-11-27 08:15:13 [INFO] [STDERR] FramebufferStatus 0x8CD6 at beginUpdateChunks1
2013-11-27 08:15:13 [INFO] [STDERR] FramebufferStatus 0x8CD6 at beginUpdateChunks2
2013-11-27 08:15:13 [INFO] [STDERR] FramebufferStatus 0x8CD6 at endUpdateChunks1
2013-11-27 08:15:13 [INFO] [STDERR] FramebufferStatus 0x8CD6 at endUpdateChunks2
2013-11-27 08:15:13 [INFO] [STDERR] GL error 0x0506: Invalid framebuffer operation (Fb status 0x8CD6) at pre-useProgram
2013-11-27 08:15:13 [INFO] [STDERR] GL error 0x0506: Invalid framebuffer operation (Fb status 0x8CD6) at pre-useProgram
2013-11-27 08:15:13 [INFO] [STDERR] GL error 0x0506: Invalid framebuffer operation (Fb status 0x8CD6) at endTileEntities
2013-11-27 08:15:13 [INFO] [STDERR] GL error 0x0501: Invalid value at copy shadow depth
2013-11-27 08:15:13 [INFO] [STDERR] GL error 0x0506: Invalid framebuffer operation (Fb status 0x8CD6) at pre-useProgram
2013-11-27 08:15:13 [INFO] [STDERR] GL error 0x0506: Invalid framebuffer operation (Fb status 0x8CD6) at clear pre
2013-11-27 08:15:13 [INFO] [STDERR] FramebufferStatus 0x8CD6 at clear
2013-11-27 08:15:13 [INFO] [STDERR] GL error 0x0506: Invalid framebuffer operation (Fb status 0x8CD6) at clear
2013-11-27 08:15:13 [INFO] [STDERR] GL error 0x0506: Invalid framebuffer operation at gbuffers_skybasic fogMode
2013-11-27 08:15:13 [INFO] [STDERR] GL error 0x0506: Invalid framebuffer operation (Fb status 0x8CD6) at pre-useProgram
2013-11-27 08:15:13 [INFO] [STDERR] GL error 0x0506: Invalid framebuffer operation (Fb status 0x8CD6) at pre-useProgram
2013-11-27 08:15:13 [INFO] [STDERR] GL error 0x0506: Invalid framebuffer operation at gbuffers_skybasic fogMode
2013-11-27 08:15:13 [INFO] [STDERR] GL error 0x0506: Invalid framebuffer operation (Fb status 0x8CD6) at pre-useProgram
2013-11-27 08:15:13 [INFO] [STDERR] FramebufferStatus 0x8CD6 at beginUpdateChunks1
2013-11-27 08:15:13 [INFO] [STDERR] FramebufferStatus 0x8CD6 at beginUpdateChunks2
2013-11-27 08:15:13 [INFO] [STDERR] FramebufferStatus 0x8CD6 at endUpdateChunks1
2013-11-27 08:15:13 [INFO] [STDERR] FramebufferStatus 0x8CD6 at endUpdateChunks2
2013-11-27 08:15:13 [INFO] [STDERR] GL error 0x0506: Invalid framebuffer operation at gbuffers_textured fogMode
2013-11-27 08:15:13 [INFO] [STDERR] GL error 0x0506: Invalid framebuffer operation (Fb status 0x8CD6) at pre-useProgram
2013-11-27 08:15:13 [INFO] [STDERR] GL error 0x0506: Invalid framebuffer operation (Fb status 0x8CD6) at endTileEntities
2013-11-27 08:15:13 [INFO] [STDERR] GL error 0x0506: Invalid framebuffer operation (Fb status 0x8CD6) at pre-useProgram
2013-11-27 08:15:13 [INFO] [STDERR] GL error 0x0506: Invalid framebuffer operation (Fb status 0x8CD6) at pre-useProgram
2013-11-27 08:15:13 [INFO] [STDERR] GL error 0x0506: Invalid framebuffer operation (Fb status 0x8CD6) at pre-useProgram
2013-11-27 08:15:13 [INFO] [STDERR] GL error 0x0506: Invalid framebuffer operation (Fb status 0x8CD6) at pre-useProgram
2013-11-27 08:15:13 [INFO] [STDERR] GL error 0x0506: Invalid framebuffer operation (Fb status 0x8CD6) at pre-useProgram
2013-11-27 08:15:13 [INFO] [STDERR] FramebufferStatus 0x8CD6 at beginHand
2013-11-27 08:15:13 [INFO] [STDERR] GL error 0x0506: Invalid framebuffer operation (Fb status 0x8CD6) at pre endHand
2013-11-27 08:15:13 [INFO] [STDERR] FramebufferStatus 0x8CD6 at pre endHand
2013-11-27 08:15:13 [INFO] [STDERR] GL error 0x0505: Out of memory at pre-useProgram
2013-11-27 08:15:13 [INFO] [STDERR] GL error 0x0506: Invalid framebuffer operation (Fb status 0x8CD5) at pre-final
AND MORE......
please help me!!! (and fix it)
I only get this issue if I change Resource Pack or Shader Pack mid-game. As soon as I exit and reload, I'm fine again.
I also use Player API and Smart Moving..
The Karyonix FML Patch is on the 1st post of this thread, but it is only needed in 1.6.4.
What kind of video card is in your computer (Intel, AMD, nVidia)? Also, what driver is installed for it (320.49, 331.XX //\\ 13.9, 13.11), and what OS (Windows, Mac)?
Do you use any other resource packs on your machine? If you did, did you increase your Java memory in the Minecraft Launcher at all?
Might help if you posted a ForgeModLoader-Client-0.log or Crash Dump when it crashes, please use spoiler tags, or post it to pastebin.com and link it here.
Out of memory issue hmm I usually use this, though don't know if it'll help, put it in the java paramaters
-Xmx2560M -Xms2560M -d64 -XX:MaxPermSize=256M -XX:UseSSE=4 -Djava.net.preferIPv4Stack=true -XX:+UseStringCache -XX:+OptimizeStringConcat -XX:+UseFastAccessorMethods
It could be talking about VideoRAM (if he has Intel Integrated video, or a 256/512MB video card)..
As for RAM, I would recommend Xmx350M (the default), and Xms####M as 1/2 of your physical ram (the number that start -> rt-click computer -> properties says under system).
If your computer has 4GB of RAM, use Xms2048M. If it is 8GB of RAM, you can use Xms4096M. Don't use any more than that, even if your computer has the RAM, it's useless.
To be honest, anything over 2048MB is useless. Minecraft allocates 1024 (1GB) by default now.
Only issue I'm having now atm is with the shaders mod here. when I have it installed I get that flickering screen when the world tries to load up and of course the lines I posted on the previous page of this thread. Don't know why it's doing it, before I didn't have an issue and now it just does it.
I use Xms350M and Xmx4096M myself, because all of my machines have either 8GB or 16GB of RAM, and I use a x32 texturepack with Bump Mapping (and Mod Support). I have 60 mods in my list.
Works pretty flawlessly, and I'm quite happy with it!
Enough bragging, mind you, lol..
I can agree that more mods, and more textures will cause MC to crash if it isn't allocated enough ram. If it's allocated too much, Windows will crash :P. The other concern is that the shaders run in a memory allocation outside of MC & WINDOWS, so, it needs its own RAM as well.
What video card is in your system, and what OS?
I'm going to guess Windows, and nVidia.
If it's Mac, you're going to be out of luck. You'll have to use Sildur's Shaders, or Chocapic's WIP.
If it's Windows, roll back your display drivers to 320.49 or earlier. Sonic Ether recommends 306.XX and Karyonix recommends 314.XX. I use 320.49 myself on all of my computers. The latest 331 works, but you have to edit composite.vsh and change line 47 'float timepow = 2.0f;' to 'float timepow = 3.0f;'.
If it's Windows and you have an AMD, strange, it's slower but normally flawless. Upgrade your drivers to the latest 13.11 BETA drivers. They work great, and give more OpenGL support ;).
Yeah I have an AMD card, used to use Nvidia but I switched over, the AMD card I use right now has lasted much longer compared to the Nvidia cards I've had, 3 so far and all them have died on me and they weren't even overclocked! I'll try applying the beta drivers and see what happens.
here's the forge log I hope I can solve this
http://www.mediafire.com/view/8flz71o45lwskxy/ForgeModLoader-client-0.log
Check your file name in the properties and make sure it's does not end as ",jar,zip"
If it does, remove the ".zip" and the end will be .jar
I get this even if I DON'T change resource pack/shaders. It started since Optifine updated to HD_U_C7, and now it even happens on HD_U_C6...
You won't have any luck. The folks in this thread think that everything works hunky-dory on AMD cards, when the truth is that it does not.
He will have to go into Computer -> Organize -> Folder and Search Options -> View and uncheck the box 'hide file extensions for known file types'.
Then he can rename the file and take the .ZIP off the end so it is only .JAR.
This is a strange mediafire bug when using specific browsers (like it happens with IE but not FF).
Hmm, I just updated to HD_U_C7 yesterday, with Karyonix's patch.
I'll have to see if it is doing it to me now, I've only updated one of my installs at the moment (my notebook with an FX 880m).
I'll take a boo for you, I can't believe your log is 1.96MB!
Mine with 60 mods is only on average 650KB.
I have to say this is completely inaccurate. There are far more nVidia problems on here (driver related) than AMD problems.
The only AMD problem is that it is 50% slower than the comparable nVidia counterpart. Once in a blue moon you will get a shaderpack that won't load pieces, which is a shaderpack issue -- the only ones I've seen do this are SEUS L1-2-3 and M1.