1.8

  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord
P

pancakemaster24

New Member
Jul 29, 2019
137
0
0
With all the drama involved with Mojangs new model format I felt like it would be good to have a thread dedicated to it and all other 1.8 news involving modded Minecraft. So guys knock your selves out but do NOT start a flame war.


 
Indeed. I have a feeling this thread'll die fast- 1.8'll be quite a while. Just look how long 1.7.10 took! We don't even have an official 1.7 pack out of Alpha yet! (dW20 doesn't count).
 
Bashful Giant said:
Indeed. I have a feeling this thread'll die fast- 1.8'll be quite a while. Just look how long 1.7.10 took! We don't even have an official 1.7 pack out of Alpha yet! (dW20 doesn't count).
Click to expand...
True but I meant for this thread to be involved in all1.8 news not just the drama going on now
 
Right now it's a bunch of unanswered questions. I currently have no upgrade path for my main aesthetic mod, so assuming LexManos does listen to all the things modders are doing with the current rendering model, I mainly have to wait to see what they come up with.
 
coolsquid321 said:
Well, since Forge is updated, a lot of mods will probably update soon. 1.8 isn't changing most mods that much, however some mods have problems with the new rendering system (some mods will need 95 gigs of json files). For me, it took about 20 seconds to update. I just had to change my imports.
Click to expand...
Ya i think 1.8 will be easier to update to than 1.7 unless you have custom rendering.My question is how hard will it be for @Reika to update
 
ScottulusMaximus said:
Anyone care to explain what the issue is? I missed this one, what did Mojang break now basically?
Click to expand...
From what I recall, they have a new model format that uses JSON files to define the model. Sounds great. Should make designing custom models more accessible. Sure it is, for vanilla. Then, throw in mods that like to do things beyond cubes, suddenly, this new model format is a clunky old dinosaur. One of the modders calculated their mod would need a couple of gig of json files in the new format, and that mod isn't one of the major custom block users.

So in an ideal world, forge needs to add in a true custom block renderer (as in, restore the old version) so modders can totally bypass the json mess.


Then, add on top of all that the usual mixed reviews on performance being worse, even with all the "improvements" to the rendering system.
 
I feel that someone will come up with a custom renderer between now and the release of big mods/modpacks for 1.8
 
Strikingwolf said:
I feel that someone will come up with a custom renderer between now and the release of big mods/modpacks for 1.8
Click to expand...
Or Forge will reimplement the old ISBRHs. If they do not, I will.

pancakemaster24 said:
Ya i think 1.8 will be easier to update to than 1.7 unless you have custom rendering.My question is how hard will it be for @Reika to update
Click to expand...
Probably less difficult than 1.7, because aside from the Tessellator, less changed "meaningfully", unlike in 1.7 where the syntax of many things changed entirely.
Additionally, I usually just write wrappers for old code; my packet handler is still 1.6 code wrapped in a 1.7 frontend, and I will do the same to get around the ISBRH and BlockPos changes if necessary.


That said, as usual, I will only update when it is both convenient and useful to do so. Early updating alienates most players, and it forces you to trudge through thousands of func_348478_b and field_238972_c before others get around to naming them.
 
  • Like
Reactions: xbony2
Golrith said:
From what I recall, they have a new model format that uses JSON files to define the model. Sounds great. Should make designing custom models more accessible. Sure it is, for vanilla. Then, throw in mods that like to do things beyond cubes, suddenly, this new model format is a clunky old dinosaur. One of the modders calculated their mod would need a couple of gig of json files in the new format, and that mod isn't one of the major custom block users.
Click to expand...

Even if your mod is 'just cubes' the new model system is a problem. If your block has multiple 'states', each one needs a JSON file. Even if you're just changing the texture, which is an incredibly basic feature. Stuff like pipes and cables, which often have 2^6 'states' will need 64 files per block. And mods like Chisel and Carpenter's Blocks? Let's not think about that.
 
Hyperme said:
Even if your mod is 'just cubes' the new model system is a problem. If your block has multiple 'states', each one needs a JSON file. Even if you're just changing the texture, which is an incredibly basic feature. Stuff like pipes and cables, which often have 2^6 'states' will need 64 files per block. And mods like Chisel and Carpenter's Blocks? Let's not think about that.
Click to expand...
The answer is 2^areyouhavingalaughmojang?
 
Hyperme said:
Even if your mod is 'just cubes' the new model system is a problem. If your block has multiple 'states', each one needs a JSON file. Even if you're just changing the texture, which is an incredibly basic feature. Stuff like pipes and cables, which often have 2^6 'states' will need 64 files per block. And mods like Chisel and Carpenter's Blocks? Let's not think about that.
Click to expand...
So are texture packs going to have similar issues?
 
Hyperme said:
Even if your mod is 'just cubes' the new model system is a problem. If your block has multiple 'states', each one needs a JSON file. Even if you're just changing the texture, which is an incredibly basic feature. Stuff like pipes and cables, which often have 2^6 'states' will need 64 files per block. And mods like Chisel and Carpenter's Blocks? Let's not think about that.
Click to expand...

What about TileEntitySpecialRenderer?
 
Golrith said:
From what I recall, they have a new model format that uses JSON files to define the model. Sounds great. Should make designing custom models more accessible. Sure it is, for vanilla. Then, throw in mods that like to do things beyond cubes, suddenly, this new model format is a clunky old dinosaur. One of the modders calculated their mod would need a couple of gig of json files in the new format, and that mod isn't one of the major custom block users.

So in an ideal world, forge needs to add in a true custom block renderer (as in, restore the old version) so modders can totally bypass the json mess.


Then, add on top of all that the usual mixed reviews on performance being worse, even with all the "improvements" to the rendering system.
Click to expand...

Well I got most of that;) Why did Mojang do it tho? I have no knowledge of programming outside a LUA script for a turtle, but if it's hurting mods so badly, surely it negatively impacts vanilla?
 
You must log in or register to reply here.
Top Bottom