So for the first time in all my years of playing minecraft, everything is just a mess. Not only is my 1.8 world, literally not loading in the recent snapshots, any advice on that would be wonderful. But also, as of the last few snapshots, literally no matter what resource pack that I use, none of them will load the grass textures, and it looks ridiculous to have such nice high quality dirt, using 512, up to 2K resource packs, and having that plains 16 pixel dirt, So any advice on either of these problems would be much appreciated.
Don't use snapshots for general play. Load your worlds on a stable version, and wait for a stable 1.13 release. The snapshots are not meant to work perfectly with older worlds.
While that was a kinda nonsense answer, of no help. The last snapshot that loads grass properly, (which is 17w46a) is better then 1.12.2. I have a combinations of resource packs, that will literally not load on 1.12. 1.12 just can't handle it. It's a combination of 512x, to some 1024x resource packs. Forget the 2048 pixel resource packs. So it's a catch 22. So all that said, it's just as bad to have to leave out plenty of resource pack options, to have a couple blocks not load.
Check the pack descriptions, most probably aren't updated for the snapshots, and some may not be updated to the current version of the game either, or simply incomplete all together.
What do you mean by updates for the snapshots? Is there some sort of difference? They all wont load combined on 1.12.2, but a few snapshots later, 17w46a, they'll all load together, and perfect. Then any snapshot after that, they'll all load, but wont display some blocks like the grass, which I know from 46a, that have been designed.
Snapshots are incomplete updates, dev builds for the purpose of debugging. They are changing many things in the snapshots and some may effect the way textures are applied to the blocks. Some resource pack makers may not have updated the packs to accommodate those changes, and some of the packs may not have been updated to even work on 1.12.#, not every resource pack is 100% complete or even updated between versions.
So how would it work on the first 3, but then magically not on the next 10? Is there any reason for that? Some of them even, on certain snapshots, will just load the purple black blocks covering the world, which I know means imcompatible at some level. But I don't know why the latest, stable version won't load them all together, instead crashes and says in the error code that there's to many textures, but after that it'll load, but not display textures.
Well, I guess. But what would cause the game to repeatedly crash upon loading the variety of resource packs on the latest stable version, saying that there are to many textures and I should try a lower resolution pack?
I really do appreciate you trying to help me, but I don't think you're understand. If they're to big for my computer to handle, then why would those same work perfect a couple snapshots later?
And before the questions of my computer continue, my computer is so much better then anything minecraft could ever be, seeing as this computer is only a few months old, and costs just shy of 5 grand. Main components involved, are CPU and GPU, and 7900x and 1080ti are by far exceeding expectations.
Among the changes they may are sometimes ones that effect the way they are loaded in, if the textures are too large, they will sometimes take up too much space in the heap. You can have an amazing computer, this wont effect the limitations of the code itself. The best way to try getting around that limit is to see if giving the game more RAM makes a change, but on some versions the limitation is out of your control.
There's still something so confusing about how an official release having performance issues, then the following couples snapshots fix them and everything works perfectly, following by the next and all remaining snapshots, have the proper performance to them, loading all the resource packs requested, but then in game, they don't display many of the properly loaded resource textures.
The problem lies with the texture pack makers needing to keep their end up to date. Basically there will always be an inconsistency between versions. More so with snapshots as they are ever changing.
Snapshots are put out by Mojang for testing and bug finding, not normal play. The launcher even says this and that you should backup first. If you want to just play use stable releases not buggy test releases.
Once again for you wberosc, that doesn't tell me why 1.12.2 would have issues loading the multiple resource packs, but all the snapshots load them just fine, while most of them just don't display properly. No matter how it's sliced, 17w46a, is a snapshot and is the only one working properly, even compared to the official release.
To explain why resource packs may not work in latest snapshots is simple. Mojang changed how Block ID's are handled. In 17w47a on description page it was said that new format was included and that EVERY, and they meant EVERY Resource Pack is now broken until updated.
That's why 17w46a works and later ones don't.
As for why 1.12.2 doesn't work... I don't know, if you could post a error log it would help.
That's The line that seems troublesome in the output log. If it'll help I can make a 30 second video of the exact same pack not working on 1.12.2, but all snapshots later it loads perfectly. And on top of that, thank you for the specific reason as to why, didn't know they were redoing block ids.
Caught error stitching, removing all assigned resourcepacks
cdo: Unable to fit: minecraft:blocks/log_jungle - size: 2048x2048 - Maybe try a lowerresolution resourcepack?
at cdn.c(SourceFile:58)
at cdp.b(SourceFile:137)
at cdp.a(SourceFile:76)
at cgb.n(SourceFile:763)
at cgb.a(SourceFile:188)
at cgc.a(SourceFile:23)
at cev.c(SourceFile:105)
at cev.a(SourceFile:93)
at bib.f(SourceFile:761)
at bnw.a(SourceFile:133)
at blk.a(SourceFile:337)
at bnw.a(SourceFile:141)
at blk.k(SourceFile:400)
at bnw.k(SourceFile:77)
at blk.q(SourceFile:377)
at bib.t(SourceFile:1625)
at bib.az(SourceFile:1000)
at bib.a(SourceFile:419)
at net.minecraft.client.main.Main.main(SourceFile:123)
Since you don't seem to know anything beyond basic common sense, why are you coming back here? If someone can explain as to why the game will run a resource pack the three different ways, between not loading, loading and working fine, and loading and some textures then great, you simply don't know. DaimeneX was able to identify the reason for them loading, but not displaying, which was due to Block ID's being changed. That's one part answered, but people like you who throw nonsense down "trying to help" are no help. The resource pack clearly isn't the problem as only the "stable and official" 1.12.2 is literally the only release that cannot load it. I don't wanna be rude but you don't need to come back when you don't know much at all about my issues.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
So for the first time in all my years of playing minecraft, everything is just a mess. Not only is my 1.8 world, literally not loading in the recent snapshots, any advice on that would be wonderful. But also, as of the last few snapshots, literally no matter what resource pack that I use, none of them will load the grass textures, and it looks ridiculous to have such nice high quality dirt, using 512, up to 2K resource packs, and having that plains 16 pixel dirt, So any advice on either of these problems would be much appreciated.
Don't use snapshots for general play. Load your worlds on a stable version, and wait for a stable 1.13 release. The snapshots are not meant to work perfectly with older worlds.
While that was a kinda nonsense answer, of no help. The last snapshot that loads grass properly, (which is 17w46a) is better then 1.12.2. I have a combinations of resource packs, that will literally not load on 1.12. 1.12 just can't handle it. It's a combination of 512x, to some 1024x resource packs. Forget the 2048 pixel resource packs. So it's a catch 22. So all that said, it's just as bad to have to leave out plenty of resource pack options, to have a couple blocks not load.
Check the pack descriptions, most probably aren't updated for the snapshots, and some may not be updated to the current version of the game either, or simply incomplete all together.
What do you mean by updates for the snapshots? Is there some sort of difference? They all wont load combined on 1.12.2, but a few snapshots later, 17w46a, they'll all load together, and perfect. Then any snapshot after that, they'll all load, but wont display some blocks like the grass, which I know from 46a, that have been designed.
Snapshots are incomplete updates, dev builds for the purpose of debugging. They are changing many things in the snapshots and some may effect the way textures are applied to the blocks. Some resource pack makers may not have updated the packs to accommodate those changes, and some of the packs may not have been updated to even work on 1.12.#, not every resource pack is 100% complete or even updated between versions.
So how would it work on the first 3, but then magically not on the next 10? Is there any reason for that? Some of them even, on certain snapshots, will just load the purple black blocks covering the world, which I know means imcompatible at some level. But I don't know why the latest, stable version won't load them all together, instead crashes and says in the error code that there's to many textures, but after that it'll load, but not display textures.
Like I said, they make changes between versions.
Well, I guess. But what would cause the game to repeatedly crash upon loading the variety of resource packs on the latest stable version, saying that there are to many textures and I should try a lower resolution pack?
The packs you are trying to load are too big for your computer to handle. Most computers can't handle the larger format packs.
I really do appreciate you trying to help me, but I don't think you're understand. If they're to big for my computer to handle, then why would those same work perfect a couple snapshots later?
And before the questions of my computer continue, my computer is so much better then anything minecraft could ever be, seeing as this computer is only a few months old, and costs just shy of 5 grand. Main components involved, are CPU and GPU, and 7900x and 1080ti are by far exceeding expectations.
Among the changes they may are sometimes ones that effect the way they are loaded in, if the textures are too large, they will sometimes take up too much space in the heap. You can have an amazing computer, this wont effect the limitations of the code itself. The best way to try getting around that limit is to see if giving the game more RAM makes a change, but on some versions the limitation is out of your control.
There's still something so confusing about how an official release having performance issues, then the following couples snapshots fix them and everything works perfectly, following by the next and all remaining snapshots, have the proper performance to them, loading all the resource packs requested, but then in game, they don't display many of the properly loaded resource textures.
The problem lies with the texture pack makers needing to keep their end up to date. Basically there will always be an inconsistency between versions. More so with snapshots as they are ever changing.
-
View User Profile
-
View Posts
-
Send Message
ModeratorSnapshots are put out by Mojang for testing and bug finding, not normal play. The launcher even says this and that you should backup first. If you want to just play use stable releases not buggy test releases.
Once again for you wberosc, that doesn't tell me why 1.12.2 would have issues loading the multiple resource packs, but all the snapshots load them just fine, while most of them just don't display properly. No matter how it's sliced, 17w46a, is a snapshot and is the only one working properly, even compared to the official release.
To explain why resource packs may not work in latest snapshots is simple. Mojang changed how Block ID's are handled. In 17w47a on description page it was said that new format was included and that EVERY, and they meant EVERY Resource Pack is now broken until updated.
That's why 17w46a works and later ones don't.
As for why 1.12.2 doesn't work... I don't know, if you could post a error log it would help.
That's The line that seems troublesome in the output log. If it'll help I can make a 30 second video of the exact same pack not working on 1.12.2, but all snapshots later it loads perfectly. And on top of that, thank you for the specific reason as to why, didn't know they were redoing block ids.
Caught error stitching, removing all assigned resourcepacks
cdo: Unable to fit: minecraft:blocks/log_jungle - size: 2048x2048 - Maybe try a lowerresolution resourcepack?
at cdn.c(SourceFile:58)
at cdp.b(SourceFile:137)
at cdp.a(SourceFile:76)
at cgb.n(SourceFile:763)
at cgb.a(SourceFile:188)
at cgc.a(SourceFile:23)
at cev.c(SourceFile:105)
at cev.a(SourceFile:93)
at bib.f(SourceFile:761)
at bnw.a(SourceFile:133)
at blk.a(SourceFile:337)
at bnw.a(SourceFile:141)
at blk.k(SourceFile:400)
at bnw.k(SourceFile:77)
at blk.q(SourceFile:377)
at bib.t(SourceFile:1625)
at bib.az(SourceFile:1000)
at bib.a(SourceFile:419)
at net.minecraft.client.main.Main.main(SourceFile:123)
Again you either need to do what it says and use a smaller pack, or see if assigning more RAM in your JVM arguments allows it to work.
Since you don't seem to know anything beyond basic common sense, why are you coming back here? If someone can explain as to why the game will run a resource pack the three different ways, between not loading, loading and working fine, and loading and some textures then great, you simply don't know. DaimeneX was able to identify the reason for them loading, but not displaying, which was due to Block ID's being changed. That's one part answered, but people like you who throw nonsense down "trying to help" are no help. The resource pack clearly isn't the problem as only the "stable and official" 1.12.2 is literally the only release that cannot load it. I don't wanna be rude but you don't need to come back when you don't know much at all about my issues.