Subscribe
blc 3 loading screen problem - possible work around
Posted on 18 January 2021 - 12:44 AM
i have the same problem but i have found a couple work arounds that might work.i found that it was a combo of blc 3, optifine and the texture pack scale. the texture pack had to be 256 or below or either blc or optifine turned off. so try below and see if this helps.1) turn off blc 3
2) or if you insist on blc 3 turn off optifine
3) if you insist on optifine then check your texture pack you are using. mine was a 512x texture pack that made it hang. i could use all others (16,32,64,128,256)
4) in order to get it to start if you insist on blc 3 and optifine with a different texture pack you will need to get to your minecraft folder and go to the resource packs folder and take out the offending texture pack.
Posted on 18 January 2021 - 02:12 AM
russwilson wrote
i have the same problem but i have found a couple work arounds that might work.i found that it was a combo of blc 3, optifine and the texture pack scale. the texture pack had to be 256 or below or either blc or optifine turned off. so try below and see if this helps.
1) turn off blc 3
2) or if you insist on blc 3 turn off optifine
3) if you insist on optifine then check your texture pack you are using. mine was a 512x texture pack that made it hang. i could use all others (16,32,64,128,256)
4) in order to get it to start if you insist on blc 3 and optifine with a different texture pack you will need to get to your minecraft folder and go to the resource packs folder and take out the offending texture pack.
1) turn off blc 3
2) or if you insist on blc 3 turn off optifine
3) if you insist on optifine then check your texture pack you are using. mine was a 512x texture pack that made it hang. i could use all others (16,32,64,128,256)
4) in order to get it to start if you insist on blc 3 and optifine with a different texture pack you will need to get to your minecraft folder and go to the resource packs folder and take out the offending texture pack.
No, I literally deleted my 512x Resource Pack But It Didn't Stop The Glitch From Occurring.